Balancer V2

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Balancer V2 is an automated market maker whose pools can hold up to eight tokens at custom weights. Depositors are liquidity providers, and any pool of assets that move against each other exposes them to impermanent loss: the pool sells the rising asset for the falling one, so the LP exits worth less than if they had simply held. That loss cannot be explained to this client in two sentences and is indefensible when it bites, so the whole AMM category is rejected regardless of protocol quality. Balancer is well-built infrastructure and still wrong for a mass-affluent diversification sleeve. It held about $25M in TVL across 92 pools at the 2026-08-14 survey.

Kill criteria: the events that revoke this verdict
• Ships a product line without impermanent-loss exposure that merits its own review

The research file

Mechanism applicability

Balancer V2 documentation identifies customizable AMM pools under a shared Vault, including weighted pools with as many as eight tokens, stable pools and changing-weight liquidity bootstrapping pools. A BPT represents pooled inventory that traders rebalance according to pool math. That directly establishes AMM-LP membership; customizable weights and a shared custody/accounting layer do not remove relative-price rebalancing.

Current observation and control applicability

The DefiLlama protocol API read on 2026-08-15 showed about $25.4M of tracked Balancer V2 TVL across nine networks, and the official V2 documentation and pool interface remained accessible. Pools can have different factories, owners, weights and controls, while Vault and factory deployments vary by network. Current pool composition, governance, contract versions, audits, migrations and incident exposure remain deferred because the shared mechanism already decides the class.

Exit applicability

Balancer V2 permits liquidity removal for BPT holders, including during documented emergency pauses, but the holder exits the pool’s then-current balances rather than the asset mix they would have retained outside the AMM. Pool math, weights, available tokens and price impact determine the realized exit. Continued removability is operationally useful yet does not eliminate the adverse relative-performance outcome covered by the class dossier.

Why the class rule decides

The shared v1 AMM-LP dossier controls this application. Reopen only if Balancer ships an economically separate product without pooled multi-asset or changing-weight inventory that rebalances against the holder as prices move. That product would then require its own review of governance, Vault and pool control, deployments, contracts and audits, incidents, assets, fees, liquidity and stressed exits. A migration, new pool type, or higher TVL would not by itself change the class verdict.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Balancer V2 Docs — pool types · primary · accessed 2026-08-15
  Supports: weighted pools, eight tokens, stable pools, liquidity bootstrapping pools, custom AMM logic
• Balancer V2 Docs — emergency pause and withdrawals · primary · accessed 2026-08-15
  Supports: Vault, WeightedPool, pause authority, liquidity removal, deployment window
• DefiLlama — Balancer V2 survey record · secondary · accessed 2026-08-15
  Supports: current TVL, supported chains, DEX category

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.