DuskEVM testnet went live Aug 10, then got recirculated hard on Aug 13 — @Dusk_Foundation posting "DuskEVM Testnet is LIVE" like it's the headline, and it kind of is. Spent the task poking around what actually ships with it, not what the announcement thread promises. $DUSK
Here's the thing that got me — you deploy on DuskEVM, you're writing plain Solidity, Hardhat, the whole familiar EVM stack, gas paid in DUSK, transparent by default. Hedger — the actual confidential-transaction layer, the homomorphic encryption + ZK piece that's supposed to be Dusk's whole reason for existing — sits off to the side as something you reach for "where appropriate." Still testnet too, not bundled in.
So the sequencing is: generic EVM compatibility ships first, privacy ships... whenever. Devs porting Ethereum contracts get instant familiarity today. The confidentiality story, the part everyone's actually excited about, is opt-in and not-yet.
Kept rereading the docs page expecting to find privacy baked into the default path and it just wasn't there. Had to double check I wasn't missing a flag or something. Nope — separate module, separate integration step.
Not saying that's wrong, #dusk sequencing infra this way is probably the sane move. But it's a pretty clean example of "default" and "advertised" being two different products shipped at two different times.
Makes me wonder how much of DuskEVM's early activity ends up being plain transparent contracts anyway, once it's live enough to matter — does anyone actually reach for Hedger once the easy path already works?
Here's the thing that got me — you deploy on DuskEVM, you're writing plain Solidity, Hardhat, the whole familiar EVM stack, gas paid in DUSK, transparent by default. Hedger — the actual confidential-transaction layer, the homomorphic encryption + ZK piece that's supposed to be Dusk's whole reason for existing — sits off to the side as something you reach for "where appropriate." Still testnet too, not bundled in.
So the sequencing is: generic EVM compatibility ships first, privacy ships... whenever. Devs porting Ethereum contracts get instant familiarity today. The confidentiality story, the part everyone's actually excited about, is opt-in and not-yet.
Kept rereading the docs page expecting to find privacy baked into the default path and it just wasn't there. Had to double check I wasn't missing a flag or something. Nope — separate module, separate integration step.
Not saying that's wrong, #dusk sequencing infra this way is probably the sane move. But it's a pretty clean example of "default" and "advertised" being two different products shipped at two different times.
Makes me wonder how much of DuskEVM's early activity ends up being plain transparent contracts anyway, once it's live enough to matter — does anyone actually reach for Hedger once the easy path already works?