Snapsettle 00 reading Base Sepolia, Unichain Sepolia and Lasna
Snapsettle

Cross-chain intents, settled by Reactive

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…

Scroll to open the clock

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.

    What is new, and what it costs.

    Other intent protocols already repay solvers. What differs is who confirms the fill, who has to act, and how the wait is chosen.

    Who confirms the fillWho must send a transactionSolver repaid after the fillHow the wait is chosen
    AcrossUMA optimistic oracle over bundlesa bundle proposer~30 min to 2 hone rule for every order
    RelayRelay's own oracle, credited on Relay's hubRelayper order; no figure publishedone rule for every order
    Open Intents Frameworka pluggable oracle: Hyperlane, Wormhole, storage proofssomeone submits the attestationdepends on the oracleits reference AcrossResolver publishes a constant 2 h
    SnapsettleReactive, reading both chains' logsnobody for small orders · the solver's confirm for larger ones~2 s · 30 s · 300 s, by valueper order, published through ERC-7683

    The trade. Across's 30-minute window is not waste: it is when a bad bundle can be disputed. Snapsettle trusts Reactive's validators to read two chains correctly instead, and makes that trade per order: small orders settle on sight, larger ones wait and are re-checked on Unichain before any payout. The escrow caps what the Reactive path can release per hour.

    Why Reactive. The check needs an event on Base and an event on Unichain. A contract on either chain cannot see the other. A bot could, and could be faster, but it would be a trusted operator. Reactive makes the observer a network.

    Every order, with its four transactions.

    # Order USDC Policy Open → fill Fill → seen Fill → repaid Total State