#dusk
Have you ever thought if you could pass KYC without handing over your personal data? 👀
Let’s dive into Dusk Citadel 2 together... In many digital systems, proving you’re eligible often means revealing more information than necessary. Your identity. Your credentials. Sometimes even details that have nothing to do with the service you’re trying to access.
Citadel 2 takes a different $DUSK approach through zero-knowledge proofs.
A trusted License Provider first verifies the user and issues a signed license. Later, when access is needed, the user can generate a proof showing they hold a valid registered license without revealing the personal details behind it or which specific license was used.
The interesting part is the separation between verification and disclosure in DUSK.
The application gets the answer it needs without getting the entire identity attached to that answer. I think this matters especially for regulated financial applications where compliance still needs strong verification but users shouldn't have to expose unnecessary information on-chain.
That makes Citadel 2 more than an identity tool in my view. It represents a different way to think about digital credentials.
If blockchain can verify eligibility without collecting everything about you, why should it need to know everything at all?
#dusk @Dusk
Have you ever thought if you could pass KYC without handing over your personal data? 👀
Let’s dive into Dusk Citadel 2 together... In many digital systems, proving you’re eligible often means revealing more information than necessary. Your identity. Your credentials. Sometimes even details that have nothing to do with the service you’re trying to access.
Citadel 2 takes a different $DUSK approach through zero-knowledge proofs.
A trusted License Provider first verifies the user and issues a signed license. Later, when access is needed, the user can generate a proof showing they hold a valid registered license without revealing the personal details behind it or which specific license was used.
The interesting part is the separation between verification and disclosure in DUSK.
The application gets the answer it needs without getting the entire identity attached to that answer. I think this matters especially for regulated financial applications where compliance still needs strong verification but users shouldn't have to expose unnecessary information on-chain.
That makes Citadel 2 more than an identity tool in my view. It represents a different way to think about digital credentials.
If blockchain can verify eligibility without collecting everything about you, why should it need to know everything at all?
#dusk @Dusk