ThisDID Directory
every DID method, measured
← Resolver Directory Providers Analytics API docs
did:dht
TS Universal Resolver driverNew · under test

Ed25519-signed DNS packets in BitTorrent's Mainline DHT, verified against the DID's own key.

Live scores

Popularity 30
Availabilityno data
ThisDID canary 24hno data
resolutions: 24h 0 · 7d 0 · 30d 23 · from /analytics

Routing

ThisDID→godiddy→archon

Probation verification

No upstream anywhere resolves did:dht — ThisDID is the only public route. Results are honestly stamped verification: unverified (upstreamUnsupported) until an independent verifier exists.

Facts

JSON API
/directory/api/methods/dht
Last reviewed
2026-08-24

Research

The DID's suffix IS the Ed25519 identity key: one Pkarr relay GET returns a BEP44 mutable item whose signature the driver verifies against that key before reconstructing the document from its DNS records — a relay can withhold but never forge. The spec (DIF, W3C-registered) is complete and the Mainline + Pkarr rails are live, but records expire without republishing and the method's main publisher ecosystem (TBD's Web5) shut down, so real population is sparse: an absent record answers notFound, deliberately not the spec's identity-key-only fallback, which would resurrect expired or deactivated DIDs. No upstream anywhere resolves did:dht (Archon answers 501), so results are honestly stamped unverified.

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