every DID method, measured
OwnYourData OYDID — self-verifying identifiers over provenance logs.
Live scores
Probation verification
New driver under the verification guarantee: ThisDID resolutions are double-checked in parallel against an independent upstream — for did:oyd, oyd — until the live match-rate earns graduation.
DIF Universal Resolver docker driver
did:oyd has an approved and merged resolver docker container in the DIF Universal Resolver repository.
- Driver source
- https://github.com/OwnYourData/oydid
Facts
- Network
- OYDID (provenance log)
- Try it live
- did:oyd:zQmaBZTghndXTgxNwfbdpVLWdFf6faYE4oeuN2zzXdQt1kh
- JSON API
- /directory/api/methods/oyd
- Last reviewed
- 2026-08-28
Research
The identifier commits to its own document: a base58btc multihash of the stored record, whose provenance log (create/update/revoke entries, each Ed25519-signed and hash-chained) lets any resolver verify the full history from public HTTPS endpoints — no ledger involved. OwnYourData (EU NGI-funded) remains actively developed in 2026 and its public repo and resolver answer in well under a second. ThisDID routes did:oyd to resolver.ownyourdata.eu as the authoritative first hop; notably, the DIF Universal Resolver's oyd driver is a pure proxy to that same resolver and Godiddy does not support the method, so today nobody independently verifies did:oyd. All verification primitives (SHA-256 multihash, canonical-JSON log hashing, Ed25519) are reproducible with WebCrypto alone, making a local verifying driver — the only independent check of the method anywhere — a planned small build.