In my last post about $DUSK I ended with a question I couldn't answer yet: is selective disclosure actually practical, or just an elegant idea on paper? I spent this week trying to answer it, and the answer seems to have a name: Citadel.

Citadel is @Dusk _Foundation's approach to identity and compliance. Instead of handing over full KYC documents to every platform, a user holds credentials and proves specific claims about them using zero-knowledge proofs. A venue can verify that I'm eligible to trade a regulated asset without ever seeing the underlying documents. Eligibility becomes something you prove, not something you expose.

What makes me take this seriously is where it sits in the stack. Compliance isn't bolted on as a policy layer that an application might skip; it's expressed in the same proof system the #dusk chain already uses for transactions. The recent developer tooling around wallet connectivity suggests the team is now working on the unglamorous part: making this usable, not just possible.

My honest reservation is adoption. Cryptographic eligibility proofs only matter if regulated venues accept Dusk's model as satisfying their obligations, and that's a legal question as much as a technical one.
So this is where I end the campaign: not convinced, but genuinely curious. If regulated finance ever moves on-chain, I suspect it will look less like hiding data and more like proving claims. That's the experiment $DUSK is running.