Spent the task today digging into DuskEVM vs DuskVM on Dusk Network, and one contrast wouldn’t let go of me — hold up, why does only one of these get the red-carpet treatment.

DuskEVM’s public testnet went live Aug 10 (@Dusk Foundation posted it themselves), chain 745 if you check the RPC, and there’s already a full Blockscout explorer indexing it. Within a day devs were deploying plain Solidity through Hardhat like #dusk was just another L2 — gas paid straight in $DUSK , no new mental model needed. DuskVM, the native ZK side that’s supposed to be the actual privacy-and-compliance story, just sits behind a quickstart doc and a quiet admission that it takes more comfort with Dusk-specific tooling to really use. No launch clip. No thread.

Chewed on that after I put the laptop down for a snack. The path getting the friction stripped away first is the one that looks like every other EVM chain out there. The path that’s actually different — the one the whole regulated-RWA pitch leans on — is still the one asking people to be patient.

Not calling it a flaw exactly… just noticing that the order things ship in tells you who’s getting optimized for right now. Same $DUSK gas either way. Which side ends up mattering more once the testnet-week novelty wears off?
$DUSK #dusk @Dusk