Deactivating existing DIDs with cheqd Cosmos CLI
The purpose of this document is to describe how an existing DID (and associated DIDDoc) can be deactivated using the
NOTE: The procedures below are only recommended for development purposes!Using
cheqd-nodeCosmos CLI for real-world production usage is not recommended, since the identity keys are passed in raw form to the CLI. This is fine in development/testing usage, but is not recommend for mainnet.Developers are encouraged to use production-grade CLI tools such as Veramo SDK for cheqd or look at our developer guide on how to integrate custom applications.
As in flow with creating DID-Document we need to compile
payload.jsonfile with private key inside and pass it to the CLI. The resulting JSON in our example will look liks:
Send the updated DIDDoc to the ledger. This must be signed with the correct identity keys:
cheqd-noded tx cheqd deactivate-did <Payload_in_JSON> \
--from <cosmos_account> --node <url> --chain-id <chain> --fees <fee>
Payload_in_JSON- previously compiled JSON.
--from: Cosmos account key which will pay fees for the transaction to be written to ledger.
--node: IP address or URL of node to send request to
--fees: Set to 10000000000ncheq, which is the fixed fee for deactivating a DID
Note that each of cheqd's on-ledger identity transactions has a fixed fee, the pricing for cheqd DIDs and DID-Linked Resources can be found here. If your account has insufficient balance the transaction will fail.
cheqd-noded tx cheqd deactivate-did "payload.json" \
--from my_account --node http://rpc.cheqd.network:443 --chain-id cheqd-testnet-6 --fees 10000000000ncheq