I bridged some testnet DUSK over to DuskEVM last night and deployed a small contract, mostly just to watch a transaction move through the pipe end to end. It confirmed fast. Naturally assumed that meant done — inclusion showing up, transaction closed, move on.
Turns out that's not actually the same thing here, and the gap matters more than it sounds. DuskEVM runs as a rollup: a sequencer includes your transaction in an L2 block first, then a batcher separately posts that data over to DuskDS, and only after state commitments and fault proofs connect back does it actually settle. Inclusion happens on one clock. Settlement happens on another. My wallet showed confirmed the moment the first one happened, not the second.
Reminded me of a check clearing at a bank counter. The teller hands you a receipt the second they take it — feels done. The actual money doesn't move between banks until it clears behind the scenes, on its own schedule, regardless of what the receipt says.
Makes sense why Dusk draws the line this sharply, given who this chain is actually built for. A regulated venue moving real securities can't treat "looks confirmed" and "is settled" as interchangeable — the docs are explicit that anything moving value between DuskEVM and the Dusk L1 should check protocol or wallet status directly, not infer finality from how much time passed.
Worth being clear this was testnet — mainnet timing may look different once it's fully live.
Still turning it over — for a chain aiming at MTF-grade settlement, does that inclusion/settlement split get abstracted away for the end user eventually, or does regulated finance actually want that gap left visible on purpose?
#dusk $DUSK @Dusk #DUSK
Turns out that's not actually the same thing here, and the gap matters more than it sounds. DuskEVM runs as a rollup: a sequencer includes your transaction in an L2 block first, then a batcher separately posts that data over to DuskDS, and only after state commitments and fault proofs connect back does it actually settle. Inclusion happens on one clock. Settlement happens on another. My wallet showed confirmed the moment the first one happened, not the second.
Reminded me of a check clearing at a bank counter. The teller hands you a receipt the second they take it — feels done. The actual money doesn't move between banks until it clears behind the scenes, on its own schedule, regardless of what the receipt says.
Makes sense why Dusk draws the line this sharply, given who this chain is actually built for. A regulated venue moving real securities can't treat "looks confirmed" and "is settled" as interchangeable — the docs are explicit that anything moving value between DuskEVM and the Dusk L1 should check protocol or wallet status directly, not infer finality from how much time passed.
Worth being clear this was testnet — mainnet timing may look different once it's fully live.
Still turning it over — for a chain aiming at MTF-grade settlement, does that inclusion/settlement split get abstracted away for the end user eventually, or does regulated finance actually want that gap left visible on purpose?
#dusk $DUSK @Dusk #DUSK