# Voting

Balancer governance votes take place on the balancer.eth Snapshot spaceopen in new window. Per BIP-921 (1-BAL-1-Vote Reconfiguration)open in new window, voting power is denominated in raw BAL across all production chains where BAL is deployed. The previous veBAL-based strategies have been retired.

# Strategy Stack

The space uses a seven-strategy stack, one strategy per production chain where BAL is deployed. A voter's total voting power is the sum across all seven chains. There is no single named strategy — the Ethereum strategy is a composite, and the six L2 strategies use Snapshot's standard erc20-balance-of-delegation.

The six L2 strategies count raw BAL balance plus any BAL delegated to the voter on that chain. The Ethereum strategy nests a Snapshot delegation wrapper around a contract-call strategy that invokes BalVotingPower.votingPower(voter).

# BalVotingPower Contract

The Ethereum strategy reads voting power from BalVotingPower.sol — a singleton, stateless view contract (sourceopen in new window, deployed at 0x411e723E6652347FF3Dd31749913A834e3D43DB4open in new window) — exposing a single function:

function votingPower(address user) external view returns (uint256);

For the given voter, the contract returns raw + fromBpt, where:

1. raw — the voter's raw BAL balance: BAL.balanceOf(user).
2. fromBpt — the BAL portion of all BPT attributable to the voter, computed by summing:
   • the voter's directly-held 80/20 BAL/WETH BPT balance, plus
   • the BPT amount still locked inside veBAL for the voter, read as veBAL.locked(user).amount (face value, not the decay-adjusted balanceOf),
   • then converting the combined BPT amount to its underlying BAL equivalent via the pool's current BAL/total-supply ratio.

Hardcoded references in the contract:

The veBAL escrow multiplier no longer confers any extra weight — only the underlying BAL inside the lock is counted, at its face value. Delegation is not handled by the contract itself; it is layered on by the outer Snapshot delegation strategy (see below).

# Delegation

Voters delegate voting power per chain through Snapshot's Delegate Registryopen in new window at the same deterministic contract address across all seven networks. To use the same delegate everywhere, register your delegate on each chain where you hold BAL.

The 45% individual delegation cap introduced by BIP-521open in new window has been removed.

# Quorum

# Proposal Submission

The previous 200,000 veBAL submission threshold has been removed. Only registered members of the balancer.eth Snapshot space can submit proposals. Per BIP-838open in new window, proposals must first be discussed on the Balancer Forumopen in new window as an RFC.

See the Governance Process for the full proposal lifecycle.

# What Requires a BIP?

Following BIP-918open in new window, the core team holds an operational mandate over day-to-day decisions — protocol fee parameter changes, vendor selection, chain deprecation, partner deal negotiations — which do not require a Snapshot vote. The following still require a Snapshot vote:

• New pool factories
• Novel pool types
• New chain deployments
• Changes to BAL supply or minting parameters
• Treasury actions beyond routine operations

# Related Documentation

• Governance Overview
• Governance Process
• Snapshot — Snapshot platform basics
• BAL Token
• BIP-921 (1-BAL-1-Vote)open in new window