Onchain settlement
Public settlement batches
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.
Settlement is keeper-driven and runs in dry-run until the reward distributor is configured on Base. Reward settlement is currently disabled (dry-run).
Distributor · PendingSettlement batches
0 on this instanceNo settlement batches on this instance yet
The network is pre-launch and this batch log is process-local. Settlement batches appear here once rewards accrue and the keeper runs — each with its batch hash, receipt and worker counts, and a BaseScan link once submitted. Read the live feed directly:
curl -s https://basis.watch/api/settlement/batches
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). Until the BasisRewardDistributor is configured, batches are computed and recorded in dry-run for verification only — no funds move.
For the reward formula and worker eligibility, see /workers; for the receipts that feed each batch, see /receipts. $BASIS is planned, not live.