PairExecution and permissions
The keeper submits bounded liquidity operations, while the creator retains controls over its execution policy.
What the keeper can do
The configured keeper can execute the vault’s fixed swap and liquidity methods. It cannot send arbitrary calldata to arbitrary destinations, claim creator earnings, retarget the quote asset or withdraw LP positions.
The keeper is nevertheless trusted to choose responsible routes, minimum outputs and liquidity parameters. Spending caps do not make a malicious price quote safe. This trust and the effects of a compromised keeper must be considered before enabling automation.
Creator controls
Each vault starts with a 0.02 ETH execution cap and a minimum interval of fifteen minutes. The creator can pause execution or change the cap and interval within the contract’s bounds.
The creator cannot change the fixed revenue split. Pausing keeps released funds reserved until execution is allowed again. A cap of zero prevents spending without preventing fee receipt or creator claims.
Transaction recovery
Execution should persist the intended operation, transaction hash and receipt state. After a timeout, the existing transaction must be checked before another transaction is sent.
A worker must not mark an operation successful merely because an RPC accepted it. Confirmation requires a successful receipt and the expected vault event.
Activation status
Production automation is not enabled until the Pair deployment, keeper wallet, gas funding and integration verification are complete. A running website or healthy API does not prove that the keeper is active.
The application keeps launch activation separate from ordinary browsing and cost estimation.