{
  "id": "webs",
  "name": "did:webs",
  "status": "upstream",
  "probation": false,
  "summary": "did:web secured with KERI key event logs (did:webs).",
  "research": "The ToIP KERI Suite WG spec (v0.10.3, still draft even though the underlying KERI/ACDC/CESR specs were ratified in January 2026) is strict by design: a resolver MUST fetch both did.json and keri.cesr, MUST verify the full key event log, and MUST fail on any mismatch — serving did.json alone degrades did:webs to plain did:web security and is explicitly non-conformant. A faithful TypeScript verifier means a clean-room CESR parser plus KEL state machine (~4–5k lines against keripy's ~25k-line reference; signify-ts is a KERIA client without the validator and drags runtime-WASM libsodium, which Workers block). With adoption still tutorial-grade — GLEIF's own testnet endpoint is down and no production did:webs is discoverable — ThisDID serves the method upstream, where Godiddy resolves the canonical tutorial DID via GLEIF's reference driver in ~200ms. An edge driver waits on production publishers or a maintained TS KEL verifier.",
  "links": [
    {
      "label": "did:webs spec (ToIP)",
      "url": "https://trustoverip.github.io/kswg-did-method-webs-specification/"
    },
    {
      "label": "GLEIF reference resolver",
      "url": "https://github.com/GLEIF-IT/did-webs-resolver"
    },
    {
      "label": "W3C DID Methods registry",
      "url": "https://www.w3.org/TR/did-extensions-methods/"
    }
  ],
  "lastReviewed": "2026-08-28",
  "chain": [
    "ThisDID",
    "godiddy",
    "archon"
  ],
  "dif": {
    "dockerDriver": {
      "image": "gleif/did-webs-resolver-service:0.2.7",
      "repo": "https://github.com/GLEIF-IT/did-webs-resolver",
      "hub": "https://hub.docker.com/r/gleif/did-webs-resolver"
    }
  },
  "scores": {
    "resolutions24h": 0,
    "resolutions7d": 1,
    "resolutions30d": 8,
    "popularity": 21,
    "availability": 100,
    "canary24h": null,
    "verificationMatch30d": 0,
    "verificationMismatch30d": 0
  }
}