Balancer DAO governs Balancer, a decentralized exchange built as a programmable automated market maker: instead of the fixed 50/50 pools of a Uniswap, Balancer pools can hold up to eight assets in arbitrary weights, which makes them double as self-rebalancing index funds. Its Vault architecture — one contract that holds all pool assets and nets transfers across them — became one of the most-forked designs in DeFi. But Balancer's real significance to DAO governance is its adoption, and eventual abandonment, of the vote-escrow (ve) model: it is the clearest case study of a flagship protocol locking its token for governance, running that system for four years, and then unwinding it in the open. (BAL token docs)

veBAL — the 80/20 vote-escrow lock

BAL launched in June 2020 with a fixed 100M maximum supply, but liquid BAL never carried governance weight. In March 2022 Balancer adopted the veModel, a direct descendant of Curve's veCRV, with one distinctive twist: you did not lock BAL itself. You locked an 80/20 BAL/WETH Balancer Pool Token (BPT) — a liquidity position that is itself 80% BAL — for up to one year, and received non-transferable veBAL whose weight scaled with lock length and decayed toward the unlock date. Locking the LP token rather than the bare asset meant governance participants were also providing protocol liquidity, not just idling tokens in an escrow.

veBAL bundled the same three rights the ve-model everywhere offers: a vote on protocol proposals, a share of protocol fees, and — the load-bearing one — a weekly vote on gauge weights that decided how BAL emissions were split across pools. As with Curve, that gauge vote created a market: Aura Finance rose as an aggregation layer (Balancer's Convex), accumulating veBAL and renting out its emission-steering power to projects that wanted deep liquidity. The vote-market dynamic the Curve Wars made famous replayed on Balancer.

November 2025 — the $128M v2 exploit

On 3 November 2025 Balancer suffered one of the largest DeFi exploits of the year: an attacker drained roughly $128 million from Balancer v2 pools across six chains — Ethereum, Base, Polygon, Arbitrum and others — in under 30 minutes. The bug was not a stolen key or a governance takeover but an arithmetic precision error: a rounding flaw in the Vault's _upscaleArray scaling logic, which — chained through dozens of tiny crafted batchSwap operations executed inside a contract constructor — let the attacker suppress BPT prices and repeatedly extract value. It is a textbook entry for the DAO security and governance-attacks page: the DAO's votes worked fine; the loss came from a subtle invariant-math bug in audited, years-old code. (Check Point Research analysis)

2026 — Balancer Labs winds down, and so does veBAL

The exploit's fallout reshaped the whole project. In March 2026 the founding company, Balancer Labs, announced it was dissolving its corporate entity — a co-founder wrote that after the exploit the entity "became a liability" — while the protocol itself stayed live under DAO stewardship. That forced the DAO to confront a question every maturing DAO eventually faces: is the emission-subsidised ve-machine still worth its overhead once the growth phase is over?

Its answer, ratified in Q2 2026, was to dismantle it:

• BIP-919 (BAL Tokenomics Revamp) — end all new BAL emissions, lift the LP share of swap fees from 50% to 75%, and route 100% of protocol fees to the DAO treasury. With no emissions left, the gauge system had nothing to steer.
• BIP-920 (veBAL Compensation Airdrop) — a 500,000 USDC airdrop to veBAL lockers, compensation for locked positions that would no longer earn incentives.
• BIP-921 (1-BAL-1-vote) — replace the two veBAL Snapshot strategies with a seven-strategy stack counting raw BAL across every production chain: no lockup, no decay. Governance reverted to plain token-weighted voting.

The arc is the lesson. The ve-lock was adopted to bind control to long-term commitment; four years on, with emissions gone and the vote-market's overhead exposed, Balancer judged the lock no longer paid for itself and returned to the one-token-one-vote model the lock was invented to escape.

Balancer was not alone. Months later Pendle retired its own vePENDLE gauge system for a liquid staking token (sPENDLE) plus algorithmic emissions — the same finding, that the ve-lock concentrated power in a rentable few while most holders sat out, reached independently by another of the model's biggest adopters.

How Caper approaches this

Balancer's ve-experiment ran the full loop: lock the token to couple influence to commitment, watch an aggregator tokenise and rent that locked power, then — once emissions stopped justifying the machinery — unwind the whole thing back to plutocratic token-weighted voting. A caper reaches for the same goal the lock was after — influence tied to genuine stake — but without a lock to tokenise or a gauge to fight over. Its voting weight (t·v)/(V·T) combines the tokens a member holds with the votes they have earned through participation, so a large position alone cannot capture control and there is no locked receipt for a third party to aggregate and sell. There are also no emissions: a caper's tokens are minted along a bonding curve, not a weekly inflation vote, so there is no emission stream for a "war" to capture in the first place. And because that same earned weight is each member's pro-rata exit claim on the treasury, control stays coupled to real economic exposure rather than to whoever locked the most this cycle. This is a design contrast, not a claim of superiority — the mechanics are on the linked pages and verified against the caper contract source.

References

• Balancer docs — BAL token and veBAL (primary).
• Balancer Labs, Unlocking the veModel — the 2022 veBAL launch rationale (primary).
• BIP-919, BIP-920, BIP-921 — the 2026 tokenomics revamp and veBAL deprecation, on the Balancer governance forum (primary).
• Check Point Research, How an attacker drained $128M from Balancer (November 2025).
• CoinDesk, Balancer Labs to shut down after exploit (March 2026).