Solidus Identity
Solidus Identity vs Credo TS
Credo TS is excellent, EUDI-embedded infrastructure — and it's a library. Every project built on it still stands up its own network, issuer, and trust registry. Solidus ships all three already running.
Where Solidus is different
- Credo has no network, no L1, no chain-anchored issuance, and no revenue model of its own, per its own brief — Solidus ships network, SDK, and issuer together.
- did:solidus is registered in the W3C DID Method Registry and resolves on a live testnet RPC, which a network-agnostic framework doesn't provide by itself.
- Native KYC issuance via Verify in the same stack — a framework alone doesn't issue credentials; you still have to build or buy that layer.
Side by side
| Feature | Solidus | Credo TS |
|---|---|---|
| What it is | Network + SDK + native KYC issuer, one stack | TypeScript framework only (DIDComm/VC); no network of its own |
| Chain-anchored trust | did:solidus resolves on a live testnet | None — network-agnostic framework, per brief |
| Native KYC / credential issuance | Native, via Verify | Not offered — framework only |
| Vertical completeness | One vendor: network, SDK, and issuer together | SDK only; network, issuer, and trust registry left to the implementer |
Check it yourself
did:solidus is registered in the W3C DID Method Registry: curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 → state: closed, merged: true, merged_at: 2026-07-04.