Onchain settlement
Rewards settle on Base.
Accrued worker rewards are batched and settled on Base. Each batch is public and, once submitted, links to its transaction on BaseScan. A batch hash settles once — settlement is idempotent, with no double-pay — and a batch that fails on-chain leaves its rewards recoverable, never erased.
The settlement flow
A keeper collects accrued rewards into a batch, computes a batch hash over its contents, and settles every worker named in the batch in one Base transaction. The rail below is a structural view of that flow — a visualization, not live production volume.
Settlement rail · Base
1 batchesRewards batch deterministically, then settle once on Base — a batch settles a single time.
1 settlement batches recorded. Each rides accrued rewards to Base and lands as a single, idempotent settlement.
Settlement activity
Batches recorded
1
0 confirmed on Base
Settled rewards (raw)
Confirmed worker BASIS, base units.
Unsettled rewards (raw)
352,800,000,000,000
Accrued from completed jobs, awaiting the next batch.
Settlement batches
1 recorded- batchb09081e79759d7…aa59a448pendingreceipts 1workers 1amount 166,500,000,000,000 base units
How settlement works
A keeper collects accrued rewards into a batch, computes a batch hash over its contents, and submits a single Base transaction that pays every worker named in the batch's receipts.
Settlement is idempotent. A given batch hash settles at most once — re-submitting the same batch cannot pay twice. This is the same no-double-anything invariant that governs jobs and receipts.
All settlement happens on Base (chain id 8453). A batch that fails on-chain rolls its rewards back to unsettled so they settle in a later batch — funds are never lost or double-paid.
For the reward formula and worker eligibility, see /workers; for the receipts that feed each batch, see /receipts.