Voting Actions - January 12th - 16th
Proposal: [BIP-905] Kill Stale Gauges Q4 2025
Vote: Yes, let’s do it
Reasoning: We support this housekeeping item.
Voting Actions February 2nd - 6th
Proposal: [BIP-907] Update DAO Multisig Signer Set and Adjust Annual Stipend
Vote: Yes, let’s do it
Reasoning: We support this proposal as an operational upgrade to improve execution speed and reliability. Replacing inactive signers strengthens liveness without changing the 6-of-11 security threshold, and the stipend adjustment simply normalizes compensation to market benchmarks in USD terms.
Proposal: [BIP-908] Bounty for Information and Recovery of Stolen Funds
Vote: Yes, let’s do it
Reasoning: We support this proposal, as it officialises the process for the bouty for relevant information/return of stolen funds.
Proposal: [BIP-909] Permissions Update Request #8
Vote: Yes, let’s do it
Reasoning: We are the authors of this proposal. It grants the managed treasury more permissions to handle the assets.
Voting Actions February 9th - 13th
Proposal: [BIP-910] Grant Permissions for New V3 Stable Pool and Weighted Pool Factories
Vote: Yes, let’s do it
Reasoning: We support this update to strengthen the Emergency subDAO’s operational readiness across networks.
Proposal: [BIP-911] Emergency subDAO Signer Swap - Q1 2026
Vote: Yes, let’s do it
Reasoning: We support this update to grant the appropriate operational and emergency permissions for the newly deployed V3 pool factories. It ensures proper parameter management and factory disable capabilities while preserving the existing security framework.
Voting Actions February 23rd - 27th
Proposal: [BIP-912] Deprecate PoL on CoWAMM Positions (BIP-666)
Vote: Yes, let’s do it
Reasoning: We support this proposal as it improves capital efficiency in the Treasury. The PoL positions created under BIP-666 served their purpose during the CoWAMM launch and testing phase, but current utilisation and trading activity are limited. Exiting these pools and transferring the WETH and USDC to the Treasury allows the assets to be redeployed under the existing treasury mandate, while keeping the BAL in the Treasury. This ensures DAO capital is allocated more productively while maintaining flexibility to revisit similar initiatives in the future.
Proposal: [BIP-913] Enable Gauges for svZCHF/ZCHF and ixEDEL/USDC on Ethereum
Vote: Yes, let’s do it
Reasoning: We support enabling these gauges, as they bootstrap liquidity for pools that currently serve as the primary on-chain trading venues for both svZCHF and ixEDEL. Incentivising these markets can help establish initial depth, support price discovery, and encourage ecosystem growth around Frankencoin and Reserve’s Index DTF infrastructure. As these pools mature, Balancer benefits from capturing the associated swap activity and fee generation while expanding the range of assets available on the protocol.
Voting Actions March 9th - 13th
Proposal: [BIP-914] Disable Outdated Oracle LP Pool Factories (v1 and v2)
Vote: Yes, let’s do it.
Reasoning: We support this proposal as a clean-up and risk-reduction measure. Disabling outdated Oracle LP Pool Factories (both the deprecated v1 and superseded v2 versions) removes unnecessary attack surface and prevents accidental or malicious use of contracts that are no longer maintained or aligned with current standards. While these factories are effectively unused, leaving them active on-chain introduces avoidable operational and security overhead.
Proposal: [BIP-915] Grant Pool Creator Fee Permissions to Omni Multisig
Vote: Yes, let’s do it.
Reasoning: Granting the Omni multisig permission to set swap and yield fee percentages enables faster, more coordinated execution, particularly during ongoing pool operations across multiple chains.
This change reduces friction for pool creators while maintaining appropriate safeguards, as all actions remain subject to multisig approval and established governance processes.
Proposal: [BIP-916] Set Network Remapping Manager for StakeDAO
Vote: Yes, let’s do it.
Reasoning: We support this proposal as it enables StakeDAO to efficiently manage cross-chain boost for their veBAL position, aligning with the broader direction of expanding veBAL utility across L2s.
Granting NetworkRemappingManager permissions allows StakeDAO to operate their OnlyBoost strategy effectively, without introducing meaningful risk. The permission is tightly scoped to remapping boost addresses and does not provide access to funds, while the grant-and-revoke pattern ensures no lingering elevated privileges.
Voting Actions March 16th - 20th
Proposal: [BIP-917] Enable Gauges for the Sagix Miliarium Aureum on Ethereum
Vote: Yes, let’s do it.
Reasoning: We support this proposal, as it introduces liquidity hubs to capture meaningful trading volume across key assets. The inclusion of a significant yield-bearing component provides a sustainable source of protocol revenue, even in lower volume environments. This aligns incentives between liquidity providers and the protocol while strengthening Balancer’s positioning as a preferred routing venue.