The book ticks. Monad has the fills after.
A CLOB cannot wait 300 ms. A hosted matching engine is not a market. Interlude runs the book in the session. Fills settle to the same address on Monad.
A website is fast and dishonest. Monad is honest and late. Interlude is both.
How fast is a cancel?
A WEBSITEInstant
MONAD ALONENext block
INTERLUDEInstant
Who holds the book?
A WEBSITETheir server
MONAD ALONEMonad
INTERLUDEMonad
Can they hide a fill?
A WEBSITEYes
MONAD ALONENo
INTERLUDENo
Does liquidity stay on Monad?
A WEBSITENo
MONAD ALONEYes
INTERLUDEYes
The book ticks on the engine
Place, cancel, match. The return comes back in the same round trip. No gas after one grant.
Fills settle at the same address
Diffs commit to Monad. Vaults, oracles and other apps still see the same accounts.
A watcher can replay the tape
The batch names every fill. A slash walks the diffs backwards. The operator cannot quietly edit a match.
Mark the book as live storage
The mapping that has to tick. Annotate it. whenNotDelegated locks those slots on Monad.
Ship one node next to the flow
Or ship one book per region and let nearestFloor pick. One writer per contract.
Traders sign once
Then every place and cancel hits the engine. Same ABI as a normal Monad book.
Undelegate when the session is done
The lock lifts. The book is ordinary Monad again, post-session state.
A constant-product pool on Interlude. Buy and sell move the mid before Monad's next block; balances settle as slots.
Open the tap bookOnchain games
Real-time movement, combat and physics with authoritative state, settled to Monad at round end.
Agent swarms
Thousands of autonomous agents negotiating in one session, committing only the outcome.
Realtime social
Presence, reactions and live coordination that feel like web2 but stay verifiable end to end.