# [BIP-922] Recover unclaimed legacy LM MerkleRedeem funds to BizDev Safe

- Space: [Balancer](https://snapshot.box/s:balancer.eth.md)
- Author: 0x58865c1B463Fd2772cD50EB50976A07FaE3Dc6F1
- State: Closed
- Voting type: Weighted
- Start: 2026-07-31 18:00 UTC
- End: 2026-08-04 18:00 UTC
- Votes: 11
- Quorum: 10,000,000 voting power
- Discussion: https://forum.balancer.fi/t/bip-xxx-recover-unclaimed-legacy-lm-merkleredeem-funds-to-bizdev-safe/7089
- Open in Snapshot: https://snapshot.box/#/s:balancer.eth/proposal/0xd56aaecd79ed7d00fdb8f25216e73494b2bfe635480d22c1556af422311a1965

## Results

- Yes, let's do it: 6,473,256.62 voting power, 100.0%
- No, this is not the way: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# Summary

Recover unclaimed $BAL and $LDO incentives still sitting in Balancer’s pre-veBAL `MerkleRedeem` liquidity-mining contracts (~364k BAL and ~350k LDO respectively), and transfer recovered tokens to the BizDev Safe for redeployment as user incentives at BizDev’s discretion.

# Background

Before veBAL, Balancer distributed liquidity-mining rewards via weekly MerkleRedeem contracts ([erc20-redeemable](https://github.com/balancer/erc20-redeemable)): an owner published a merkle root every week; LPs claim with proofs. Unclaimed tokens remain in the contract indefinitely.

Two legacy Ethereum trees are in scope:

- `MerkleRedeem` at `0x6d19b2bF3A36A61530909Ae65445a906D98A2Fa8` (BAL)
- `MerkleRedeem` at `0x884226c9f7b7205f607922E0431419276a64CF8f` (LDO)

These pre-date `MerkleOrchard` and veBAL. Residual orchard balances from the 2023 incident were handled separately via [BIP-196](https://forum.balancer.fi/t/bip-196-redistribution-of-recovered-legacy-incentives/4422). This BIP covers only the legacy `MerkleRedeem` contracts above.

Per [BIP-882](https://forum.balancer.fi/t/bip-882-transitioning-onchain-operations-of-the-balancer-dao-to-balancer-onchain-limited/6859), the BizDev Safe (`multisigs/balancer_bizdev`) manages third-party incentive funds. Given these Merkle trees haven’t seen claims in years, their incentives will be better off being actively managed under the BD mandate.

# Technical Specifications

Both trees can be reseeded with all existing incentives being attributed to the admin. It can then claim the full amount and forward that to the BD safe: https://github.com/balancer/multisig-ops/pull/2842

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

