every DID method, measured
← Resolver Directory Providers Analytics API docs
did:indy
Upstream routedDocker

Hyperledger Indy ledger DIDs — served upstream; a local driver has no trustworthy transport.

Live scores

Popularity 53
Availability 98%
ThisDID canary 24hno data
resolutions: 24h 0 · 7d 261 · 30d 270 · from /analytics

Routing

DIF Universal Resolver docker driver

did:indy has an approved and merged resolver docker container in the DIF Universal Resolver repository.

Docker image
universalresolver/driver-did-indy:latest
Driver source
https://github.com/decentralized-identity/uni-resolver-driver-did-indy

Facts

JSON API
/directory/api/methods/indy
Last reviewed
2026-08-28

Research

Sovrin MainNet stopped accepting writes on 31 March 2025 and the Sovrin Foundation dissolved on 21 May 2025 — but its nodes still answer reads (live nymResponse observed August 2026), and the network story did not end there: Indicio MainNet remains actively written (a fresh NYM landed mid-August 2026) while IDunion looks dead and BCovrin/CANdy expose no browse APIs. The ecosystem's growth migrated to cheqd (ThisDID local driver) and did:webvh. A local driver stays parked on transport grounds, not liveness: Indy nodes speak ZeroMQ only, nobody hosts a public indy-vdr proxy, and IndyScan's HTTP API is Indicio-only Elasticsearch data without state proofs — an edge driver would be an unverified scraper with worse coverage than the upstream chain, which resolves both sovrin and indicio namespaces in about a second today.

Links

Curated method research + live measured scores · A DIF Identifiers & Discovery Working Group project advancing the Universal Resolver and interoperable DID methods · Resolver · Analytics · Status · JSON API · API docs · Source