@Dusk #dusk $DUSK I've been looking deeper into Dusk's identity layer, and Citadel is probably one of the more interesting pieces I've come across.
The basic idea sounds simple: prove you're eligible without handing over your entire identity.
Citadel 2 uses zero-knowledge proofs so a user can prove they hold a valid credential without putting the personal details or even the exact credential used on-chain. The blockchain verifies the proof, while the actual attributes can stay private.
The part that actually caught my attention is how much control stays with the user.
A service can require something specific — residency, an age bracket, accreditation, whatever its policy needs — without getting access to everything else sitting inside the credential. And the service provider still decides which credentials and attributes it accepts.
That matters a lot more when you think about regulated assets.
KYC usually creates this awkward tradeoff: institutions need enough information to verify eligibility, but users don't necessarily want every platform storing copies of their personal documents.
Dusk is basically trying to replace "show me your identity" with "prove that you meet the requirement."
Honestly, that's a much more interesting use of zero-knowledge than just hiding transaction amounts.
The real question I'm watching now is whether selective disclosure like this can become practical enough for real financial workflows, where compliance requirements aren't theoretical and every edge case matters.
Reason: 15m chart shows a sharp rejection from 1.1556 with two strong bearish candles. Price is now around the EMA25, so avoid chasing; better entry on a small bounce.
Invalidation: 15m close above 1.095 Leverage: 2–3x max
A clean rejection around 1.06–1.07 would be the better trigger.