Balancer V3

Balancer V3 is outside the current firm shelf because its structure falls within the amm-lp policy class. This is a firm policy classification, not a negative quality rating or a client trade instruction. We retain below the factual evidence on its mechanism, control, losses, and exits.

Review triggers: events that reopen the verdict
• Ships a product line without impermanent-loss exposure that merits its own review

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.

The research file

Mechanism applicability

Balancer’s current documentation describes V3 as a programmable AMM with a central Vault, standard weighted and stable pools, custom pool types and hooks, and operations that let users add or remove liquidity. A liquidity provider owns a share of pool inventory. Its composition changes as traders swap against the pool’s pricing function. That makes it an AMM-LP; flexible weights, hooks, or fees do 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. Official docs and deployments remained current. V3 puts common accounting in the Vault and leaves pool-specific math and hook behavior to each pool, so risk and control depend on the pool, hook, and deployment. We have not reviewed current pool composition, hook authority, governance, contract versions, audits, or incidents because the shared mechanism already decides suitability.

Exit applicability

Balancer V3 supports proportional and unbalanced liquidity removal through its routers and Vault. The assets and value received depend on the pool balances, weights, pricing function, hook behavior, and available tokens at the time of exit. An unbalanced withdrawal changes how the trade executes but does not remove the economic rebalancing the LP has already borne. This directly fits the shared dossier’s concern about explaining the product and exiting under stress.

Why the class rule decides

The shared v1 AMM-LP dossier controls this review. Reopen it only if Balancer ships an economically distinct product without pooled multi-asset or concentrated inventory that rebalances against the holder as relative prices move. That product would need a 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.

Class rule

The amm lp class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.

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 research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.