Project @Dusk_Foundation spent the morning poking around the new DuskEVM testnet instead of doing anything productive, ngl.

it went live august 10th, and most of the framing going around was “solidity + hardhat support now works,” which, fine, but that’s not the part that actually stopped my scrolling.

what got me is the settlement split. deploy a contract on duskevm and the sequencer executes it there but the batcher still posts that transaction data back to DuskDS as blobs, and a proposer anchors the resulting state commitments to it after. execution happens in one place, finality happens back on the base layer. gas for all of it is paid in DUSK, bridged over from DuskDS first, before anything gets deployed.

that’s the part i keep circling back to before a dev writes a single line of solidity here, they’ve already had to move actual DUSK across a bridge. that’s a real action, not a vibe. checked the testnet explorer earlier and there’s already contracts sitting there from the past few days, which for something six days old is not nothing..

still working out whether this settlement-anchoring setup meaningfully matters for how NPEX-style regulated assets eventually get treated on the EVM side, or if i’m just reading too much into a standard OP-stack pattern. leaning toward the former, not fully sold though.

anyone actually deployed something on it yet, or still just reading docs like me?

$DUSK #dusk