Sarah — a compliance officer at an EU fund — just received an email from a trader:
“I urgently need to prove I’m an accredited investor to buy tokenized bonds. Here’s my passport scan + household registration + a photo of my entire family at the beach last year!”
Sarah looks at the 47MB file and sighs:
“Great… another internal audit because of a potential data leak.”
And on a public blockchain, it can get even worse: the moment you prove your eligibility, everyone may be able to see sensitive information about your balances and strategy.
But on @Dusk_Foundation , it’s different.
Dusk supports selective disclosure through Citadel: prove only the specific attribute required — such as residency or accredited investor status — without exposing the underlying data.
Combined with DuskEVM testnet, which is already live and supports Solidity + Hardhat deployments, and Hedger — a privacy module using homomorphic encryption (ElGamal over ECC) and zero-knowledge proofs — the architecture is designed for privacy-preserving compliance.
According to the project’s official documentation, lightweight circuits can generate proofs client-side in under 2 seconds, while balances and amounts remain encrypted end-to-end and can still be audited when regulators require it.
Settlement runs on DuskDS with Succinct Attestation, using a committee-based PoS model.
Key parameters stated in the docs and whitepaper:
1/ Minimum stake: 1,000 DUSK
2/ Epoch duration: 2,160 blocks
3/ Committee credits: 64
4/ Maximum iterations: 50
5/ Deterministic finality within seconds
Phoenix enables shielded transfers, while Moonlight provides transparency — essentially, privacy where needed and transparency where useful.
Sarah only needs to verify the proof.
The trader keeps the underlying data private.
No more sending the compliance team an entire family photo album just to prove one eligibility requirement. 🔐
$DUSK #dusk $SNDK $AKE
“I urgently need to prove I’m an accredited investor to buy tokenized bonds. Here’s my passport scan + household registration + a photo of my entire family at the beach last year!”
Sarah looks at the 47MB file and sighs:
“Great… another internal audit because of a potential data leak.”
And on a public blockchain, it can get even worse: the moment you prove your eligibility, everyone may be able to see sensitive information about your balances and strategy.
But on @Dusk_Foundation , it’s different.
Dusk supports selective disclosure through Citadel: prove only the specific attribute required — such as residency or accredited investor status — without exposing the underlying data.
Combined with DuskEVM testnet, which is already live and supports Solidity + Hardhat deployments, and Hedger — a privacy module using homomorphic encryption (ElGamal over ECC) and zero-knowledge proofs — the architecture is designed for privacy-preserving compliance.
According to the project’s official documentation, lightweight circuits can generate proofs client-side in under 2 seconds, while balances and amounts remain encrypted end-to-end and can still be audited when regulators require it.
Settlement runs on DuskDS with Succinct Attestation, using a committee-based PoS model.
Key parameters stated in the docs and whitepaper:
1/ Minimum stake: 1,000 DUSK
2/ Epoch duration: 2,160 blocks
3/ Committee credits: 64
4/ Maximum iterations: 50
5/ Deterministic finality within seconds
Phoenix enables shielded transfers, while Moonlight provides transparency — essentially, privacy where needed and transparency where useful.
Sarah only needs to verify the proof.
The trader keeps the underlying data private.
No more sending the compliance team an entire family photo album just to prove one eligibility requirement. 🔐
$DUSK #dusk $SNDK $AKE