Skip to article content Aerodromefinance

Aerodromefinance can reduce V3 gauge rewards for early claims

- updated

Aerodromefinance can reduce AERO rewards when a position claims early from a penalty-enabled Slipstream V3 gauge. On Base, this deduction applies when the factory’s penalty rate is positive and the position has not reached its pool’s effective minimum stake time. The calculation uses accrued rewards, leaving underlying liquidity outside its scope. Claiming rewards can trigger the deduction while the position stays staked. Withdrawing the position also settles its rewards through the same penalty check.

A zero pool override makes V3 use the factory’s default stake duration when checking an early claim.

V3 Gauge Eligibility

Slipstream V3 introduced configurable minimum stake times and early reward deductions. Existing gauges remain in use alongside that deployment, so the pool’s name alone does not establish its timing rules.

Gauge Identity

A gauge distributes emissions to eligible staked liquidity positions. Its implementation determines whether this early-claim mechanism exists, and the relevant factory supplies its settings. A reward rule documented for V3 should not be applied automatically to older gauges or basic-pool LP tokens.

Position Compatibility

A concentrated liquidity position is represented by a non-fungible token (NFT). The gauge accepts positions from its configured position manager. Its deposit function also requires the position’s token pair and tick spacing to match the gauge. Tick spacing constrains the price boundaries available for the position. Matching token symbols alone does not establish compatibility.


The Pool’s Effective Minimum Stake Time

V3 measures the penalty window from the NFT’s gauge deposit timestamp. It compares that timestamp plus the pool’s effective minimum duration with the timestamp of the executing block.

Each position’s depositTimestamp(tokenId) records its individual gauge entry time. Time spent holding the NFT before staking does not count toward this window. Positions deposited at different times can therefore reach their thresholds separately, even when the same wallet deposited them.

The factory supplies the effective duration through minStakeTimes(pool) , expressed in seconds. A zero per-pool override makes the V3 factory use its default minimum stake duration. A zero override alone therefore does not establish penalty-free claims.

The comparison uses a strict earlier-than condition. At the exact threshold, this timing condition no longer triggers a deduction. A positive rate and an unmet time threshold must coincide. Neither a positive configured rate after maturity nor an early timestamp with a zero rate produces this penalty.


The Reward Amount Subject to Deduction

Accrued emission rewards supply the penalty base. The deduction equals those rewards multiplied by the configured rate in basis points, divided by 10 000. Integer division rounds down in the reward token’s smallest units. Underlying liquidity and unrelated wallet balances are outside this calculation.

A nonzero early-claim deduction is transferred to the minter. The remaining reward amount goes to the position’s recorded depositor. The V3 view function earned(account, tokenId) already subtracts the applicable penalty from its calculated claimable amount. Subtracting it again from that returned value would understate the payout.

Reward Claims and NFT Withdrawals

V3 applies the same reward-settlement routine to a reward claim and a gauge withdrawal. These operations differ in what happens to the position NFT, even when their reward deductions match.

Reward-Only Claims

The recorded depositor’s direct getReward(tokenId) call settles the position’s accrued emissions without withdrawing its NFT. The position remains in the gauge afterward. An early claim can therefore incur the configured deduction despite continued staking. The function does not offer an amount parameter for selecting only part of the accrued reward balance.

Gauge Withdrawals

The recorded depositor’s withdraw(tokenId) call settles outstanding rewards before returning the NFT to its depositor. The minimum stake duration does not itself block an earlier withdrawal; the applicable deduction affects rewards during settlement. Withdrawal removes the gauge stake; the call does not itself burn the position’s underlying liquidity.


Stake Maturity and Active Liquidity

Reaching the stake threshold removes the timing deduction under unchanged settings, while reward accrual follows the position’s active liquidity. Slipstream distributes emissions to staked liquidity within the active price range. A position outside that range does not acquire new emissions merely because its stake timer has matured. Its price boundaries and the pool’s price remain relevant throughout the waiting period.

An emission rate or APR cannot establish that this particular position has reached its timing threshold.


A Claim-Timing Decision for One Staked NFT

For an NFT with positive accrued rewards in a penalty-enabled V3 gauge, claiming before maturity provides earlier access to AERO only if the deduction leaves a positive remainder. Waiting changes that timing condition while leaving exposure to the position’s price range.

  • Confirm that the NFT is staked in a V3 gauge and was issued by its configured position manager.
  • Read the NFT’s deposit timestamp and the effective duration for its actual pool.
  • Compare the intended claim time with their sum, using the applicable factory penalty rate.
  • Recognize that the gauge’s earned result already includes its calculated timing deduction.
  • Match any positive net reward transfer with its ClaimRewards event, and inspect any EarlyWithdrawPenalty event.

Under unchanged settings, a claim executed at or after the threshold avoids this timing deduction. A successful earlier claim records a penalty event when its calculated deduction is nonzero. The NFT remains staked after a reward-only claim. A changed factory rate or effective duration invalidates an estimate made from the earlier configuration; the transaction uses the settings in force during execution.


Configuration Changes Before Execution

V3 reads the penalty rate and effective minimum duration when calculating the deduction. It stores the position’s deposit time rather than a permanent copy of those factory settings. Changes can consequently affect positions that are already staked. A previously observed maturity time is not immutable when its governing duration changes. The authorized stake manager can update these parameters within the implementation’s bounds.

A pending claim has not settled its rewards. Its eventual block timestamp and applicable configuration determine the timing check. The successful transaction establishes the actual deduction and transferred reward amount, so a displayed estimate should not be treated as a completed payment.

Graphic: Aerodromefinance: Configuration Changes Before Execution
Visual summary: Configuration Changes Before Execution

Open full-size image

Questions and answers

Can an Approved NFT Operator Deposit a Position Into the V3 Gauge?

The V3 deposit function requires its caller to own the position NFT. An operator approval alone does not satisfy that ownership check. The deposit also requires a live gauge and a position that matches its configured manager, token pair, and tick spacing. Authorization to manage an NFT does not replace these deposit requirements.

Will a Reward Claim Restart the Minimum Stake Timer?

A reward-only claim does not reset the V3 position’s deposit timestamp. The claim updates reward accounting while leaving that timestamp unchanged. Withdrawing clears the recorded deposit time, and a later deposit records a new timestamp. Keeping the NFT outside the gauge between deposits does not preserve the earlier staking interval.

Does a Voter-routed Claim Bypass the early-claim Deduction?

A Voter-routed claim uses the same penalty calculation for each affected V3 position. The account-based reward function allows only the Voter contract to call it and processes the account’s staked token IDs. Each position’s own deposit timestamp still matters, so a single account can have positions with different timing outcomes.

Is the V3 Penalty Rate Allowed to Consume All Accrued Rewards?

The V3 factory permits a configured penalty rate up to 100% of accrued rewards. This is an implementation bound, not a statement about the active rate. At that bound, an otherwise applicable early-claim deduction can consume the entire reward balance being settled. The calculation still uses rewards as its base.

What Happens If an Early Claim Has No Accrued Rewards?

A claim with zero updated rewards produces no reward deduction. The settlement routine checks for a positive reward balance before calculating and transferring a penalty. This does not disable the factory’s timing settings. A later claim with positive rewards can still incur a deduction if its position remains inside the applicable window.

Which Permission Controls Changes to the early-claim Penalty Settings?

The factory’s gaugeStakeManager permission controls changes to the penalty rate and minimum stake durations. It can set the factory default and pool-specific duration overrides. These administrative settings are separate from the position owner’s ability to claim rewards. Holding the NFT does not grant authority to change its factory’s penalty configuration.

Are Swap Fees Accrued Before Staking Included in the early-claim Penalty?

Previously accrued position fees are collected to the depositor during the V3 gauge deposit. The later early-claim deduction uses accrued emission rewards as its base. Pre-staking swap fees and gauge emissions therefore enter different accounting paths. Staking also changes subsequent earnings from position fees to gauge emissions.