#dusk $DUSK @Dusk DuskEVM testnet for a CreatorPad task, deploying a dummy Solidity contract with Hardhat. Everything felt familiar until I hit the mempool. the thing nobody puts in the deck DuskEVM runs sequencerbonly right now, no public mempool.
So all that EVM compatible, just like Ethereum framing… sure, the tooling is identical, but the actual transaction flow isn't decentralized the way people assume when they hear EVM. Someone's sequencer decides ordering.
That's not a knock, just not what the marketing copy implies and then there's the bridge. On Aug 16 the team flagged suspicious activity tied to a team managed wallet used in bridge ops and shut it down for a security review
still closed as of writing, pending the DuskEVM mainnet rollout. Again: team managed wallet doing bridge custody. Not a DAO multisig, not a decentralized relayer set. A wallet the team controls.
Neither of these is disqualifying at this stage testnets and pre mainnet bridges usually look like this everywhere.
But it's a pattern worth sitting with: the privacy/compliance narrative is the loud part, and the actual infrastructure underneath is still pretty centralized in the boring, operational places.
how much of that changes once DuskEVM mainnet actually ships, versus just moving the same trust assumptions one layer deeper.
$TUT $PORTAL
So all that EVM compatible, just like Ethereum framing… sure, the tooling is identical, but the actual transaction flow isn't decentralized the way people assume when they hear EVM. Someone's sequencer decides ordering.
That's not a knock, just not what the marketing copy implies and then there's the bridge. On Aug 16 the team flagged suspicious activity tied to a team managed wallet used in bridge ops and shut it down for a security review
still closed as of writing, pending the DuskEVM mainnet rollout. Again: team managed wallet doing bridge custody. Not a DAO multisig, not a decentralized relayer set. A wallet the team controls.
Neither of these is disqualifying at this stage testnets and pre mainnet bridges usually look like this everywhere.
But it's a pattern worth sitting with: the privacy/compliance narrative is the loud part, and the actual infrastructure underneath is still pretty centralized in the boring, operational places.
how much of that changes once DuskEVM mainnet actually ships, versus just moving the same trust assumptions one layer deeper.
$TUT $PORTAL