Been working through Dusk Network's #dusk @Dusk confidentiality stack this afternoon. Specifically the gap between how Hedger and Citadel are supposed to interact — and what the DuskEVM testnet actually shows right now.
The design premise is clean. Hedger handles the privacy side via homomorphic encryption and ZK proofs. In-browser proving is running sub-2 seconds on the active testnet. You deploy a confidential transaction, counterparties and amounts stay hidden. That part is live. Institutions can execute without leaking position data to the market. Real, not theoretical.
Then there's Citadel. The other half — the ZK-KYC selective disclosure layer where a regulator or auditor gets on-demand access without the entire ledger going transparent. Prove eligibility, prove compliance status, reveal a specific transaction to a specific party when required. The piece that's supposed to make confidential execution acceptable inside a regulated framework, not just inside crypto.
Here's the thing though. The current status on Citadel is pretty straightforward: SDK exists but needs updates for the current Rusk model. So on a testnet where Hedger is already handling live confidential flows $DUSK, the selective oversight layer is still being updated for compatibility. The privacy half is shipping. The regulatory access half is behind it.
I keep thinking about that. The bridge is still closed post-Aug 16 incident, DuskEVM mainnet timing pending, and Hedger is already ahead of Citadel on the deployment curve.
Confidentiality without the auditing channel... at what point does that just look like a privacy chain with better marketing?
$DUSK
The design premise is clean. Hedger handles the privacy side via homomorphic encryption and ZK proofs. In-browser proving is running sub-2 seconds on the active testnet. You deploy a confidential transaction, counterparties and amounts stay hidden. That part is live. Institutions can execute without leaking position data to the market. Real, not theoretical.
Then there's Citadel. The other half — the ZK-KYC selective disclosure layer where a regulator or auditor gets on-demand access without the entire ledger going transparent. Prove eligibility, prove compliance status, reveal a specific transaction to a specific party when required. The piece that's supposed to make confidential execution acceptable inside a regulated framework, not just inside crypto.
Here's the thing though. The current status on Citadel is pretty straightforward: SDK exists but needs updates for the current Rusk model. So on a testnet where Hedger is already handling live confidential flows $DUSK, the selective oversight layer is still being updated for compatibility. The privacy half is shipping. The regulatory access half is behind it.
I keep thinking about that. The bridge is still closed post-Aug 16 incident, DuskEVM mainnet timing pending, and Hedger is already ahead of Citadel on the deployment curve.
Confidentiality without the auditing channel... at what point does that just look like a privacy chain with better marketing?
$DUSK
