I bridged some DUSK over to DuskEVM today and kept refreshing the tracker like it would change something. My transaction showed "included" almost right away. Then it just sat there for a while before anything said "settled." Assumed that gap was UI lag.
It's not. DuskEVM runs on a rollup lifecycle: a sequencer includes your transaction in an L2 block fast, but that's not the same step as settlement. A separate batcher has to publish that data to DuskDS — Dusk's own consensus and data-availability layer — and only once state commitments and fault proofs tie back to that layer is anything actually settled. Included and settled are two different promises, made by two different parts of the stack.
Felt like a package showing "out for delivery" the moment it leaves the warehouse, long before it's actually sitting on your porch. Both true. Not the same claim.
What stood out is that you're not supposed to guess at this from elapsed time. Moving value between DuskEVM and the Dusk L1 means checking actual protocol or wallet status, not assuming enough minutes have passed. For something meant to carry regulated financial assets, that's not a small detail — a fund can't settle on a guess.
So does that two-stage design become a selling point once institutions actually depend on it, or just a UX hurdle regular users bounce off before they understand why it's built that way?
@Dusk_Foundation $DUSK #dusk
#dusk $DUSK
It's not. DuskEVM runs on a rollup lifecycle: a sequencer includes your transaction in an L2 block fast, but that's not the same step as settlement. A separate batcher has to publish that data to DuskDS — Dusk's own consensus and data-availability layer — and only once state commitments and fault proofs tie back to that layer is anything actually settled. Included and settled are two different promises, made by two different parts of the stack.
Felt like a package showing "out for delivery" the moment it leaves the warehouse, long before it's actually sitting on your porch. Both true. Not the same claim.
What stood out is that you're not supposed to guess at this from elapsed time. Moving value between DuskEVM and the Dusk L1 means checking actual protocol or wallet status, not assuming enough minutes have passed. For something meant to carry regulated financial assets, that's not a small detail — a fund can't settle on a guess.
So does that two-stage design become a selling point once institutions actually depend on it, or just a UX hurdle regular users bounce off before they understand why it's built that way?
@Dusk_Foundation $DUSK #dusk
#dusk $DUSK