Once I saw DuskEVM was OP Stack based, I wanted to trace an actual transaction through it instead of just accepting the label. So I went through the flow step by step last night.
A transaction gets submitted to the DuskEVM sequencer first. That's standard OP Stack behavior, the sequencer orders it and includes it in an L2 block almost immediately. That's the part that feels fast and familiar to anyone who's used a rollup before. But the sequencer isn't the end of the story here, a batcher takes that transaction data and publishes it to DuskDS, Dusk's settlement and data-availability layer underneath.
That's the adapter piece I was trying to understand. OP Stack normally hands that job to Ethereum. Here it's swapped out for DuskDS instead, which means the same rollup architecture developers already know is being redirected toward a settlement layer built specifically around deterministic finality for regulated assets, not toward general-purpose L1 security.
Following it through like that made something click that reading the summary hadn't. The sequencer step and the DuskDS step are doing genuinely different jobs, one gets your transaction moving, the other is what actually anchors it. I hadn't separated those two moments before, I'd just been picturing "transaction happens" as one single event.
#dusk $DUSK @Dusk $AIO $HEMI
A transaction gets submitted to the DuskEVM sequencer first. That's standard OP Stack behavior, the sequencer orders it and includes it in an L2 block almost immediately. That's the part that feels fast and familiar to anyone who's used a rollup before. But the sequencer isn't the end of the story here, a batcher takes that transaction data and publishes it to DuskDS, Dusk's settlement and data-availability layer underneath.
That's the adapter piece I was trying to understand. OP Stack normally hands that job to Ethereum. Here it's swapped out for DuskDS instead, which means the same rollup architecture developers already know is being redirected toward a settlement layer built specifically around deterministic finality for regulated assets, not toward general-purpose L1 security.
Following it through like that made something click that reading the summary hadn't. The sequencer step and the DuskDS step are doing genuinely different jobs, one gets your transaction moving, the other is what actually anchors it. I hadn't separated those two moments before, I'd just been picturing "transaction happens" as one single event.
#dusk $DUSK @Dusk $AIO $HEMI