FeedPlumb · Build
TaskRunner Keeper service
Routine contract maintenance, run on time, within limits your contracts enforce.
Included in: Custom quote
TaskRunner at a glance
- Who it is for
- Vault and protocol teams that need harvests or capped reallocations triggered reliably.
- The problem it solves
- Maintenance calls that nobody triggers cost yield, and trusting a bot with broad powers is a risk in itself.
What it does
- Calls only functions your contracts already permit, inside on-chain limits
- Simulates every call and sends it only if the simulation passes
- Your governance allowlists the keeper address
- No discretionary trades and no custody of funds
How it works
- Your contracts define the jobs and their limits, for example capped reallocations.
- Your governance allowlists the keeper address. FeedPlumb does not grant itself a role.
- Each call is simulated first and sent only if the simulation passes.
- The keeper makes no discretionary trades and does not hold funds.
The current scope is harvests and capped reallocations. It runs on a test network.
Join the waitlist
Hear when TaskRunner opens for new protocols.
Included in paid plans. Plans and API keys are in your Workspace. Questions go to support@feedplumb.com.