The first warning came from a line under a lifecycle diagram, easy to skip.

A community explainer on DuskEVM stated flat out: no 7-day fault window, ~15 min withdrawal finalization, MIPS pre-verifier eliminates the fraud proof delay. Clean number, figured I'd plan a withdrawal around it.

Assumption: official docs would confirm that number.

Not what I found. Dusk's own docs lay out the DuskEVM lifecycle in four steps, tx to sequencer, included in an L2 block, batcher publishes to DuskDS, then state commitments and fault proofs connect that state to settlement. Fault proofs still named explicitly. No 15 minutes anywhere. Instead a line telling you not to infer finality from elapsed time, check protocol or wallet status instead.

That's the actual gap. Inclusion is fast, docs say so themselves. Settlement is separate, gated by something nobody put a clock on.

So the fault proof step didn't disappear, it's just not documented the way Optimism's permissionless challenge system is, where anyone can run the prover and watch contesting happen.

Can't tell if that's compressed and privately resolved, or just not public yet.

Glad I checked before timing a withdrawal off someone else's number.

What happens to that 15 minute number the first time a fault proof needs contesting mid settlement rush? 👍

#dusk $DUSK @Dusk