> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/network/cheqd/identity-write-pricing.md).

# Identity Write Pricing

Pricing for identity transactions on the cheqd Network, including Decentralized Identifiers (DIDs) and DID-Linked Resources (DLRs).

> Note: the prices listed below are subject to change, as they are parameters controlled by community governance mechanisms.

## cheqd Identity Write Pricing

Below are a list of prices in CHEQ and approximate dollar values for carrying our identity writes to the network:

| Metric                        | Cost (USD) |
| ----------------------------- | ---------- |
| **DID write**                 | $2.00      |
| **DID update**                | $1.00      |
| **DID deactivate**            | $0.40      |
| **Resource create (default)** | $0.20      |
| **Resource create (JSON)**    | $0.10      |
| **Resource create (image)**   | $0.40      |

cheqd Identity pricing detailed above was implemented on-ledger as part of the January 2023 release - [v1.0.x](https://product.cheqd.io/network/upgrades/2021/v0.1.x)​.

For more information on cheqd's Identity Transaction pricing, see our latest Tokenomics - [cheqd’s tokenomics for SSI explained: part 4](https://blog.cheqd.io/cheqds-tokenomics-for-ssi-explained-part-4-3f4c6a9ea1c0).

## Comparison with other networks <a href="#comparison-with-other-networks" id="comparison-with-other-networks"></a>

| Metric                                      | cheqd Testnet | cheqd Mainnet        | Sovrin StagingNet | Sovrin MainNet | Indicio   |
| ------------------------------------------- | ------------- | -------------------- | ----------------- | -------------- | --------- |
| **DID write**                               | Free          | \~$2.00 *(50 CHEQ)*  | $1.00             | $10.00         | $5000 p/a |
| **DID update**                              | Free          | \~$1.00 *(25 CHEQ)*  | $1.00             | $10.00         | $5000 p/a |
| **DID deactivate**                          | Free          | \~$0.40 *(10 CHEQ)*  | $1.00             | $10.00         | $5000 p/a |
| **Resource create (schema)**                | Free          | \~$0.10 *(2.5 CHEQ)* | $5.00             | $50.00         | $5000 p/a |
| **Resource create (credential definition)** | Free          | \~$0.10 *(2.5 CHEQ)* | $2.50             | $25.00         | $5000 p/a |
| **Resource create (status list)**           | Free          | \~$0.10 *(2.5 CHEQ)* | $2.00             | $20.00         | $5000 p/a |
| **Resource create (status list entry)**     | Free          | \~$0.10 *(2.5 CHEQ)* | $0.01             | $0.10          | $5000 p/a |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cheqd.io/product/network/cheqd/identity-write-pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.