FeedPlumb · Build
TaskRunner Keeper service
Routine contract maintenance, run on time, within limits your contracts enforce.
TaskRunner at a glance
- Who it will be for
- Vault and protocol teams that need harvests or capped reallocations triggered reliably.
- The problem it will solve
- Maintenance calls that nobody triggers cost yield, and trusting a bot with broad powers is a risk in itself.
Planned features
- Will call only functions your contracts already permit, inside on-chain limits
- Will simulate every call first and send it only if it would succeed
- Your governance will allowlist the keeper; we will never grant ourselves a role
One more feature
- No discretionary trades and no user funds held
How it will work
- Your contracts define the jobs and their limits on chain, for example curator reallocations with caps.
- Your governance will allowlist the keeper address for the role it needs. We will never grant ourselves a role.
- Before every call, the keeper will simulate it and send it only if the simulation passes. If a condition is not met, the contract reverts.
- The keeper will make no discretionary trades and will never hold user funds.
The first version will cover harvests and capped reallocations. Liquidations will not be included. The service currently runs on a test network.
Join the waitlist Opening soon
Hear when TaskRunner opens for new protocols.
Opening soon. Sign-ups and quote requests are not open yet.