#dusk $DUSK @Dusk Today I went through the actual GitHub repos behind Citadel instead of just reading the announcement page, and the gap between the two was bigger than I expected.
Citadel was formally presented back in January 2023 a full research paper, a working protocol design, three defined parties (user, license provider, service provider), and a private NFT model built specifically to solve a real problem other SSI systems had: even when zero-knowledge proofs hide the content of a credential, the credential itself is usually stored as a public, traceable on-chain value. Citadel's whole contribution was fixing that leak.
The tooling exists too — Moat, the Citadel SDK, is live on GitHub, with a CLI and remote-access API for building on the protocol, requiring a running Rusk node and connected wallet. That's not vaporware; the code is real and open.
But checking the current documentation hub, I found a note that stopped me: the SDK "exists but needs updates for the current Rusk model." That's a meaningful gap between "protocol was designed and published" and "protocol is actively maintained against the network's current implementation." A three-year-old cryptographic design being technically sound doesn't tell you whether the integration layer keeps pace with a chain that's since gone through a multilayer architecture shift.
I don't think that means Citadel is abandoned — research-grade privacy tooling often sits dormant between bursts of integration work, especially while the team's attention was on DuskDS/DuskEVM/DuskVM. But it does mean citing Citadel as evidence of "live compliance infrastructure" right now overstates where the SDK actually is.
What I'm tracking going forward: whether Moat gets a commit updating it for the current Rusk model, whether any named institution or KYC provider actually deploys Citadel in production rather than referencing it as a use case, and whether Citadel gets folded explicitly into the DuskEVM/DuskVM roadmap or stays a standalone 2023 artifact.
Citadel was formally presented back in January 2023 a full research paper, a working protocol design, three defined parties (user, license provider, service provider), and a private NFT model built specifically to solve a real problem other SSI systems had: even when zero-knowledge proofs hide the content of a credential, the credential itself is usually stored as a public, traceable on-chain value. Citadel's whole contribution was fixing that leak.
The tooling exists too — Moat, the Citadel SDK, is live on GitHub, with a CLI and remote-access API for building on the protocol, requiring a running Rusk node and connected wallet. That's not vaporware; the code is real and open.
But checking the current documentation hub, I found a note that stopped me: the SDK "exists but needs updates for the current Rusk model." That's a meaningful gap between "protocol was designed and published" and "protocol is actively maintained against the network's current implementation." A three-year-old cryptographic design being technically sound doesn't tell you whether the integration layer keeps pace with a chain that's since gone through a multilayer architecture shift.
I don't think that means Citadel is abandoned — research-grade privacy tooling often sits dormant between bursts of integration work, especially while the team's attention was on DuskDS/DuskEVM/DuskVM. But it does mean citing Citadel as evidence of "live compliance infrastructure" right now overstates where the SDK actually is.
What I'm tracking going forward: whether Moat gets a commit updating it for the current Rusk model, whether any named institution or KYC provider actually deploys Citadel in production rather than referencing it as a use case, and whether Citadel gets folded explicitly into the DuskEVM/DuskVM roadmap or stays a standalone 2023 artifact.