Research

Digital Contract Design's successor to did:btcr, presented as did:btc1 through 2025 before the rename. The spec is very active but self-declared draft with possible breaking changes, and it is not yet in the W3C DID method registry. Identifiers are bech32m (a secp256k1 key or a genesis-document hash); document updates are discovered by scanning beacon addresses over Esplora-style HTTPS APIs and verified with hash-chained JSON Patches and BIP-340 Schnorr signatures — mechanics a Worker driver could implement, and an official TypeScript implementation exists (@did-btcr2/method, noble/scure-based). Adoption is test-network-only so far (mutinynet/signet vectors; no mainnet DIDs found in the wild), so ThisDID serves it upstream — both Godiddy and the DIF Universal Resolver resolve the mutinynet canary today — and a verifying edge driver waits on W3C registration or real mainnet usage.