# Concentrated liquidity: complete keeper re-centers in one step

## What this does

One call, executed as the Aave manager: raise the RebalanceProxy's per-rebalance band translation cap for the aDOT/HOLLAR concentrated-liquidity vault from 500 to 780 ticks.

## Why

The vault's keeper re-centers the liquidity band once price has drifted more than 660 ticks (~6.8%) from the band's midpoint. The on-chain RebalanceProxy independently caps each re-center at 500 ticks — a safety limit on how far any single rebalance may move the band. Because the cap is smaller than the trigger, every re-center since launch has been clamped: the keeper steps 380 ticks toward the target, the remaining drift falls below the trigger, and the band settles permanently off-centre. An off-centre band pairs the vault's tokens at a skewed ratio, pushing inventory into the one-sided limit position instead of the two-sided range — the direct cause of the lopsided liquidity observed in the pool's first week.

Raising the cap to 780 (= the 660-tick trigger plus two tick-spacings of alignment slack) lets any triggered re-center complete in a single step, so the band always lands centred on the time-weighted average price. The cap continues to bind exactly as designed against anything larger: a compromised or faulty keeper still cannot move the band more than ~8.1% per 6-hour interval.

## Details

- Target: RebalanceProxy 0x8B7Dd119b7edb85D9cF166129DBec5D88DC78C94, setCustomDiff(0xa206D0959813f17c17C87147271C49065438648A, 780)
- Origin: dispatcher.dispatchAsAaveManager (EconomicParameters track); EVM gas 1,000,000 at max fee 0.6 gwei
- Verified by chopsticks dry-run on a fork of mainnet: execution Succeed, 29,080 gas used, and the proxy's storage slot for the vault's translation cap updated to 780
- Preimage: 0x23362c8032520619b34033cbf2ab857cd32f78e717a437b3d8d68154a45181b0 (190 bytes)

No funds move. The change affects only how far the keeper's next re-center may travel; all other proxy limits (width cap 300, 6h minimum interval) are unchanged.


# Concentrated Liquidity Keeper Fix

## What happened
A vault keeps money in a specific price range. A "keeper" moves this range when prices change a lot.

## The problem
- The keeper wanted to move the range by up to 660 ticks.
- A safety limit only allowed 500 ticks per move.
- So each move stopped short and the range stayed off-center.
- This made the pool's money lopsided.

## The fix
- Raise the safety limit from 500 to 780 ticks.
- Now the keeper can finish the move in one step.
- The range lands centered again.

## Good to know
- No money moves. Only a setting changes.
- The limit still stops any move bigger than about 8.1%.
- A test on a copy of the real network worked fine.

call

Executed

Submitted

DecisionDepositPlaced

DecisionStarted

ConfirmStarted

Confirmed

whitelisted_caller

Concentrated liquidity: complete keeper re-centers in one step

root

referendum_canceller

referendum_killer

general_admin

treasurer

spender

tipper

omnipool_admin

economic_parameters

Origin able to dispatch a whitelisted call.

 Origin for spending very high amounts of HDX(<= 50M HDX) from the treasury as well as generally administering it.

Origin able to spend up to 2,222,222 HDX from the treasury at once.

Origin able to spend up to 50K HDX from the treasury at once.

Origin able to perform specific Omnipool-related actions.