Spent my CreatorPad session on #Dusk's selective disclosure angle, half expecting the usual "privacy-first L1" talking points. What actually stopped me was the DuskEVM testnet — live since Aug 10, this week — and how plain it looks once you're actually poking around in it. Solidity, Hardhat, standard deploy flow. $DUSK . @Dusk .
Here's the thing though… every transaction on that testnet is sitting fully exposed on Blockscout. Sender, amount, contract call, all visible, no shielding, nothing hidden. For a chain built around "selective disclosure" as the headline feature, the actual entry point developers get pointed to first is just… transparent EVM. The confidential piece, Hedger, isn't baked in — it's something you add on top, later, once you're already building.
I kept clicking through the explorer expecting at least a partial mask on something. Nope. Full visibility, same as any regular chain. Had to sit with that for a sec — the marketing sells privacy as the default state, but the onboarding path runs through open rails first.
Not saying it's wrong, sequencing adoption before complexity makes sense. But it does flip the story a bit — privacy here reads more like a feature you graduate into than something you start with.
@Dusk
$DUSK
#dusk
Here's the thing though… every transaction on that testnet is sitting fully exposed on Blockscout. Sender, amount, contract call, all visible, no shielding, nothing hidden. For a chain built around "selective disclosure" as the headline feature, the actual entry point developers get pointed to first is just… transparent EVM. The confidential piece, Hedger, isn't baked in — it's something you add on top, later, once you're already building.
I kept clicking through the explorer expecting at least a partial mask on something. Nope. Full visibility, same as any regular chain. Had to sit with that for a sec — the marketing sells privacy as the default state, but the onboarding path runs through open rails first.
Not saying it's wrong, sequencing adoption before complexity makes sense. But it does flip the story a bit — privacy here reads more like a feature you graduate into than something you start with.
@Dusk
$DUSK
#dusk
