Reject the exposure of personal data! Decoding Citadel's "Issuer-Holder-Verifier" triadic architecture.
Hello, readers. Did everyone think Citadel was just a privacy mask? I see a more intricate design of "three roles" in the technical details:
Issuer: Banks or compliant institutions responsible for verifying your identity and providing you with an encrypted "certificate" on the chain.
Holder: That's you. This certificate resides in your wallet, and only you can decide when to present it.
Verifier: Like Dusk Trade. It initiates challenges, and you respond with ZK proofs.
The key point is: The verifier can only see a "Yes/No" result and will never access your original personal data.
A little note from me: This process returns identity sovereignty to the users. This kind of "selective disclosure" implementation is the golden standard for future RWA platforms handling identity verification.
$DUSK #dusk #Citadel #SSI #ZKP #Privacy @Dusk
