Here's something almost everyone misses about @Dusk : Zedger, Citadel, and Hedger get thrown around like three separate buzzwords. They're not. They're one compliance architecture, each quietly solving a different layer of the same problem.
Zedger handles the asset itself. Built on Phoenix's UTXO privacy model, it governs how securities are minted, burned, and force-transferred — the legal mechanics issuers actually need for regulated tokens.
Citadel handles the person. It manages licenses and identity, proving an investor is eligible (KYC'd, accredited, jurisdiction-cleared) without exposing their full identity on-chain.
Hedger handles the newer EVM side. Using homomorphic encryption plus zero-knowledge proofs, it keeps balances and transfers encrypted end-to-end on DuskEVM, while staying fully auditable by design.
Put them together and the picture clicks: Citadel proves who can transact, Zedger governs what the asset legally does, and Hedger keeps how much moved private but verifiable. Not three features. One compliant pipeline.
$DUSK #dusk
Zedger handles the asset itself. Built on Phoenix's UTXO privacy model, it governs how securities are minted, burned, and force-transferred — the legal mechanics issuers actually need for regulated tokens.
Citadel handles the person. It manages licenses and identity, proving an investor is eligible (KYC'd, accredited, jurisdiction-cleared) without exposing their full identity on-chain.
Hedger handles the newer EVM side. Using homomorphic encryption plus zero-knowledge proofs, it keeps balances and transfers encrypted end-to-end on DuskEVM, while staying fully auditable by design.
Put them together and the picture clicks: Citadel proves who can transact, Zedger governs what the asset legally does, and Hedger keeps how much moved private but verifiable. Not three features. One compliant pipeline.
$DUSK #dusk