Solidus Identity

Solidus Identity vs walt.id

walt.id gives you a full OID4VC issuer/wallet/verifier stack to run yourself. Solidus gives you the same standards plus the network and the KYC issuer already running underneath.

Solidus is a public testnet: no mainnet, no token, no external audit, and no paying customer. Every claim below is checkable; none of them are a substitute for the certifications an incumbent already holds.

What walt.id does better

Where Solidus is different

Side by side

Solidus compared with walt.id. Rows marked as won by walt.id are noted in the final column.
FeatureSoliduswalt.id
Developer adoptionNo published number45,000+ developers (self-reported)walt.id wins
Deployment referenceNoneAccenture, IBM, Mastercard, Air NZ; 20M-citizen Thailand rolloutwalt.id wins
Production maturityPublic testnet, unaudited, no paying customerProduction, multi-year enterprise usewalt.id wins
ArchitectureL1 network + SDK + native KYC issuer, one stackFull OID4VC issuer/wallet/verifier OSS stack; no L1 of its own
Chain-anchored trustdid:solidus resolves on a live testnetNone — framework only, per brief
Native KYC / credential issuanceNative, via VerifyNot offered as part of the stack
License / hosted pathApache-2.0 protocol, no gated tierFree OSS core + paid Cloud tier for hosted use
Standards statusdid:solidus registered in W3C DID Method Registry; DIF Associate MemberEUDI-aligned OID4VC stack; no registered DID method of its own

Check it yourself

Resolve a did:solidus DID against the live testnet RPC at rpc.solidus.network, or verify the registry entry: curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 → merged: true.

Compare the receipts, not the pitch.