Balancer asks former users to check buffer shares and legacy rewards
On October 26, 2026, Balancer asked previous users to verify funds and rewards remaining in the protocol after a review of DAO-owned assets and historical positions.
The notice specifically identifies liquidity-buffer positions associated with Ethena and Gauntlet, as well as legacy $LDO rewards belonging to Gnosis DAO and its stakeholders. Most identified entities had already been notified and initiated withdrawals, but the protocol warns that standard portfolio dashboards like DeBank may miss these positions due to their unique accounting method.
Buffer shares mechanics
Balancer's liquidity buffers operate through the Vault's internal accounting system, where depositors receive recorded shares rather than $BPT tokens. These shares cannot be transferred and can only be removed by the original account or contract that supplied the liquidity. The buffer holds an underlying asset alongside its ERC4626 vault token, providing liquidity for entering wrapped positions without routing conversions through lending protocols.
Unlike standard pool liquidity, buffer funding has different economics: no swap fees, no yield participation, and no connection to the liquidity-mining system. The withdrawal function, removeLiquidityFromBuffer, requires specifying the number of shares to remove, which burns the shares and returns corresponding tokens.
Legacy rewards persistence
The forum notice separately addresses funds remaining in legacy Balancer v2 liquidity-mining contracts. Some users had withdrawn their liquidity while leaving partner rewards unclaimed. The contributor specifically names legacy $LDO rewards associated with Gnosis DAO as an example where exiting a pool can leave associated rewards claimable separately.
Those rewards require a separate check after a liquidity withdrawal: exiting the pool can leave the associated partner rewards unclaimed.
Withdrawal guidance
Balancer directs users to its Portfolio page for checking supported legacy positions and rewards, though coverage is limited to those specific contracts. For users with remaining pool exposure, the legacy interface remains available for withdrawals from Balancer v1, v2 and v3 pools and for unstaking gauge positions.
The manual exit guide emphasizes identifying the correct protocol version before choosing a withdrawal path, as contract names overlap between versions. It requires users to verify addresses against its registry and simulate transactions before sending, with slippage allowances derived from simulations. The guide excludes several specialized pool types and gauges from SDK coverage, directing users to contract recipes for those cases.
Related
