"DID-Linked Resources" are identified with a did:cheqd Decentralized Identifier with a Universally Unique Identifier (UUID) that acts as a permanently-accessible link to fetch the resources from the cheqd ledger. We refer to this as the "resource ID". Through the "resource ID" or a set of DID URL query parameters, applications are able to persistently access a digital resource on the cheqd network.
| Create DID-Linked Resource | Create a custom DID-Linked Resource for a schema, Trust Registry or other persistent data file. | create-dlr.md |
| Create Status List | Create an on-ledger Status List associated with a DID. | status-lists |
| Understanding DID-Linked Resources | Detailed guide explaining the context and technical composition of DID-Linked Resources on cheqd. | understanding-dlrs |
| DID Resolution and DID URL Dereferencing | Architecture decision record explaining the different parameters for fetching DID Document data on cheqd, including DID-Linked Resources | adr-005-did-resolution-and-did-url-dereferencing.md |
Below are a list of alternatives for creating cheqd DID-Linked Resources.
| cheqd Studio | Our API product enables users to use cheqd's functionality with minimal complexity and easily integrate APIs into existing apps. | Broken link |
| DID Registrar | Simple setup for building cheqd DIDs into existing applications using REST APIs, building into the Universal Registrar. | did-registrar |
| Credo | Credo is an SDK which supports the European Architecture and Reference Framework (ARF) standards as well as AnonCreds with full cheqd support for DIDs. | credo.md |
| cheqd Cosmos CLI | Cosmos-native CLI for creating transactions on cheqd. Should be used for testing purposes only. |