This proposal seeks approval to redistribute assets recovered through a proactive whitehat action on legacy Balancer V2 Composable Stable Pools on Fantom. Approximately $16,000 in assets were secured and are currently held in the Beets multisig.
These assets will be redeemed into FTM where possible, and if approved, converted into S using the most economically efficient route available. Afterwards they will be distributed proportionally to affected liquidity providers (LPs) based on verified historical LP positions. A fixed claims window will be established, after which any unclaimed funds will revert to the Beets treasury.
Following the Balancer V2 Composable Stable Pool exploit on November 3rd, Beets conducted a broader review of all pools. During this review, three legacy V2 pools on Fantom were identified as inheriting the same disclosed attack surface.
Although Beets had already migrated its primary operations from Fantom to Sonic, these pools remained deployed on-chain and represented residual risk. In coordination with the Balancer team, Beets executed a proactive whitehat rescue to secure the remaining funds and eliminate the possibility of third-party exploitation.
Approximately $16,000 was successfully secured and transferred to the Beets multisig, where it is currently held pending a governance-aligned resolution.
The affected legacy pools on Fantom were:
This action was independent of the Sonic incident and reflects Beets’ broader commitment to proactively neutralising inherited risks across historical deployments.
Affected wallet addresses can be found here: https://docs.google.com/spreadsheets/d/1T4DpVPGbWx578aNWT3lHfBW4gjB_Y8KAPsKCtw3XJio/edit?gid=1836289232#gid=1836289232
Converting the recovered value into S allows Beets to align compensation with the protocol’s current home on Sonic, while also ensuring LPs receive the maximum possible value from the recovered assets.
Since many of these LPs are very old and likely inaccessible, we are proposing to put a time limit of 6 months on the claims.
This BIP proposes the following actions:
This proposal resolves a small but important legacy issue in a way that prioritises fairness and transparency. The primary risks relate to operational complexity and ensuring accurate historical verification, both of which are mitigated by on-chain data availability and Music Director oversight.
If approved, contributors will: