#dusk $DUSK @Dusk If you send DUSK across the DuskEVM bridge, how do you actually know when your funds are safe to spend on the other side — and what happens if you guess wrong?
Went digging into this after almost making an assumption that could've cost me. My instinct was: inclusion looks confirmed on the block explorer, so the funds must be usable. Turns out that's exactly the wrong way to think about it.
Dusk's own developer docs are blunt about this: inclusion and settlement are two separate stages, and apps moving value between DuskEVM and the DuskDS layer are explicitly told to check protocol or wallet status directly — not to infer finality just because some amount of time has passed. Transaction inclusion on DuskEVM happens fast because it's a sequencer-based L2, but that's not the same moment your funds are actually settled and safe against the base layer.
Here's what that means practically: if you're bridging assets and you send or spend based on "it's probably done by now," you're relying on a guess the protocol itself explicitly warns against. The gap between "looks included" and "actually settled" is exactly the kind of window where acting too early creates real exposure — using funds that could still be reorganized or invalidated before they're truly final.
@Dusk _Foundation — I haven't found a published number for the actual typical wait time between DuskEVM inclusion and DuskDS settlement finality under normal network conditions, only the guidance to check status rather than count elapsed time.
If the protocol itself says don't estimate by elapsed time, are most wallets and bridge UIs actually surfacing real settlement status to users, or are people still just watching a timer and guessing?
Went digging into this after almost making an assumption that could've cost me. My instinct was: inclusion looks confirmed on the block explorer, so the funds must be usable. Turns out that's exactly the wrong way to think about it.
Dusk's own developer docs are blunt about this: inclusion and settlement are two separate stages, and apps moving value between DuskEVM and the DuskDS layer are explicitly told to check protocol or wallet status directly — not to infer finality just because some amount of time has passed. Transaction inclusion on DuskEVM happens fast because it's a sequencer-based L2, but that's not the same moment your funds are actually settled and safe against the base layer.
Here's what that means practically: if you're bridging assets and you send or spend based on "it's probably done by now," you're relying on a guess the protocol itself explicitly warns against. The gap between "looks included" and "actually settled" is exactly the kind of window where acting too early creates real exposure — using funds that could still be reorganized or invalidated before they're truly final.
@Dusk _Foundation — I haven't found a published number for the actual typical wait time between DuskEVM inclusion and DuskDS settlement finality under normal network conditions, only the guidance to check status rather than count elapsed time.
If the protocol itself says don't estimate by elapsed time, are most wallets and bridge UIs actually surfacing real settlement status to users, or are people still just watching a timer and guessing?