Flow of an Intent
An intent moves through Reiy as a protected object. The user locks funds, coordinates solver competition, and succeeds only if Move contracts verify the signed result. For the full set of sequence and state diagrams, see Architecture.1. The user submits an intent
The user chooses the sell token, buy token, amount, minimum payout, deadline, slippage tolerance, and partial-fill preference. The app builds a transaction with the contracts SDK and submits it to the Reiy Move contracts. At admission, the protocol applies . If the user’s minimum is too far below the oracle-anchored fair price after slippage tolerance, the intent is rejected.2. The intent is indexed
The indexer reads Sui checkpoints, decodes Reiy events and object changes, and writes protocol state for coordinators, solvers, and dashboards.3. Fisherman creates an auction round
Fisherman groups open intents that share the same token pair and into a round. After the collection window closes, it asks registered solvers to solve the round.4. Solvers compete
Each solver returns a proposed : how much of each intent it fills, the payout, a , and a . Fisherman validates every response and selects the highest valid score.5. Fisherman signs a certificate
For the winning solution, Fisherman signs a settlement . The certificate names the solver and the exact per-intent payouts, and it expires after a short window.6. Settlement executes on-chain
The winning solver settles in a single Sui transaction. The contracts verify the signature, the solver, the epoch, the deadline, and each user’s protected minimum before any funds move. If any check fails, settlement aborts and the escrow stays put.Epoch and auction lifecycle
Understand contract epochs and Fisherman statuses.
Track settlement
See trader-facing settlement outcomes.