Deploying a small test contract on Dusk's testnet, live since August 10, felt like standard Hardhat work until the tx just... confirmed. No pending state, no mempool to watch, no waiting for gas competition to settle. For a second I thought my RPC was broken. It wasn't, DuskEVM simply doesn't run a public mempool. It's sequencer-only, by design. That's the detail from this CreatorPad task on @Dusk_Foundation and $DUSK , #dusk that actually stuck with me.
I'd assumed EVM-compatible meant EVM-b...