Skip to main content
The agent operates your vault under a narrow on-chain mandate. This page is the plain-language version of that mandate; the contract is the binding one.

​
The agent CAN

  • Plant — open liquidity positions in pools on your vault’s allowlist
  • Tend — re-centre ranges when price moves away from them
  • Harvest — claim emissions and fees, convert them, compound them into positions
  • Rotate — move liquidity between allowlisted venues when yield migrates
All of it inside your vault, and only inside your vault.

​
The agent CANNOT

  • Move funds out of the vault. There is no operator function that transfers value to any external address. Every release path is owner-only and pays only to you.
  • Touch pools outside the allowlist. The allowlist is enforced by the contract, not by policy.
  • Swap without limits. Every conversion is bounded by a hard per-swap loss cap set in the contract. A trade that would cost more simply reverts.
  • Act without limits. Operator actions are rate-limited on-chain; a malfunctioning (or compromised) agent cannot churn your vault.
  • Change the fee. The performance fee is immutable for the life of your vault — no function exists to raise it.
  • Take new deposits on your behalf. Only you can add capital.
  • Resist being fired. You can revoke the operator role at any time, unilaterally.

​
What revocation looks like

Revoke the agent and your vault enters a suspended state: automation stops, positions sit where they are, and every exit path keeps working. The app shows the suspension prominently rather than pretending everything is fine. See Guardrails for the other paths into (and out of) suspension.
The worst case a malicious or fully compromised operator key could achieve is bad management — poorly placed ranges, wasteful churn within the rate limits and swap caps. It cannot achieve theft. That distinction is enforced by the contract, and it is the design’s central promise.