The technology is incredibly impressive, and the developer experience of the “confidential EVM” is going to the gods
Bears say Hedger homomorphic encryption is a half-finished product and the documentation isn’t friendly. Nonsense. Hedger uses homomorphic encryption + PLONK to build a confidential EVM. As of August 2026, it’s still refining the cross-bridge UX on the testnet. In the Rusk repo, commits like “spend_and_execute implementation wip” indicate that mainnet-level confidential contracts are already being sealed. “Not friendly to Solidity developers”? That’s a filtering mechanism—those coming for airdrops, copying contracts, launching rug pulls… see the documentation and get a headache, then just leave. The ones who stay are teams that genuinely want to build regulated financial applications. They already have to read the legal stuff, handle KYC, and run audits—reading a few more ZK documents isn’t a big deal. This kind of “high-cold” approach keeps the DUSK ecosystem clean, and also ensures the asset quality running on top will be high. Once the DuskEVM mainnet stabilizes, Solidity developers who come in will find the underlying layer is steadier than they imagined, because the teams handling the hard parts have already carried it for you. Now those complaining about the experience—wait until institutions onboard. They’ll realize: “hard to use” is actually so people don’t dare to use it recklessly.
#dusk $DUSK @Dusk
Bears say Hedger homomorphic encryption is a half-finished product and the documentation isn’t friendly. Nonsense. Hedger uses homomorphic encryption + PLONK to build a confidential EVM. As of August 2026, it’s still refining the cross-bridge UX on the testnet. In the Rusk repo, commits like “spend_and_execute implementation wip” indicate that mainnet-level confidential contracts are already being sealed. “Not friendly to Solidity developers”? That’s a filtering mechanism—those coming for airdrops, copying contracts, launching rug pulls… see the documentation and get a headache, then just leave. The ones who stay are teams that genuinely want to build regulated financial applications. They already have to read the legal stuff, handle KYC, and run audits—reading a few more ZK documents isn’t a big deal. This kind of “high-cold” approach keeps the DUSK ecosystem clean, and also ensures the asset quality running on top will be high. Once the DuskEVM mainnet stabilizes, Solidity developers who come in will find the underlying layer is steadier than they imagined, because the teams handling the hard parts have already carried it for you. Now those complaining about the experience—wait until institutions onboard. They’ll realize: “hard to use” is actually so people don’t dare to use it recklessly.
#dusk $DUSK @Dusk