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.

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 Credo TS does better

Where Solidus is different

Side by side

Solidus compared with Credo TS. Rows marked as won by Credo TS are noted in the final column.
FeatureSolidusCredo TS
EUDI implementation pedigreeNone yetEmbedded in the FUNKE-winning EasyPID prototypeCredo TS wins
Institutional stewardshipDIF Associate MemberOpenWallet Foundation-stewardedCredo TS wins
Standards coverage shippedDID, VC, SD-JWT VC, BBS+ (testnet, unaudited)DIDComm v1/v2, OID4VC, AnonCreds, SD-JWT VC, BBS+Credo TS wins
Production maturityPublic testnet, unaudited, no paying customerActive multi-year releases, embedded in a real EUDI pilotCredo TS wins
What it isNetwork + SDK + native KYC issuer, one stackTypeScript framework only (DIDComm/VC); no network of its own
Chain-anchored trustdid:solidus resolves on a live testnetNone — network-agnostic framework, per brief
Native KYC / credential issuanceNative, via VerifyNot offered — framework only
Vertical completenessOne vendor: network, SDK, and issuer togetherSDK 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.

Compare the receipts, not the pitch.