Strategy rules
One wide, rule-based range per pool. The rules live in the vault account on chain; the keeper can only re-range inside them.
Loading rules
Loading rules
Range history
The vault's range over its last re-ranges, with the active bin at each one
What the keeper can do
Enforced by the vault program, not by the server
- 01Re-range inside the rules
Width, drift trigger, cooldown and the cost cap are read from the vault account on every re-range. A re-range outside them is rejected.
- 02Claim fees into the vault
Claimed fees land in the vault's own token accounts. The service share goes to the published fee recipient; the rest is credited to depositors by share.
- 03Funds stay between the vault and its position
Every re-range removes liquidity into the vault and adds it back to the new range. Token accounts on both sides are fixed in the program.
- 04Your exit is always open
Withdraw and emergency withdraw are signed by you alone and work while the vault is paused or the keeper is stopped.
When this strategy loses money
Price moves and stays away
As the price crosses the range, the position sells the token that is rising and buys the one that is falling. If the price moves and does not come back, your holdings are worth less than simply holding the same tokens. Fees & PnL shows this as "vs simply holding".
Price leaves the range
Out of range, the position earns no fees and holds only one of the two tokens. The keeper re-ranges after the drift trigger and the cooldown, never sooner.
Each re-range has a cost
Removing and re-adding liquidity loses a little value to the pool price on the way. That cost is capped per re-range and every re-range lists it below.
Fees are not compounded for you
Claimed fees wait as your own balance in the vault. They are paid out when you claim or withdraw, and are counted separately from the price change of your position.
Recent re-ranges
Each row is two transactions: remove from the old range, add to the new one