When you bridge, a helper pays you on the other chain from their own pocket, then waits 30 minutes to 2 hours to be paid back. Snapsettle pays them back in seconds.
Solver repaid about two seconds after the fill. No contract on Base or Unichain can see both sides. Reactive can.
Reading the bench evidence…
Open it up.
Inside are four contracts on three chains. The user's money waits in an escrow on Base. The solver fills the order on Unichain from its own pocket. A Reactive contract on Lasna sees both events, checks the fill against the order, and calls back to Base to pay the solver.
Nobody runs a relayer for this. The callback is a Reactive transaction.
Every leg, timed.
Median and 95th percentile over the live loops of orders that settle on sight. Each time comes from the clock that is hardest to fool: the chain's own blocks where possible, the solver's own receipt for the fill.
Finality is a setting.
Reactive acts on what it sees, even if a chain later reorganises. So each order carries its own policy: small ones settle on sight; larger ones wait, then the solver's confirm re-reads the fill on Unichain before anything is paid. Solvers read the wait from our ERC-7683 resolver as estimatedDelaySeconds.
It also says no.
A fill with the wrong terms is not paid. A late fill reverts. An order nobody fills goes back to its owner.