{
  "id": "btcr2",
  "name": "did:btcr2",
  "status": "upstream",
  "probation": false,
  "summary": "The modern successor to did:btcr (formerly did:btc1), anchored in Bitcoin transactions.",
  "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.",
  "links": [
    {
      "label": "did:btcr2 spec",
      "url": "https://dcdpr.github.io/did-btcr2/"
    },
    {
      "label": "dcdpr/did-btcr2",
      "url": "https://github.com/dcdpr/did-btcr2"
    },
    {
      "label": "TypeScript implementation",
      "url": "https://github.com/dcdpr/did-btcr2-js"
    },
    {
      "label": "W3C DID Methods registry",
      "url": "https://www.w3.org/TR/did-extensions-methods/"
    }
  ],
  "lastReviewed": "2026-08-28",
  "chain": [
    "ThisDID",
    "godiddy",
    "archon"
  ],
  "scores": {
    "resolutions24h": 0,
    "resolutions7d": 264,
    "resolutions30d": 268,
    "popularity": 53,
    "availability": 98,
    "canary24h": null,
    "verificationMatch30d": 0,
    "verificationMismatch30d": 0
  }
}