Solidus Network
Solidus vs KILT Protocol
KILT is the architectural precedent did:solidus's own W3C registry submission cites — same category, same DID-method model, six years earlier. The gap between us is production maturity, not design, and KILT has earned the word "audited" in a way we have not.
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 KILT Protocol does better
- Six-plus years live with an audited codebase and no major exploits — the brief's own words. KILT is the one vendor in this comparison where "audited" is a sourced fact about them, not a claim we get to make about ourselves.
- did:kilt is registered in the W3C DID Method Registry — the actual precedent did:solidus's own PR #713 cites.
- Polkadot shared-security model: KILT inherits relay-chain security and skips a class of L1 launch risk that a from-scratch chain like Solidus still carries.
- Real EU government engagement: small-scale German ministry-level pilots and university research relationships (TU Munich and others) — six years of EU-sovereign credibility Solidus does not have yet.
- SocialKYC is a shipped, roughly five-year-iterated KYC product — direct precedent for what verify.solidus.network is still building toward.
Where Solidus is different
- No parachain coupling: HotStuff BFT gives Solidus direct control of its own consensus instead of depending on the Polkadot relay chain, per the brief's own architectural read.
- Native BBS+, SD-JWT VC, and OID4VCI/OID4VP shipped end-to-end (unaudited, conceded up front) — the brief itself describes KILT's 2024–26 standards shipment pace as slower.
- did:solidus is registered in the W3C DID Method Registry (PR #713, merged 2026-07-04) — the same submission that cites did:kilt as its precedent.
Side by side
| Feature | Solidus | KILT Protocol |
|---|---|---|
| Production maturity | Public testnet, unaudited | 6+ years live, audited, no major exploitsKILT Protocol wins |
| DID method registered in W3C registry | did:solidus — registered 2026-07-04, citing did:kilt as precedent | did:kilt — registered years earlierKILT Protocol wins |
| Consensus / security model | HotStuff BFT — 4-node dev committee, no shared-security dependency | Substrate parachain — Polkadot shared security |
| Credential standards shipped | BBS+, SD-JWT VC, OID4VCI/OID4VP end-to-end (unaudited) | DID + VC issuance at protocol layer; slower 2024–26 shipment pace per brief |
| KYC / identity-verification product | verify — one of 7 live testnet products | SocialKYC — shipped, ~5 years of production iterationKILT Protocol wins |
| Government / institutional pilots | None | German ministry-level pilots (small-scale, per brief)KILT Protocol wins |
| Token / fee model | None — no token exists | $KILT required for fees, registration, staking, governance |
Check it yourself
curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 → merged: true, merged_at 2026-07-04 — the same registry entry cites did:kilt as prior art.