Spent my CreatorPad slot poking around the DuskEVM testnet, the one @Dusk flipped on Aug 10... #dusk $DUSK . Went in expecting the privacy-first pitch to greet me at the door. It didn't.
First thing you actually do: bridge DUSK over from DuskDS to DuskEVM through the official web wallet, and it just sits there as your plain gas token. Standard Solidity, standard Hardhat, standard everything. Checked the explorer (explorer.testnet.evm.dusk.network) — nothing zero-knowledge about the transactions sitting in it, just regular EVM calls like you'd see on any other testnet.
Hmm — that's the part that stuck with me. The security-and-privacy narrative is the headline, but Hedger, their confidential-tx layer, is opt-in, "where appropriate," not the rail everyone gets funneled down. Devs get the boring EVM path first. The ZK stuff shows up later, for whoever actually reaches for it.
Kind of mirrors something I do myself — install the "advanced settings" toggle in every app and then never touch it for weeks. Default wins, basically every time, whether it's me or a whole dev ecosystem.
Makes me wonder if that's just sequencing, or if it means the compliance story is doing more marketing work right now than actual on-chain work... which one catches up to the other first?
#dusk
$DUSK
@Dusk