Presence now. The log is still Monad.
A reaction that waits for a block is not a reaction. A hosted feed can erase it. Interlude: the room updates now. What people did settles on Monad.
A website answers in one round trip and asks for trust. Monad settles every write where anyone can check it. Interlude does both.
How fast is a reaction?
A WEBSITEOne round trip
MONAD ALONENext block
INTERLUDEOne round trip
Can they erase it later?
A WEBSITEYes
MONAD ALONENo
INTERLUDENo
Does the other person see it now?
A WEBSITEYes, if the host tells the truth
MONAD ALONEAfter the block
INTERLUDEYes. Monad confirms after.
The room updates now
Join, react, leave. The sender gets the receipt in one round trip (38-42 ms p50 of network, measured), and every other tab reads the same contract.
The log settles on Monad
Diffs commit. Who was here, and what they did, is the contract.
Undelegate closes the session
Commits stop. After the challenge window anyone calls releaseStake, the lock lifts, and the room is ordinary Monad again, same address.
Mark presence as live storage
Who is here, the last reaction, the lobby seats. That is what the engine holds.
Ship the room
One node, or one per region with nearestFloor. The public demo already does this.
Users sign once
Then every tap is a call. No popup. No gas on the loop.
Monad has the room after
Commits land. Other apps can read who showed up, after the session, at the same address.
Open two tabs. Walk. The other tab sees you before Monad does. Same idea as a live room.
Open the demoOnchain games
Real-time movement, combat and physics with authoritative state, settled to Monad at round end.
High-frequency DeFi
Order books that answer in one round trip and settle on Monad, beside the fully on-chain books that hold resting liquidity there.
Agent swarms
Autonomous agents negotiating in one session, committing only the outcome.