Aperture financeAperture finance: LP Rebalancing Trigger Controls
Aperture finance offers price, asset-ratio and scheduled triggers for a one-time rebalance of a liquidity provider (LP) position. Price conditions follow the relationship between the pool's tokens; ratio conditions follow the position's composition. A scheduled trigger uses a selected date. The choice should match the reason for moving liquidity, while the destination settings define the new position. Duration, gas and slippage controls introduce separate execution conditions. A matching trigger therefore does not establish that liquidity has moved.
Table of contents
A matching condition and a stalled rebalance
An automated rebalance becomes eligible when its trigger condition and execution restrictions are satisfied; the automation service can then submit the on-chain transaction. The operation removes liquidity, swaps tokens when necessary and supplies liquidity within the destination range. The selected position and its authorization must support that operation. Saving the trigger alone does not perform the rebalance.
A stalled request needs a narrower response than immediately replacing its settings. An unfinished duration window calls for waiting; updating the trigger restarts that wait. An unacceptable destination range calls for stopping and reconsidering the instruction. Gas or slippage restrictions can also prevent execution. The one-time rebalance documentation specifies automatic trigger expiry after 90 days, so an expired instruction cannot execute merely by waiting longer. Changing those restrictions changes the transaction that the user permits, so loosening them simply to obtain a completed action can defeat the original choice.
Which trigger matches the reason for moving liquidity?
A price trigger fits a price boundary, a ratio trigger fits an inventory boundary and a scheduled trigger fits a calendar decision. These conditions answer different questions even when they occasionally become eligible together. Price asks whether the pool's exchange relationship has crossed the selected level. Ratio asks whether the position's token composition has reached the selected threshold. A date expresses when an action becomes due without establishing that either market condition exists.
Trigger parameters and their execution conditions
The controls below separate the selected condition from restrictions on its execution. Their values come from the saved instruction; none supplies a universal setting for every position.
| Parameter | Selected value or basis | Execution condition |
|---|---|---|
| Price threshold | Pool-token price with an above or below condition | The supported pool-price condition must match |
| Asset-ratio threshold | Selected token ratio within the position | The position's composition must satisfy the condition |
| Scheduled time | Selected execution date | Scheduling does not remove transaction restrictions |
| Duration | Selected TWAP interval for price or ratio triggers | The waiting period applies; available oracle history can limit the averaging window |
| Gas fee ceiling | Percentage of position value; dollar input converts to that basis | A restrictive ceiling can prevent execution |
| Combined effect | The trigger selects when to act | Execution restrictions still govern the action |
Price boundaries and position composition
Pool-price triggers measure one token against the other token in the pool. USD-price triggers are no longer supported. The quote direction therefore matters: reversing the displayed pair changes the meaning of an above or below condition. A threshold copied from a differently quoted display can express the opposite market movement.
Position composition also depends on the selected liquidity range. As trading moves the price through that range, the position holds changing amounts of its tokens. A ratio threshold therefore follows inventory inside that particular position. It does not measure the allocation of the entire wallet.
A concentrated liquidity position stops earning swap fees while the pool price remains outside its range. That boundary explains why waiting for a ratio condition and waiting for a price condition can have different consequences. Moving the range changes the relationship between future prices and the position's composition.
What does the duration setting actually measure?
The duration setting introduces an averaging window and a minimum wait for price or ratio triggers. TWAP means time-weighted average price. It smooths the input used to evaluate the condition, so a brief spot-price crossing need not produce the same outcome as a trigger without that setting.
Aperture uses an arithmetic TWAP from the on-chain price oracle for triggers with a TWAP duration. If the oracle holds insufficient history, the calculation uses the available observations. The chosen duration consequently does not establish that the oracle contains a full window of data.
A duration setting should not be read as proof that every observed price remained beyond the threshold throughout the interval.
Gas permission and the cost of waiting
The gas ceiling controls the execution cost that the instruction permits, expressed against the managed position's value. A dollar entry converts to a percentage for trigger evaluation. That distinction matters when comparing saved instructions: the displayed currency amount and the percentage basis are related, but they are not interchangeable descriptions of a permanent spending limit.
Actual costs depend on transaction work, network gas conditions and the swap needed for the destination position. Aperture also applies rebalance charges and a gas surcharge. The gas ceiling is therefore not a complete statement of total cost. Waiting under a restrictive ceiling preserves that cost boundary while leaving the existing position exposed to further market movement.
The destination range and slippage boundary
The destination controls define the intended position after the trigger becomes eligible. The one-time rebalance setup includes a desired asset ratio and tick range. Its projected liquidity display describes the proposed destination. A threshold that correctly identifies when to act can still accompany a range that does not match the intended exposure.
Ticks mark the permitted price boundaries of a concentrated liquidity position. The selected pool constrains usable tick spacing, so range selection follows the pool's structure.
Rebalancing may require a swap to obtain the token amounts needed by the new range. Slippage settings constrain acceptable execution; a transaction can revert when its outputs fail the calculated minimums. Aperture's liquidity sourcing also includes a same-pool fallback when its aggregation route encounters problems. That fallback supplies another execution path, without removing output restrictions or proving that the resulting trade will suit the user.
Does a scheduled rebalance repeat automatically?
A scheduled one-time rebalance does not become a recurring strategy after execution. Recurring rebalancing is a separate feature that responds repeatedly to price or position-ratio conditions. Aperture's FAQ excludes Manta from recurring rebalance support. Choose the one-time operation when the instruction should end after the selected move. A recurring strategy fits a continuing rule, with separate choices for how later movements reposition liquidity. Its repeated actions also create repeated opportunities for execution costs.
The completed position and the next instruction
A completed rebalance has a successful on-chain transaction and a resulting liquidity position. The starting position record supplies the comparison: its identity, range and token composition describe what existed before execution. The resulting record shows where liquidity moved and which position now holds it. When one of several triggers for the original position executes, the remaining triggers for that position become invalid because the resulting position has a new ID. A saved trigger or projected balance cannot supply that evidence.
A confirmed move does not establish improved returns. It establishes that the transaction changed the position. Reversing that change requires another operation under the prices and costs then available. Before authorizing another move, decide whether the new range still serves the intended exposure and whether the next instruction should respond to price, composition or a date.
What to know about Aperture finance
Must a position leave its range before a rebalance trigger can execute?
A rebalance trigger does not generally require the position to leave its range. Its selected price, ratio or time condition determines eligibility, alongside the applicable execution restrictions. An instruction can therefore call for a range change while liquidity remains active. Leaving the range is a separate position state.
Where are saved rebalance triggers displayed?
Saved triggers appear in the position detail view. That view associates the instruction with the position that it can affect. Reviewing the saved condition is useful when an expected action has not occurred, especially when the displayed market price uses a different quote direction.
Can a recurring strategy use different actions for upward and downward movements?
A recurring strategy supports separate actions for above and below conditions. This applies to its price and ratio trigger configurations. The destination instructions can therefore differ by direction, rather than forcing both movements to produce the same range. Each action still needs destination settings that express the intended exposure.
Is a narrow destination range required for automated rebalancing?
Automated rebalancing does not require every destination range to be narrow. The range is a selected position parameter, subject to the pool's permitted boundaries. Concentrating liquidity more tightly changes where it remains active; it does not make the trigger more accurate or guarantee that the additional management costs will pay for themselves.
What separates price impact from the slippage setting during a rebalance?
Price impact is the effect of the required swap on its execution price, while the slippage setting defines an acceptance boundary for execution. Available liquidity and the amount exchanged influence price impact. Raising the slippage tolerance does not create deeper liquidity or reduce the economic effect of the swap.