Dusk ($DUSK ) dropped the DuskEVM testnet live on Aug 10 — @Dusk tweet just says "deploy and test applications on Dusk using familiar Ethereum tooling." Solidity, Hardhat, the whole kit. #dusk
Spent the last hour poking around what that actually unlocks and… it's less than the headline implies. This is developer access, not usage. No live contracts moving real value yet, no privacy features actually exercised on-chain — just a sandbox where Solidity devs can point their existing tools at Dusk infra and see if it behaves. Hedger, the ZK+homomorphic privacy layer that's supposed to be the whole point, isn't the thing being tested here. The EVM compatibility is.
Kind of a familiar pattern with privacy chains, hold up— the "privacy infrastructure" pitch always ships its onboarding layer first, and the actual confidential-transaction layer stays theoretical a while longer. Makes sense operationally (you need builders before you need private volume) but it does mean the thing being marketed and the thing being shipped aren't quite the same thing this week.
Testnet numbers aren't public yet either, so no read on whether anyone's actually deploying. Curious if DuskEVM adoption ends up EVM-generic or if devs specifically reach for the privacy layer once it's live — those feel like two very different outcomes.
Spent the last hour poking around what that actually unlocks and… it's less than the headline implies. This is developer access, not usage. No live contracts moving real value yet, no privacy features actually exercised on-chain — just a sandbox where Solidity devs can point their existing tools at Dusk infra and see if it behaves. Hedger, the ZK+homomorphic privacy layer that's supposed to be the whole point, isn't the thing being tested here. The EVM compatibility is.
Kind of a familiar pattern with privacy chains, hold up— the "privacy infrastructure" pitch always ships its onboarding layer first, and the actual confidential-transaction layer stays theoretical a while longer. Makes sense operationally (you need builders before you need private volume) but it does mean the thing being marketed and the thing being shipped aren't quite the same thing this week.
Testnet numbers aren't public yet either, so no read on whether anyone's actually deploying. Curious if DuskEVM adoption ends up EVM-generic or if devs specifically reach for the privacy layer once it's live — those feel like two very different outcomes.