Fisherman
Fisherman is Reiy’s Execution Coordinator. It is the off-chain service that turns a stream of on-chain into competitive, settleable . It is the orchestration brain of the protocol, but it holds no funds and cannot override on-chain protections.What Fisherman does
Fisherman owns everything between intent submission and on-chain :- Reads on-chain intents and exposes them through an orderbook.
- Groups compatible open intents into .
- Asks registered to quote and to solve each round, within bounded time windows.
- Validates every solver response: fills, floors, token pair, epoch, and expiry.
- Ranks valid solutions by and picks the winner.
- Signs a settlement for the winner and hands off settlement.
- Reissues a certificate if the winner fails to settle before it expires.
What Fisherman does not do
- It does not hold user funds. Escrow lives in the contracts.
- It does not build solver routes. Solvers source their own liquidity.
- It has no on-chain authority. Its signature only lets one solver attempt settlement, and the contracts still enforce every user protection independently.
Round and certificate state
Fisherman tracks the lifecycle of each round and certificate. A round moves from collecting intents, to solving, to a chosen winner, to settling, to settled, with separate states for deadline misses and retries.Why a coordinator instead of an on-chain auction
Running quote collection, batching, and ranking off-chain keeps the on-chain surface small and cheap: the contracts only verify a signature and enforce floors. Windows, batch sizes, and retry policy can be tuned without redeploying contracts, while custody and user safety stay fully on-chain.Auction rounds and certificates
See how a round becomes signed settlement authority.
Fisherman API
The live coordinator API and OpenAPI spec.