Balancer proposes moving Rocket Pool alliance treatment to its v3 liquidity pool

What happened

Balancer governance received BIP-896, proposing an alliance addendum after Rocket Pool moved its primary Ethereum liquidity from a deprecated Balancer v2 pool to a Balancer v3 pool.

What changed

The proposal would remove the v2 rETH/WETH pool and add the v3 rETH/waEthWETH pool to the special Rocket Pool alliance revenue-sharing treatment.

What did not change

The candidate does not establish that the proposal passed or executed, that incentives became active, or that rETH redemption and Rocket Pool protocol controls changed.

Confirmed

• The proposal identifies the v2 rETH/WETH pool at 0x1e19cf2d73a72ef1332c882f20534b6519be0276 for removal.
• It identifies the v3 rETH/waEthWETH pool at 0x1ea5870f7C037930CE1d5d8d9317c670e89e13E3 for addition.
• The proposed incentive token remains RPL.
• The proposal states that Rocket Pool had migrated its primary liquidity pool to Balancer v3.

Still open

• The Snapshot candidate does not establish the final vote result or execution status.
• The resulting incentive amount, duration, and realized effect on rETH liquidity are not stated.
• The candidate references a prior security-driven v2 deprecation but is insufficient to establish that separate incident's cause or scope.

What it means for an advisor

• Monitor whether alliance treatment becomes operative and whether liquidity migrates successfully to the named v3 pool.
• Reassess executable rETH secondary-market depth after migration rather than inferring liquidity from governance approval.
• The proposal does not fire Rocket Pool's existing discount, operator-count, redemption, or protocol-revenue kill criteria.