#dusk $DUSK @Dusk DuskEVM testnet went live on August 10 and I finally got around to poking at it today deployed a dummy contract just to see what EVM equivalent actually meant in practice. Chain ID 744, standard Hardhat config, RPC pointed at rpc.evm.dusk.network... felt exactly like deploying to any other OP Stack chain. Almost too easy.
Then I went looking for my tx in the mempool before it confirmed. Couldn't find it. Turns out DuskEVM has no public mempool right now sequencer only. Everything gets ordered before you ever see it move.
That's the thing that stuck with me. The pitch is familiar Ethereum tooling, full compatibility, and the tooling part is true .....Solidity, Blockscout, all of it just works.
but the actual transaction flow right now runs through a single sequencer, not some open permissionless pipe. Compliance first chain, so maybe that's the point, not a bug… but it's a different mental model than what EVM equivalent usually implies.
how much of that changes once Ethereum mainnet settlement lands in September, or if sequencer control just becomes the permanent quiet default nobody circles back to ask about.
Then I went looking for my tx in the mempool before it confirmed. Couldn't find it. Turns out DuskEVM has no public mempool right now sequencer only. Everything gets ordered before you ever see it move.
That's the thing that stuck with me. The pitch is familiar Ethereum tooling, full compatibility, and the tooling part is true .....Solidity, Blockscout, all of it just works.
but the actual transaction flow right now runs through a single sequencer, not some open permissionless pipe. Compliance first chain, so maybe that's the point, not a bug… but it's a different mental model than what EVM equivalent usually implies.
how much of that changes once Ethereum mainnet settlement lands in September, or if sequencer control just becomes the permanent quiet default nobody circles back to ask about.
