AperturefinanceAperturefinance recurring rebalancing by Pool Price or Ratio
Aperturefinance recurring rebalancing repeats liquidity adjustments when a pool-price or token-ratio condition calls for a new position. Pool-price rules respond to relative pricing, while ratio rules respond to the position’s token composition. Both pair a trigger with a separate rebalance target. Compatibility, waiting periods and execution limits determine whether a configured strategy can act.
Updated on
A suitable rule links the change that matters to the range or composition the position should regain. The same trigger can lead to different target ranges, while the same target can follow different triggers.
The short version: For duration-based triggers, the selected TWAP window sets a minimum wait without guaranteeing that the pool holds equally long price history.
Pool Price Versus Position Ratio
Pool-price triggers react to the pool quote, whereas token-ratio triggers react to the selected position’s composition. A quote describes one token in units of the other pool token. A ratio describes that position’s token mix. These inputs answer different questions: whether relative pricing has changed or whether the position has shifted toward one of its assets.
A price rule suits a decision expressed as movement from a reference quote, including absolute-token or percentage conditions. A ratio rule suits a decision expressed as a composition threshold for the position. Price changes can affect both inputs, so the choice concerns which condition should govern the action. The ratio setting does not describe the wallet’s entire balance or every liquidity position held by the address.
Recurring Support Before Trigger Selection
Recurring strategies need a compatible chain and DEX selection before either trigger type can manage the position. ApertureSwap appears on Manta Pacific in the July 2024 liquidity-tool compatibility list, while recurring rebalancing is not supported on Manta. Support for a venue’s other liquidity functions therefore does not establish support for this mode. Changing a trigger from price to ratio leaves that restriction unchanged. The Strategy flow separates chain and DEX selection from the later choice of trigger and rebalance action.
TWAP Duration and Available Pool History
Duration-based settings use a time-weighted average price, or TWAP, to temper responses to brief price movements. The price input is an arithmetic TWAP from the on-chain oracle. Both price-based and ratio-based triggers support a duration setting, so smoothing is a separate choice from the trigger type.
A duration-based trigger waits at least its specified duration before triggering.
Oracle history can cover less time than the duration that the strategy requests. In that case, the TWAP calculation uses only the available history. Pools with low trading volume tend to have fewer stored observations and shorter histories. A selected averaging window therefore describes the requested duration, without ensuring the pool already holds that much data.
An immediate trigger responds to the current on-chain pool price. A duration-based rule adds averaging and a waiting condition. The additional wait can postpone an adjustment even when a brief move crosses the threshold.
Gas, Slippage and Repeated Charges
Execution requires gas and slippage settings that permit the triggered rebalance under the prevailing conditions. The gas ceiling expresses permitted gas expense as a percentage of the position’s dollar value. The strategy’s gas-ceiling control permits settings up to 20% of that value. Actual gas expense varies with execution conditions.
High network gas prices can leave a qualifying trigger unexecuted when its configured gas ceiling is too restrictive.
Slippage settings constrain the pool-price difference between transaction submission and the start of execution. The setting determines minimum output thresholds, and a transaction reverts when its output fails those thresholds. A lower tolerance accepts less price movement during that interval, which can restrict execution when the pool price changes.
The listed rebalance fee is 0.15% of the position value plus $0.15 per rebalance.
Liquidity Intents also include a network-specific gas surcharge for potential failed-transaction gas costs. More frequent rebalancing incurs the applicable charges more often.
A Manta Rejection and a Supported Retry
In this hypothetical case, a recurring-strategy request on Manta Pacific uses a token-ratio trigger and fails with the strategy-creation error containing status code 400. The failure reflects the selected chain’s lack of recurring support. Changing the trigger to pool price would leave the incompatible selection unchanged.
The reader retries on a separate eligible Uniswap V3 position on Arbitrum where recurring support is available. The same trigger type and a ratio-based target define the retry. Assume setup succeeds. The new rule applies to the Arbitrum position; selecting it does not transfer the original Manta position.
After any required duration has elapsed, the trigger qualifies and execution satisfies the configured gas and slippage limits. Liquidity moves into a replacement position with the requested token split and tick-spacing width. That position change marks the completed rebalance. Strategy creation alone had established the rule, without establishing that the liquidity adjustment had already occurred.
Can Both Trigger Types Use the Same Rebalance Targets?
Pool-price and token-ratio triggers both allow selection from the supported rebalance-action formats after the triggering condition is defined. Percentage-based actions specify the distance above and below the future pool or spot price. Token-denominated actions express that distance in units of a pool token. A ratio-based action combines a specified token split with a width in tick spacing.
Ratio-based targets can use a 50-50 or 20-80 split with a tick-spacing width. Those targets are separate from the ratio that starts the rebalance. A strategy also supports different actions above and below its configured price or ratio range. The response to a move in one direction can therefore differ from the response to the other.
A Recurring Rule or a Single Adjustment
Recurring rebalancing repeats when its condition qualifies again, while automated one-time rebalancing performs a single adjustment. Both rebalance paths change a liquidity position’s range or composition. A typical rebalance removes old liquidity, collects its fees, swaps tokens as needed and adds liquidity to a replacement position. Unclaimed fees join that new position.
Revenue-earning limit orders pursue a conversion endpoint instead, with automatic closure after the starting asset fully converts into the desired asset. Repeated range adjustments continue managing liquidity exposure; a fully converted and closed limit-order position completes the asset-conversion task.
Aperturefinance recurring rebalancing questions worth asking
Will Updating a Recurring Trigger Restart Its TWAP Waiting Period?
Updating a duration-based trigger restarts its waiting period. The strategy must wait at least the selected duration again before it can trigger. Changing the setting therefore changes the timing of the next eligible response, even if the market condition already appears to qualify.
Is the TWAP Duration the Interval Between Recurring Rebalances?
A TWAP duration does not specify a fixed interval between recurring rebalances. It sets an averaging period and a minimum wait for a duration-based trigger. Each rebalance still requires the relevant price or ratio condition and permissible execution settings.
Must a New Liquidity Position Exist Before Its Recurring Intent Can Be Configured?
The new-position setup path creates the liquidity position before configuring its recurring intent. After position creation, the Strategy flow returns to the intent-configuration stage. The existing-position path skips new position creation and uses a selected active position.
Are USD-price Triggers Still Supported for Recurring Rebalancing?
USD-price triggers are no longer supported. Pool-price conditions use a token’s price in the other pool token’s units, while ratio conditions address the selected position’s composition. An absolute-token threshold refers to the pool quote, so its units remain part of the condition. A token-denominated quote does not restore the discontinued USD-price trigger type.
Who Pays the Gas for a Recurring Liquidity Intent?
Aperturefinance’s gasless intent model lets solvers pay gas on the user’s behalf and deduct fees in a token the user chooses. Gasless describes the payment arrangement; it does not remove the economic cost of a rebalance. A recurring strategy still has applicable rebalance charges, a gas surcharge and the gas-ceiling control.