Dusk Foundation doesn’t give you a “best effort” close when the venue flips the session.
You feel it on the dullest kind of day. No volatility. No drama. Just a reconcile run that’s supposed to be boring. Flatten exposure. Clear leftovers. Move on.
Orders are filled. Positions exist. Everyone has a screen that says the same thing. Then the venue rolls its session context. Quietly. No banner. No warning beyond the one everyone already ignored.
On most rails, half-finished work gets swept forward with a note. On Dusk, the boundary is not a note.
What breaks isn’t the trade. It’s the assumption that “recent” still counts as “current.” You reach for a post-trade action against a state that was valid seconds ago and now isn’t. Not revoked. Not disputed. Just no longer the context the venue is willing to bind to.
I’ve watched this turn stupid fast.
“Run it now before the session rolls.”
We ran it.
Nothing reverted. Nothing screamed. The call just never finalized. And the room kept circling the same sentence—the fills are there—like saying it out loud would force the boundary to bend.
It didn’t.
On Dusk, session context is real. And if your proof material is tied to the previous window, it doesn’t carry. Moonlight doesn’t let authorization drift forward just because the economics stayed the same. Disclosure is scoped to this moment, not the one everyone is still thinking about.
That’s the pressure surface.
Routine cleanup turning into a hard stop.
It’s not custody. Not validators. Not price. It’s timing discipline colliding with workflows that assume continuity by default.
The worst part is the silence. There’s nothing safe to paste into Slack. No artifact you can wave without widening disclosure. Internally, the desk knows the positions exist. Externally, the protocol won’t certify the step you’re asking for under a context it already closed.
That gap makes people improvise.
“Try the net again.”
“Book it manually and fix it later.”
“Can we just disclose enough for this rollover?”
That’s how exceptions grow legs. One quiet rollover becomes precedent.
Dusk doesn’t stop you from making off-chain decisions. It just refuses to ratify the on-chain step until you realign with the venue’s current session and the disclosure posture that applies now, not a minute ago.
So the desk does the slow thing. Pull the new context. Rebuild the call. Re-qualify under the fresh window. All while watching the clock, because the next rollover is already getting close.
If you rush it, you learn it twice.
Not as an incident.
As that familiar stall where everything feels done, and nothing is allowed to move yet.
