#dusk $DUSK @Dusk
I spent some time looking at Dusk’s Citadel layer, and this is one of those details that makes more sense the longer I think about it.
The idea isn't simply hiding identity data. Citadel is designed around selective disclosure: a user can prove a required attribute without exposing every piece of personal information behind it.
Technically, that creates a cleaner separation between verification and data exposure.
For a regulated financial workflow, that could matter a lot. An application may need to know that an investor satisfies a condition, but it doesn't necessarily need the investor's entire identity record sitting in every transaction flow.
What I like here is the specificity of the problem Dusk is trying to solve.
The real test is whether applications can make this verification process simple enough for actual users.

What you do if you have Dusk? Sell or buy more?

.