Skip to documentation
Resources/Docs
DevelopersSinjoh v2

Keepers & automation

Authorized jobs, economic execution, primary/backup coordination and bounded service authority.

2 min read·
On this page

What keepers run

Job familyWork
Market maintenanceRecenter/fold when needed, collect reserve buckets, raise funded floors and handle deferred destruction.
RevenueCollect creator/platform fees and execute independently accounted route actions.
ReservesSweep eligible unsolicited assets and realize earned protocol fees.
YieldDeposit eligible idle treasury, realize available profit and recover draining/shut positions.
RewardsPush valid payouts, convert assigned stock credits and settle market shares.
Automation earningsConvert collected earnings to gas currency under approved paths and configured economics.

Chain state is the work queue

Jobs have deterministic primary assignment, with another approved keeper taking work that remains due after the configured backup delay. Successful on-chain state prevents duplicated work. There is no separate shared queue service that grants authority or overrides contract eligibility.

Cadences and profitability margins are operating configuration. They are not governance timelocks and do not give a keeper permission to change a market’s taxes, route allocation or recipients. A skipped or failed job remains distinguishable from a completed receipt.

Gas funding and execution boundaries

Keeper signers advance transaction gas. Fee collection and eligible maintenance can pay Automation balances under their contract rules; sweep economics use earned fee revenue rather than taking an extra deduction from protected reserves. Low-balance alerts do not automatically authorize a treasury transfer.

Only recorded keepers can run restricted route/conversion/sweep jobs. Anyone-callable maintenance or payout functions remain bounded by their own validations. Simulation, actual submission, successful receipt and completed business outcome are separate milestones.

What operating evidence should show

  • The specific chain, hook/pool, route, asset or reward round being processed.
  • Whether work was due, skipped, simulated, submitted, successful or retained for retry.
  • Actual receipt, gas and output, not only a predicted quote.
  • Chain/indexer lag, service health and unavailable telemetry without conflating them.
  • Sanitized logs and metrics that exclude signing keys, tokens and credentialed endpoints.