$DUSK #dusk — DuskEVM shows a confirmation before Dusk has actually settled anything. @Dusk's own developer docs are explicit: transaction inclusion is fast, but inclusion and settlement are different stages, and apps moving value between DuskEVM and the L1 are told to check protocol or wallet status, not elapsed time, to know what's final. Sequencer executes instantly, batcher posts the data to DuskDS as blobs, proposer posts a state commitment after. Three actors, three moments — you only ever see the first.
Checked GitHub for context: dusk-network/duskevm-genesis, the repo holding DuskEVM's actual genesis block and rollup config, was last updated Aug 8. Two days later, a dated Aug 10 update was still describing DuskEVM as testnet — deploy-and-test with Hardhat and Solidity — despite January posts elsewhere already calling it a "mainnet launch." Genesis config still being touched in August lines up with testnet-stage, not mainnet-stage.
The dual fee (L2 execution plus a separate DuskDS data-availability fee) makes the staging tangible — you're paying two layers for sequential work, not one. That's the same layering the genesis repo and the docs both point to: settlement is a distinct, later event from execution, at the code level and at the announcement level.
What changed for me: DuskEVM vs DuskVM isn't a language choice, Solidity vs Rust. It's which stage of finality an application is actually built around. DuskVM's execution and settlement are the same event. DuskEVM's aren't. Anyone integrating DuskEVM right now — is your app reading settlement status, or just watching for inclusion?
Next: checking duskevm-genesis for the first commit that stops touching rollup config — that's a cleaner signal of mainnet-readiness than any announcement.
#dusk $DUSK @Dusk
Checked GitHub for context: dusk-network/duskevm-genesis, the repo holding DuskEVM's actual genesis block and rollup config, was last updated Aug 8. Two days later, a dated Aug 10 update was still describing DuskEVM as testnet — deploy-and-test with Hardhat and Solidity — despite January posts elsewhere already calling it a "mainnet launch." Genesis config still being touched in August lines up with testnet-stage, not mainnet-stage.
The dual fee (L2 execution plus a separate DuskDS data-availability fee) makes the staging tangible — you're paying two layers for sequential work, not one. That's the same layering the genesis repo and the docs both point to: settlement is a distinct, later event from execution, at the code level and at the announcement level.
What changed for me: DuskEVM vs DuskVM isn't a language choice, Solidity vs Rust. It's which stage of finality an application is actually built around. DuskVM's execution and settlement are the same event. DuskEVM's aren't. Anyone integrating DuskEVM right now — is your app reading settlement status, or just watching for inclusion?
Next: checking duskevm-genesis for the first commit that stops touching rollup config — that's a cleaner signal of mainnet-readiness than any announcement.
#dusk $DUSK @Dusk