did:cheqd using our DID ResolverThis page describes how to use and set up the cheqd DID Resolver software package.
If you do not want to install anything and just want to resolve a did:cheqd entry from the ledger, you can load the REST API endpoint for resolver.cheqd.net in your browser.
Or, make a request from terminal to this hosted REST API:
Spinning up a Docker container from the pre-built did-resolver Docker image on Github is as simple as the command below:
To configure the resolver, modify the values under the environment section of the Docker Compose file. The values that can be edited are as follows:
MAINNET_ENDPOINT : Mainnet Network endpoint as string with the following format" <networks>,<useTls>,<timeout>. Example: grpc.cheqd.net:443,true,5s
networks: A string specifying the Cosmos SDK gRPC endpoint from which the Resolver pulls data. Format: <resource_url>:<resource_port>
useTls: Specify whether gRPC connection to ledger should use secure or insecure pulls. Default is true since gRPC uses HTTP/2 with TLS as the transport mechanism.
timeout: Timeout (in seconds) to wait for before any ledger requests are considered to have time out.
TESTNET_ENDPOINT : Testnet Network endpoint as string with the following format" <networks>,<useTls>,<timeout>. Example: grpc.cheqd.network:443,true,5s
RESOLVER_LISTENER`: A string with address and port where the resolver listens for requests from clients.
LOG_LEVEL: debug/warn/info/error - to define the application log level.
Our DID Resolver uses the Cosmos gRPC endpoint from cheqd-node to fetch data. Typically, this would be running on port 9090 on a cheqd-node instance.
You can either use public gRPC endpoints for the cheqd network (such as the default ones mentioned above), or point it to your own cheqd-node instance by enabling gRPC in the app.toml configuration file on a node:
Note: If you're pointing a DID Resolver to your own node instance, by default cheqd-node instance gRPC endpoints are not served up with a TLS certificate. This means the useTls property would need to be set to false, unless you're otherwise using a load balancer that provides TLS connections to the gRPC port.
You can build your own image using docker build
Uncomment the build section in the docker/docker-compose.yml file. This relies on the Dockerfile above but uses Docker Compose syntax to customise the build:
Make sure you comment out the pre-existing image property that pulls in a container image from Github Container Registry, as shown above.
You can also do just a build with:
The instructions to configure and run the resolver are the same as when using the pre-built image.
did:cheqd via Universal ResolverThe resolver.cheqd.net API endpoint is run by the cheqd team and only handles did:cheqd credentials.
If you want to resolve DIDs from multiple DID methods, the Universal Resolver project provides a multi DID method resolver.
You can make resolution requests to a pre-existing Universal Resolver endpoint, such as dev.uniresolver.io, to their REST API endpoint:
You can also run your own instance of Universal Resolver, using the Docker Compose file of the project.
The Universal Resolver quick start guide provides instructions on how to do this:
Service for resolving DIDs and dereferencing DID-Linked Resources
DID methods are expected to provide .
The is designed to implement the for method. It also supports full DID URL dereferencing, .
Our DID resolver is a package which can be implemented directly into clients' own infrastructure as a library written in Golang. This provides full support for cheqd's resolver, and can be run by anyone, creating a secure and client-controlled environment for resolving cheqd DIDs.
Our DID resolver is also available as , a project maintained by DIF which hosts drivers of many different DID Resolvers in a compatible and easy-to-integrate format (Docker Containers).
Having multiple implementations of a DID Resolver accommodates for different clients, developers and customers - each with different needs. The flexibility and modular architecture exhibited here will allow cheqd DIDs to be resolved simply and securely within closed, controlled ecosystems with tight security protocols - as well as by community members who want to try our our identity functionality. Catering to both parties' needs makes the cheqd DID Resolver valuable in both everyday use, and for enterprise use.
You can see our resolver in action, resolving our first DID here: