Skip to main content
Solvers are execution providers. They receive quote and solve requests from Fisherman, produce executable outcomes, and settle winning certificates on-chain.

Solver requirements

  • Run an HTTP service that implements the Reiy solver endpoints.
  • Maintain a Sui wallet able to submit settlement transactions.
  • Register or configure a solver address according to the active environment.
  • Price requests within coordinator timeouts.
  • Return valid fills, payouts, protected minimums, and scores.
  • Settle winning certificates before expiry.

Integration path

  1. Understand the core concepts: intent, solver, certificate, protected minimum, and epoch.
  2. Read Solver Overview to understand responsibilities.
  3. Implement quote and solve endpoints described in Fisherman Integration.
  4. Build settlement logic using direct Sui calls or the contracts SDK.
  5. Test that invalid certificates, wrong epochs, wrong payouts, and expired certificates fail safely.
  6. Monitor settlement events through the coordinator or indexed data.

What makes a good solver

  • Fast responses within the quote and solve windows.
  • Conservative validation before submitting on-chain transactions.
  • Reliable inventory, routing, or aggregator access.
  • Clear logging for request IDs, certificate IDs, transaction digests, and failures.
  • Idempotent handlers so retries do not create inconsistent state.

Fisherman integration

Solver-facing endpoint expectations.

Solver settlement

On-chain execution after winning.