did:solidus
Also called Solidus DID method, the Solidus method
did:solidus is the DID method Solidus authored and operates. Every identifier under it has the form did:solidus:<address>, where <address> is derived deterministically from an Ed25519 public key:
Ed25519 public key (32 bytes)
→ BLAKE3 hash
→ first 20 bytes
→ Base58-encode
→ did:solidus:<result>
The same key always produces the same DID. Creating one submits a DidCreate transaction to the Solidus chain; the resulting DID Document lives in the chain's state tree and is resolvable by anyone (see DID Resolution).
What "registered" means, and what it doesn't
did:solidus is registered in the W3C DID Method Registry, formally, the DID Specification Registries maintained at github.com/w3c/did-extensions. Concretely: pull request #713 merged into that repository on 2026-07-04, and methods/solidus.json on main carries "status": "registered".
That's a real, independently checkable fact, and a narrow one. It is not a W3C standard, not a W3C endorsement, and not a certification of anything did:solidus does. The standard is DID Core (see the DID entry), a W3C Recommendation that defines what any method has to look like. Registering a method is closer to getting a project listed in a public index than to earning a stamp of approval on its design. Most identity startups only implement specs like this one; getting an actual method merged into the registry is a smaller, rarer step, but it should never be inflated past what it actually is.
Where it comes from
W3C wrote DID Core and runs the registration process. Solidus wrote the did:solidus method specification, the on-chain registry backing it, and the resolver serving it.
Solidus status
Shipped and registered, testnet-only. Every did:solidus DID that exists today lives on Solidus's public testnet. There is no mainnet, and nothing here implies one.
Proof you can run yourself, no account needed: curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 | jq '{state,merged,merged_at}' returns merged: true, 2026-07-04. Then resolve any did:solidus DID against rpc.solidus.network (exact command in the DID Resolution entry).
Where it comes from
Someone else specified this. Solidus wrote an implementation of it.
did:solidus is a DID method registered under W3C DID Core's method-extension mechanism (w3c/did-extensions PR #713, merged 2026-07-04; methods/solidus.json on main carries status "registered"). DID Core itself (the standard that makes methods possible in the first place) is a W3C Recommendation Solidus did not write. The method specification and its implementation (key derivation, on-chain registry, resolver) are Solidus's own work.
How to check this
Running in production today.
curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 | jq '{state,merged,merged_at}' returns merged:true, 2026-07-04. Then resolve a live DID against rpc.solidus.network, command in the DID Resolution entry.