Balancer is a weighted-pool AMM with fee-aware liquidity design
Bottom line: Decentralized exchange protocol for pooled token swaps, using weighted liquidity pools, veBAL gauges.
Balancer is a programmable automated market maker where token pools use custom weights, pool-specific swap fees, and shared Vault accounting to route trades and liquidity. Its distinctive angle is the weighted pool: a market holds two or more assets at ratios such as 80/20 or 60/20/20 while still pricing swaps automatically. The former veBAL gauge era ended in Q2 2026, so current analysis separates live pool mechanics from historical emissions.
Reading an 80/20 pool before you trade
An 80/20 Balancer pool expresses a portfolio choice inside an AMM. If the pool is 80% WETH and 20% BAL, the formula gives deeper exposure to WETH and lighter exposure to BAL while preserving continuous swap pricing. That differs from a plain 50/50 constant-product market, where both sides carry equal weight. The weight changes the price curve, the amount of inventory available near the current price, and the way liquidity providers experience token moves.
The design suits assets that do not need to track each other tightly. A pool with WBTC and WETH uses different assumptions from a stablecoin pool, and a pool with three tokens has a different routing profile from a two-token pair. Standard weighted pools in V3 sit under an eight-token Vault limit, and their weights sum to 100%. The minimum token weight is 1%, which keeps the math inside defined operating bounds.
Where swap fees are charged in V3
On Balancer V3, each swap pays a fee on the amount entering the pool. The same fee logic also applies to the non-proportional part of add or remove liquidity operations. If a pool expects equal-value additions across its tokens and a user adds extra inventory to only one side, that extra portion behaves like an implicit swap because it changes the pool balance. Charging the swap fee there protects existing liquidity from free rebalancing.
Fee ranges are set by pool type rather than by one global rule. Standard weighted pools use a 0.001% to 10% swap-fee range, while stable pools use a 0.0001% to 10% range. V3 also supports dynamic swap fees through hooks, where a hook contract supplies the fee for a specific swap. Those hooks create room for volatility-sensitive fees, peg-defense logic, or pool-specific behavior set at registration.
- Static fees are stored in the pool configuration.
- Dynamic fees are computed through a registered hook.
- Weighted-pool fees follow weighted-math security bounds.
- Unbalanced liquidity actions pay fees on the imbalanced portion.
- Protocol fee share is separate from the trader-facing pool fee.
What changed after veBAL gauges stopped steering emissions
Current Balancer governance no longer uses veBAL as an active economic engine. Q2 2026 governance changes halted BAL emissions, ended veBAL fee rights, and moved Snapshot voting to raw BAL across supported production chains. Existing locks remain on-chain until expiry, yet the escrow multiplier no longer adds voting weight and no new emissions flow through gauges.
That change matters for anyone evaluating pool yields. A pool's trading activity, fee setting, token composition, and external incentives now deserve separate review from the old gauge-vote narrative. Historical references to boosted emissions, vote incentives, and veBAL-directed rewards describe the earlier system. The live protocol fee path sends collected protocol fees to the DAO Treasury, with V3 swap fees taking a 25% protocol share and V2 swap fees retaining a 50% protocol share.
The Vault, routers, and BPT receipt behind a position
When someone adds liquidity through Balancer, the position is represented by BPT, a pool-token receipt that tracks the holder's share of that pool. The Vault handles token accounting across pools, while routers give traders and liquidity providers paths for swaps, joins, exits, and more complex multi-step actions. That architecture keeps pool math separate from shared settlement and accounting.
The Vault also explains why pool registration details matter. The pool type, token list, weights, fee bounds, hook configuration, and role accounts shape what actions the pool supports after launch. A hook configuration is fixed when the pool is registered, so a pool with dynamic-fee hooks behaves differently from one with a plain static fee. Developers building custom AMMs use that extension layer instead of rewriting the shared Vault foundation.
Choosing between weighted, stable, boosted, and Gyroscope pools
Balancer keeps several pool families for different market shapes. Weighted pools fit volatile assets and custom portfolio ratios. Stable pools focus on assets expected to trade near parity, such as different stablecoins or liquid staking pairs. Boosted pools combine swap liquidity with yield-bearing assets, while Gyroscope pools use specialized curves for concentrated liquidity and resilient stable-style markets.
The right pool is the one whose math matches the assets. WETH and WBTC belong in a different curve than USDC and DAI. A liquid staking token pair needs rate-provider awareness when the underlying exchange rate changes over time. A concentrated liquidity design narrows capital around a target range, while a broad weighted pool trades flexibility for less precision around one price band.
A first liquidity add starts with the pool math
A practical Balancer liquidity workflow starts by reading the token list, weights, fee, chain, and recent liquidity depth before approving assets. Then the user chooses a proportional add when they want to enter without creating an immediate rebalance. A single-token or uneven add is simpler from a wallet flow, yet the pool charges the relevant swap fee on the imbalance and the final BPT amount reflects the pool's current state.
Before confirming, the important fields are minimum BPT received, token amounts spent, slippage tolerance, gas cost, and whether the pool contains wrapped, bridged, or yield-bearing assets. After the transaction settles, the wallet holds the BPT receipt. Exiting reverses the process: the holder burns BPT and receives pool assets according to the exit type and the pool balance at that moment.
Slippage, imbalance, and contract risk in this design
Risk on Balancer concentrates around pool composition and execution details. Thin pools create worse slippage, very asymmetric weights create less depth on the smaller side, and volatile assets still expose liquidity providers to impermanent loss. Weighted math reduces some exposure patterns in 80/20 designs, but it does not erase the gap between passively holding tokens and supplying them to a live market.
Smart contract risk also varies by pool. A plain weighted pool has a different surface from a pool using hooks, rate providers, external yield tokens, or newer factories. The single most useful caution is concrete: read the pool type and hook status before treating two similar-looking pools as equivalent.
Uniswap, Curve, and Gyroscope as nearby routes
Uniswap V3 specializes in concentrated liquidity positions around price ranges, which rewards active range selection. Curve focuses on efficient swaps between assets that should stay close in value. Gyroscope designs advanced curves for stable and concentrated markets. Use Balancer when custom weights, multi-token baskets, BPT-based liquidity positions, and hook-enabled pool behavior are the main fit for the trade or liquidity strategy.
Frequently asked questions about Balancer
Which fee number should I check before using a weighted pool?
Check the pool's swap fee, the expected price impact, and the protocol fee share as separate items. The pool swap fee is the amount charged to the trade or imbalanced liquidity action. Price impact comes from pool depth and weights. The protocol share is taken from collected swap fees at the protocol level, so it affects fee distribution rather than appearing as a separate wallet charge.
Recovering value from an expired veBAL lock: what changes?
When a legacy lock reaches its natural expiry, the holder follows the unlock flow for the underlying 80/20 BAL/WETH BPT. The key change is economic: the lock no longer earns protocol fees, boosts emissions, or carries escrow-multiplied voting power. The value is tied to the underlying pool-token position and the assets behind it, not to an active veBAL reward stream.
Does an 80/20 pool reduce impermanent loss automatically?
An 80/20 pool changes the exposure pattern by keeping more weight in one asset and less in the other. That structure reduces impermanent loss for moves in the heavily weighted asset compared with a 50/50 pool, while it also creates less liquidity on the smaller side and therefore higher slippage for some swaps. The tradeoff is portfolio-shaped exposure, not a removal of market risk.
Can a weighted pool mix stablecoins with volatile assets?
Yes, a weighted pool supports assets that do not move together, provided the pool uses valid weights and supported token settings. The question is whether the curve fits the market. Stablecoin pairs usually fit stable-pool math better because the assets target a close price relationship. A volatile asset paired with a stablecoin works mechanically, but its weight and liquidity depth strongly influence slippage and provider exposure.