Gauge Controller and Reward Distribution Upgrades

Introduction of new gauge types (e.g., for crvUSD markets) with distinct reward logic and interfaces.

DeFi protocols, yield aggregators, and exchanges integrating new Curve assets.

Review new gauge contract ABIs and reward accrual mechanics to update integration logic.

Modification of reward calculation, checkpointing, or claim functions in core LiquidityGauge contracts.

Liquidity providers, yield optimizers, and keeper networks harvesting rewards.

Verify reward accrual accuracy post-upgrade and update keeper bot logic for any new function signatures.

Upgrade to GaugeController logic affecting vote weight accounting, gauge type management, or epoch transitions.

veCRV holders, governance delegates, and DAO tooling platforms.

Monitor governance parameter changes and test vote-casting and weight-query functions against the new controller.

Changes to cross-chain reward streaming logic for Root Gauges on L2s and sidechains.

Bridge operators, L2 sequencers, and multi-chain aggregators.

Validate cross-chain reward delivery and re-sync indexers with any updated event schemas.

Potential deprecation of legacy gauge interfaces or reward-claim helper functions.

Wallets, custodians, and protocols using historical gauge ABIs.

Audit codebase for deprecated function calls and migrate to the canonical gauge interface to prevent transaction failures.

New on-chain events or state changes for gauge activation, reward distribution, and parameter updates.

Data teams, risk analysts, and alerting infrastructure.

Update subgraph schemas and monitoring alerts to track new event signatures and gauge lifecycle states.

Changes to access control, admin roles, or the DAO's ability to adjust reward logic.

Security auditors and protocol risk teams.

Review the new access control model and verify that the expected governance process is enforced on-chain.

Integrators using a cached or hardcoded ABI fail to call the correct claim_rewards or claimable_reward function signature, causing a permanent loss of yield for users.

High

Verify the ABI for the specific LiquidityGauge version against the canonical Curve DAO repository. Run integration tests on a forked mainnet before the upgrade activates.

A governance UI or smart contract applies a user's veCRV weight using the old GaugeController interface, resulting in votes being cast for the wrong gauge or being rejected.

High

Audit all governance tooling and smart contracts that call vote_for_gauge_weights to ensure compatibility with the new GaugeController address and interface.

A crvUSD or factory pool gauge is deployed with a reward token that is not supported by a yield aggregator's claim logic, causing the aggregator's harvest transaction to revert.

Medium

Yield aggregators and harvest keepers must update their reward token allowlists and claim logic to handle new gauge types. Monitor the AddType event on the GaugeController.

A cross-chain bridge or relayer fails to call the updated transmit_emissions function on the ChildChainStreamer, halting CRV reward distribution to an L2 or sidechain.

Critical

Bridge operators and multi-chain deployers must verify the new streamer interface and ensure their relayer infrastructure is updated before the first reward cycle on the new contract.

A keeper bot using a static gas limit for claim_rewards fails after the upgrade due to increased computational cost in the new gauge logic, causing rewards to remain unharvested.

Medium

Keeper operators should simulate the new claim transaction on a fork to establish a safe gas limit and implement a dynamic buffer before the upgrade goes live.

A subgraph's mapping logic fails to handle a new event signature emitted by the upgraded gauge, causing the subgraph to stall and frontends to display incorrect or zero reward data.

High

Subgraph developers must update their ABIs, event handlers, and manifest files to match the new contract. Re-sync the subgraph from the upgrade block.

A protocol that calculates a user's boost using a deprecated working_balances function from the old gauge receives stale data, leading to incorrect reward distribution in a meta-yield strategy.

Medium

Update all off-chain and on-chain boost calculation logic to use the new gauge's working_balances method. Verify the calculation against the upgraded derive_balance logic.

The DAO votes to change the admin fee receiver, but a legacy gauge's withdraw_admin_fees function sends fees to a hardcoded, deprecated address, resulting in a permanent loss of protocol revenue.

Critical

Audit the admin fee withdrawal path in every active gauge version. Ensure the DAO's new fee receiver contract is compatible with all gauge implementations in use.