Spent my CreatorPad session on DuskEVM, the EVM side of Dusk ($DUSK #dusk @Dusk ), and one detail stopped me mid-scroll.
The whole pitch since the public testnet went live on August 10 has been "just deploy like any other EVM chain" — Solidity, Hardhat, the works. I went in assuming that meant it behaves like Ethereum underneath too.
It doesn't. Buried in the docs — hold up — DuskEVM right now runs sequencer-only, no public mempool. Sounds like a footnote, but it's actually the whole story: the "familiar" part is the tooling, not the execution model. On a normal EVM chain your tx sits in a mempool anyone can see. Here it goes straight to one sequencer. Quietly different from what "EVM-compatible" implies to most people skimming a thread.
Caught myself doing exactly that — skimming, nodding, assuming — until I opened the explorer and the fee docs side by side. Had to walk it back a bit. Not a red flag, early OP Stack rollups do this all the time. Just wasn't the story being told on the surface.
Wonder how many people bridging DUSK over right now clock that gap before it actually starts to matter to them.
@Dusk
#dusk
$DUSK