When I was a kid watching people play chess, the hardest part wasn’t losing—it was that someone next to you would always read out your next move in advance. The trading market is even more extreme: you can pretend your position is still, but the real soft spot is the order you haven’t placed yet. On a public chain, every bid and ask can become a trump card that someone else has peeked at in advance.
Recently I noticed Hedger @Dusk , which is adding a layer of a “flipped, downward-facing” order book to DuskEVM. It doesn’t rely on zero-knowledge proofs alone to say “I computed it correctly.” Instead, it stacks homomorphic encryption and ZKP together: homomorphic encryption is like doing addition and subtraction inside a sealed box, while ZKP proves that the rules haven’t been broken. More importantly, it uses a hybrid UTXO/account model, so on-chain assets can be accounted for like balances, and also—when needed—can be composed across layers. This leaves room in the future to obscure things like posted orders, execution intent, and position exposure. The line in the materials, “the client completes the proof within 2 seconds,” really stuck with me, because the greatest enemy of privacy is often not regulation, but waiting: once users have to wait, they retreat back to a transparent chain.
$DUSK isn’t just an observer here. Transactions with hidden amounts and hidden intent still ultimately pay gas with DUSK, so they can be executed by DuskEVM. In other words, privacy isn’t a side path—it’s a normal function that’s directly factored into execution costs.
After reading it, my conclusion is this: the real difficulty of order-book privacy isn’t whether you can “hide,” but whether the market will still trust the price after it’s hidden. Technology can obscure your trump cards, but liquidity, market makers, and real executions don’t just grow back on their own. #dusk ’s setup is like fixing a card table so it can’t be watched—but whether the game turns lively or not is another matter. Do your own homework—don’t just take my word for it.
Recently I noticed Hedger @Dusk , which is adding a layer of a “flipped, downward-facing” order book to DuskEVM. It doesn’t rely on zero-knowledge proofs alone to say “I computed it correctly.” Instead, it stacks homomorphic encryption and ZKP together: homomorphic encryption is like doing addition and subtraction inside a sealed box, while ZKP proves that the rules haven’t been broken. More importantly, it uses a hybrid UTXO/account model, so on-chain assets can be accounted for like balances, and also—when needed—can be composed across layers. This leaves room in the future to obscure things like posted orders, execution intent, and position exposure. The line in the materials, “the client completes the proof within 2 seconds,” really stuck with me, because the greatest enemy of privacy is often not regulation, but waiting: once users have to wait, they retreat back to a transparent chain.
$DUSK isn’t just an observer here. Transactions with hidden amounts and hidden intent still ultimately pay gas with DUSK, so they can be executed by DuskEVM. In other words, privacy isn’t a side path—it’s a normal function that’s directly factored into execution costs.
After reading it, my conclusion is this: the real difficulty of order-book privacy isn’t whether you can “hide,” but whether the market will still trust the price after it’s hidden. Technology can obscure your trump cards, but liquidity, market makers, and real executions don’t just grow back on their own. #dusk ’s setup is like fixing a card table so it can’t be watched—but whether the game turns lively or not is another matter. Do your own homework—don’t just take my word for it.
