Hedger: four cards—an MCQ question on the privacy track turned into a multi-select question
Privacy has been handled for over ten years, and what users still face is a single-choice question:
Either everything is hidden, or everything is naked.
Zcash uses zk-SNARKs, Monero uses ring signatures—both the sender/receiver and the amounts are cleanly concealed.
After you hide everything, then what?
Regulators want to see it, but it can’t be explained; institutions want to use it, but they can’t integrate it.
What Hedger by Dusk aims to do is to change this single-choice question into a multi-select one.
First card: holdings, balances, and amounts—end-to-end encryption.
Whatever is in your address, and how much you transferred, is accounted for on-chain as usual, but outsiders can’t see it.
Second card: auditability under regulation.
Transactions are designed to be fully auditable; when compliance checks need to look, they can.
This is the missing piece in traditional privacy coins: everyday use doesn’t expose you, but if something goes wrong, you can explain it.
Third card: generate proofs in the browser in under two seconds.
Lightweight circuits run on the client; for the user, it feels like a normal transaction—
no hardware barrier, no long waiting.
Fourth card: lay the groundwork for the soon-to-be-deployed order book of obfuscation.
This is a key facility for institutional trading—preventing market manipulation—so trading intentions and risk exposure can’t be discovered in advance.
Note: this card is laying the road, not taking the stage yet.
With four cards in place, Hedger fills the oldest gap in the privacy track:
privacy coins for individuals are plentiful, but this is the first EVM privacy engine that doesn’t trade compliance for performance.
Which of the four cards matters most to institutions?
#dusk $DUSK @Dusk
Privacy has been handled for over ten years, and what users still face is a single-choice question:
Either everything is hidden, or everything is naked.
Zcash uses zk-SNARKs, Monero uses ring signatures—both the sender/receiver and the amounts are cleanly concealed.
After you hide everything, then what?
Regulators want to see it, but it can’t be explained; institutions want to use it, but they can’t integrate it.
What Hedger by Dusk aims to do is to change this single-choice question into a multi-select one.
First card: holdings, balances, and amounts—end-to-end encryption.
Whatever is in your address, and how much you transferred, is accounted for on-chain as usual, but outsiders can’t see it.
Second card: auditability under regulation.
Transactions are designed to be fully auditable; when compliance checks need to look, they can.
This is the missing piece in traditional privacy coins: everyday use doesn’t expose you, but if something goes wrong, you can explain it.
Third card: generate proofs in the browser in under two seconds.
Lightweight circuits run on the client; for the user, it feels like a normal transaction—
no hardware barrier, no long waiting.
Fourth card: lay the groundwork for the soon-to-be-deployed order book of obfuscation.
This is a key facility for institutional trading—preventing market manipulation—so trading intentions and risk exposure can’t be discovered in advance.
Note: this card is laying the road, not taking the stage yet.
With four cards in place, Hedger fills the oldest gap in the privacy track:
privacy coins for individuals are plentiful, but this is the first EVM privacy engine that doesn’t trade compliance for performance.
Which of the four cards matters most to institutions?
#dusk $DUSK @Dusk