Balancer V3

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

Balancer V3 is an AMM with a shared vault architecture and customizable pools, deployed across nine chains including Ethereum, Arbitrum, and Base. A pooled position rebalances its basket against the depositor as relative prices move, and hooks and dynamic swap fees do not remove that impermanent loss. The rule rejects the AMM category on that mechanism regardless of engineering quality. TVL was $27.2M 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’s current documentation describes V3 as a programmable AMM with a central Vault, standard weighted and stable pools, customizable pool types and hooks, and user add/remove-liquidity operations. A liquidity provider owns a share of pool inventory whose composition changes as traders swap against its pricing function. That establishes AMM-LP membership; the flexibility of weights, hooks or fees does not remove the pooled rebalancing exposure.

Current observation and control applicability

The DefiLlama protocol API read on 2026-08-15 showed about $26.6M of tracked Balancer V3 TVL across nine networks, and official docs and deployments remained current. V3 separates common accounting in the Vault from pool-specific math and hook behavior, so risk and control are pool-, hook- and deployment-specific. Current pool composition, hook authority, governance, contract versions, audits and incidents remain deferred because the shared mechanism already decides suitability.

Exit applicability

Balancer V3 supports proportional and unbalanced liquidity removal through its routers and Vault, but the realized assets and value depend on the pool balances, weights, pricing function, hook behavior and available tokens when exiting. An unbalanced withdrawal changes execution shape rather than eliminating the economic rebalancing already borne by the LP. This directly fits the shared dossier’s explainability and adverse-exit concern.

Why the class rule decides

The shared v1 AMM-LP dossier controls this application. Reopen only if Balancer ships an economically distinct product with no pooled multi-asset or concentrated inventory that rebalances against the holder as relative prices move. That product would then need separate review of pool math, hooks, Vault and router control, governance, contracts and audits, incidents, assets, fees, liquidity and stressed exits. More TVL, a new hook or dynamic fees 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 V3 Docs — programmable AMM overview · primary · accessed 2026-08-15
  Supports: programmable AMM, Vault, pools, hooks, add and remove liquidity
• Balancer — official V3 contracts repository · primary · accessed 2026-08-15
  Supports: Vault contracts, weighted pools, stable pools, hook examples, active development
• DefiLlama — Balancer V3 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.