Deactivate a DID

The purpose of this document is to describe how an existing DID (and associated DIDDoc) can be deactivated using the cheqd-node Cosmos CLI.

NOTE: The procedures below are only recommended for development purposes!

Using cheqd-node Cosmos 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.

Setup

Pre-Requisites

• Learn how to

• with cheqd Cosmos CLI

Deactivate an existing DID

1. Compile the payload

As in flow with we need to compile payload.json file with private key inside and pass it to the CLI. The resulting JSON in our example will look liks:

3. Send an deactivate DID transaction to the ledger

Send the updated DIDDoc to the ledger. This must be signed with the correct identity keys:

Flags

• Payload_in_JSON - previously compiled JSON.

• --from: Cosmos account key which will pay fees for the transaction to be written to ledger.

• --node

Note that each of cheqd's on-ledger identity transactions has a fixed fee, . If your account has insufficient balance the transaction will fail.

Example