DID Methods supported today:
- did-tezos: architected by Spruce, did:tezos supports a powerful and robust multi-layer architecture. This includes support for "implicit" (unpublished) DIDs, on-chain (published) DIDs, DIDs that begin their lives as the former and become the latter, and additional metadata local to specific networks, including Sidetree networks.
- did-key: the classic deterministic method for generating DIDs deterministically from a JWK file or other local key material
- did-pkh: a did-key-like deterministic method for generating DIDs from blockchain addresses encoded and validated according to the emerging "CAIP" cross-chain addressing specification
- did-web: a DID method for publishing a DID document to a domain's "/.wellknown/" configuration directory, to be resolved over HTTPS
- did-webkey: a DID method designed in-house for deterministically deriving DID Documents from key material exposed by major web APIs; while we implemented it specifically for the SSH and GPG keys exposed and consumed by GitHub's APIs, it could readily be extended to analogous contexts.
- did:onion: a DID method designed to be resolved over Tor-style onion routing
- did-ethr: the classic Ethereum-based DID method at the heart of uPort, Veramo, and many web3 dApp projects (implicit only; main-net indexing & resolution coming soon)
- did-sol: the native DID method of the Solana blockchain and DeFi ecosystem
Proof types verifiable so far: