Spent the afternoon poking at it. #dusk $DUSK @Dusk
Here's the thing that actually stopped me mid-scroll — I expected "privacy chain gets EVM" to mean privacy comes baked in by default. It doesn't. DuskEVM is straight OP Stack, gas paid in DUSK, settling back to DuskDS like any other rollup. Deploy a standard Solidity contract with Hardhat and you get... a standard Solidity contract. Confidential flows only show up if you deliberately reach for Hedger on top. Privacy is the advanced path, not the default one.
Kind of makes sense once you sit with it — you can't force ZK-everything onto devs who just want familiar tooling, or nobody ships. But it does flip the marketing framing on its head a little. The people who get onboarded first are the ones who don't touch the privacy stuff at all.
Ran the chainId check myself just to see the response land — small dumb satisfaction in that. Still turning over whether "privacy chain" is even the right label for this thing anymore, or if it's becoming two products wearing one ticker.
Here's the thing that actually stopped me mid-scroll — I expected "privacy chain gets EVM" to mean privacy comes baked in by default. It doesn't. DuskEVM is straight OP Stack, gas paid in DUSK, settling back to DuskDS like any other rollup. Deploy a standard Solidity contract with Hardhat and you get... a standard Solidity contract. Confidential flows only show up if you deliberately reach for Hedger on top. Privacy is the advanced path, not the default one.
Kind of makes sense once you sit with it — you can't force ZK-everything onto devs who just want familiar tooling, or nobody ships. But it does flip the marketing framing on its head a little. The people who get onboarded first are the ones who don't touch the privacy stuff at all.
Ran the chainId check myself just to see the response land — small dumb satisfaction in that. Still turning over whether "privacy chain" is even the right label for this thing anymore, or if it's becoming two products wearing one ticker.
