$DUSK #Dusk — DuskEVM skips Optimism’s classic 7-day challenge window. That delay wasn’t simply a UX flaw; it’s part of the security model.
Digging into @DuskFoundation’s writeup on the OP Stack port, DuskEVM settles to DuskDS, while a MIPS-based pre-verifier checks state transitions before they are accepted for settlement. Dusk’s docs describe withdrawals finalizing in roughly 15 minutes.
At first, that looks like a straightforward UX upgrade. But the security question is more interesting.
On the standard OP Stack, the 7-day window provides time for permissionless fraud proofs to challenge an invalid state root. Dusk’s design moves verification earlier in the flow instead.
So I wouldn’t describe this as simply “removing the trust requirement.” The important question is where the security assumption now sits: is pre-verification independently enforced by the DuskDS validator set, or does it depend on a distinct verifier set?
That distinction matters. Faster finality is valuable, but only if we understand what changed underneath it.
Next I’m checking the Rusk GitHub and Dusk’s technical docs for how the pre-verifier set relates to the DuskDS validators.
#dusk $DUSK @Dusk
Digging into @DuskFoundation’s writeup on the OP Stack port, DuskEVM settles to DuskDS, while a MIPS-based pre-verifier checks state transitions before they are accepted for settlement. Dusk’s docs describe withdrawals finalizing in roughly 15 minutes.
At first, that looks like a straightforward UX upgrade. But the security question is more interesting.
On the standard OP Stack, the 7-day window provides time for permissionless fraud proofs to challenge an invalid state root. Dusk’s design moves verification earlier in the flow instead.
So I wouldn’t describe this as simply “removing the trust requirement.” The important question is where the security assumption now sits: is pre-verification independently enforced by the DuskDS validator set, or does it depend on a distinct verifier set?
That distinction matters. Faster finality is valuable, but only if we understand what changed underneath it.
Next I’m checking the Rusk GitHub and Dusk’s technical docs for how the pre-verifier set relates to the DuskDS validators.
#dusk $DUSK @Dusk
