The keeper
An automated account executes bounded liquidity work; the creator decides how much it may spend and how often.
What the keeper may do
The keeper is allowed to call exactly two vault functions, reinvest and reinvestNative, which follow fixed routes and deposit into the vault's own pool. It cannot run arbitrary calls, touch creator earnings, swap out the counterpart or remove liquidity. The creator can call the same two functions.
What the contract cannot police is judgement: the keeper chooses minimum outputs and deposit amounts. A spending cap limits damage from a bad quote but does not prevent it, so weigh the trust you place in it.
The execution policy
New vaults allow 0.02 ETH per run and one run per 15 minutes. The creator can call setExecutionPolicy(maximum, interval, paused) with a cap of up to 1 ETH, an interval of at least 60 seconds, and a pause switch. The fee split is out of reach.
Pausing just parks released funds until execution resumes. A cap of zero stops spending while fees keep arriving and creator claims keep working.
Operational discipline
A well-behaved executor records each intended operation and its hash, checks an existing transaction before retrying after a timeout, and treats an operation as done only after a successful receipt containing LiquidityAdded or PositionCreated. An RPC saying “accepted” proves nothing.
Status on this deployment
The Link contracts are not deployed yet. Live addresses will appear on the Contracts page once they are.