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.
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 — 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 |
|---|---|---|
| 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 | DID + VC issuance at protocol layer; slower 2024–26 shipment pace per brief |
| 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.