Skip to main content

Epoch and Auction Lifecycle

Reiy has two timing layers:
  • Contract epoch: a simple counter on-chain.
  • Fisherman auction round: the off-chain coordination loop that moves from collecting intents to settling a winner.
The contracts have no on-chain bidding or selection phases. The epoch is only a safety boundary, not an auction clock.

Contract epoch

An intent is created for the current epoch. A is signed for that same epoch, and rejects any intent whose epoch does not match. The epoch advances once a minimum collection time has passed, and a partially filled intent rolls its remainder into the next epoch.

Fisherman auction round

Off-chain, Fisherman runs each round through a short lifecycle: See the round lifecycle diagram for the full state machine.

Round timing

Because there are no on-chain phases, the timeline of a round is set entirely by Fisherman. These are the current testnet windows (each is configurable per deployment): On-chain, the only timing rule is that the epoch advances after a minimum collection time (10s by default). Exact configuration keys are listed in Definitions.

Why this matters

Settlement can happen immediately after Fisherman issues a valid current-epoch certificate. Timing controls such as quote response windows, collection windows, certificate validity, retry policy, and settlement watcher polling all belong to Fisherman, not the contracts.

Auction rounds and certificates

Learn how rounds become settlement authority.

Solution validation and ranking

Review the exact current validation rules.
Last modified on June 23, 2026