Does Balancer accept native ETH or only ERC-20 tokens?

Balancer accepts native ETH through compatible Routers, while the Vault accounts for WETH as the pool token. The Router wraps ETH before settling a WETH debt and can unwrap WETH when delivering an ETH output. Other pool assets follow the ERC-20 transfer model. This convenience does not make ETH and WETH identical inside pool math: the invariant sees WETH, and the wallet still needs the chain's native asset to pay transaction gas.

How long does a Balancer swap take to settle?

A Balancer swap settles atomically in one blockchain transaction. The Router opens the Vault, records token debts and credits, settles every balance and lets the Vault lock again before the transaction succeeds. Wall-clock confirmation time comes from the selected network and its congestion rather than a Balancer waiting period. A pending transaction has not produced a final swap, and a reverted transaction leaves the intended token exchange unexecuted while still consuming network gas.

Are Balancer Pool Tokens transferable ERC-20 assets?

Balancer Pool Tokens are ERC-20 assets representing proportional ownership in a specific pool. BPT supports standard transfers and approvals, while the Vault manages its accounting and emits the required events through the pool-token contract. It also supports EIP-2612 permits for signature-based approvals. Transferability does not fix a BPT's value: its underlying token composition, pool balances, fees and market prices continue changing after the token moves to another address.

Why does a Balancer transaction revert before settlement?

A Balancer transaction reverts when its encoded conditions fail or the Vault finishes with a non-zero token delta. Common causes include an expired Permit2 allowance, insufficient token balance, a minimum-output limit the updated quote no longer satisfies, a network mismatch or a Weighted Pool operation exceeding its 30% swap bound. Querying again reveals the latest amounts. The user then chooses whether to adjust the amount, allowance, gas settings or slippage limit before resubmitting.

Where do ERC-4626 vault shares fit into Balancer?

ERC-4626 vault shares appear in Balancer Boosted Pools, liquidity buffers and Composite Liquidity Router workflows. A rate provider converts the share token into an 18-decimal value relative to its underlying asset, allowing pool math to account for yield accrual. Buffers support wrapping and unwrapping between the share and underlying token. The position therefore combines Balancer pool exposure with the separate rules, liquidity and contract behavior of the underlying ERC-4626 vault.

Balancer is a programmable AMM built around weighted pools and the Vault

Balancer is an automated market maker, software that prices token swaps from pooled assets, with a Vault that keeps the protocol's shared token accounting. Its weighted pools let liquidity providers choose allocations such as 50/50, 80/20 or 60/20/20 instead of using one equal two-token design. A trader receives an algorithmic quote, while the chosen pool's invariant updates balances and arbitrage restores the configured proportions. Liquidity providers receive Balancer Pool Tokens (BPT) representing their share and collect net swap fees retained by the pool. The protocol operates on Ethereum and other EVM networks, with v3 using routers, standardized accounting and extensible hooks. The sections below follow a swap, compare alternatives and explain fees, entry decisions and pool-specific risks.

Updated on 2026-08-10

Jump to a section

It is a programmable automated market maker that lets users swap tokens or supply liquidity to weighted pools, while its Vault centralizes token accounting across pools.

Inside a weighted swap through the Vault

Three core components carry a Balancer v3 swap: a Router receives the instruction, a pool computes the quote and the Vault settles tokens.

The Router unlocks the Vault and opens a temporary accounting state. For an exact-input trade, the pool's invariant calculates the output from the input amount, token balances, normalized weights and swap fee. The Vault records one token as debt and the other as credit before the Router settles both sides. Every non-zero token delta must return to zero before the Vault locks again. If any credit or debt remains, the entire transaction reverts rather than leaving a partly completed exchange.

The Vault also normalizes token arithmetic before pool math runs. USDC uses 6 decimals and WETH commonly uses 18, yet both arrive at the pool as 18-decimal scaled values. Rate providers extend that normalization to yield-bearing assets such as Lido's wstETH. One transaction can combine several Vault operations, so intermediate transfers need not settle separately.

The next choice is the quote: its minimum output protects the trade from an unacceptable state change before execution. The rest of that story sits in Using Balancer.

Balancer beside Uniswap, Curve and swap aggregators

Three design choices separate Balancer from common alternatives: custom portfolio weights, shared Vault accounting and pool logic extended through optional hooks.

Uniswap v3 expresses liquidity-provider choice through price ranges in a two-token pool; liquidity outside its selected range stops earning swap fees. Curve's StableSwap concentrates depth around an expected equilibrium, making it a natural benchmark for correlated assets. Balancer Weighted Pools instead encode fixed target proportions across as many as eight tokens, while Balancer Stable Pools address correlated pairs and baskets. CoW Swap and 1inch solve a different problem: they seek execution routes and may send an order through Balancer, Uniswap or Curve. The pool design and the routing interface therefore answer separate decisions.

What do pool weights change?

Eight tokens is the Vault-level maximum for a Balancer v3 Weighted Pool, and every normalized token weight must be at least 1%.

Weights always sum to 100% and shape both inventory exposure and the price curve. A 50/50 DAI/WETH pool begins with equal value on both sides. An 80/20 pool keeps four times as much value in its heavier asset as in its lighter asset, while a 60/20/20 pool supports three-token exposure. Trades move balances away from those proportions; external price differences then create arbitrage incentives that move the pool toward market-consistent values.

Asymmetry reduces how much of the lighter asset the pool holds, which raises price impact for trades drawing heavily from that side. Standard Weighted Pools cap a swap amount at 30% of the relevant token balance. Unbalanced liquidity operations also keep the invariant ratio between 70% and 300%. These limits bound individual operations; they do not prevent market losses in the underlying tokens.

From wallet approval to pool entry

Two authorizations sit behind a typical Balancer v3 retail add: one ERC-20 approval to Permit2 and one narrow router allowance or signature.

Start on the intended network, select a pool and inspect its tokens, weights, fee rule, hook configuration and displayed depth. Balancer deployments span Ethereum, Arbitrum, Base, Gnosis, Optimism, Polygon and Avalanche, so the wallet network and gas asset must match the pool. Query functions can preview an add, removal or swap without moving tokens. The state-changing call then uses a Router; retail users should not send a transaction directly to the Vault.

The v3 interface defines five add-liquidity kinds and four removal kinds. Proportional entry follows the existing pool composition. An unbalanced or single-token entry embeds a swap-like adjustment, so the unmatched portion pays the pool's swap fee and changes the quote. Donation and custom modes serve narrower pool designs. A newcomer gains the clearest cost comparison by quoting proportional and single-token routes before choosing.

Successful entry mints BPT, an ERC-20 position token whose balance represents a proportional pool share. Removal uses a BPT approval or EIP-2612 permit.

Fees, routing and price impact

Standard Balancer v3 Weighted Pools allow swap fees from 0.001% through 10%, while Stable Pools allow a 0.0001% minimum and the same 10% ceiling.

The pool charges its swap fee on input before the invariant determines output. Price impact then changes the exchange rate as reserves move, while network gas is paid in the chain's native asset. A direct pool with thin reserves may produce a worse quote than a multi-hop route despite using fewer calls. A deeper route can justify added gas. Quote output, price impact and gas belong in the same execution decision.

A static fee enters the pool configuration, while an authorized manager or dynamic-fee hook can change the percentage used for a swap. Hook logic may respond to direction or market conditions within the pool type's bounds. The screen value is therefore specific to the pool and transaction, not a protocol-wide promise. Check the exact amount received rather than comparing fee percentages alone.

Liquidity-provider returns and exposure

Two return sources define a basic Balancer liquidity position: net swap fees retained by the pool and separately disclosed incentives or yield-bearing token accrual.

Weighted Pools suit token pairs or baskets where a chosen allocation matters, including an 80/20 treasury-style position. Stable Pools focus on correlated assets such as stablecoins, while Boosted Pools connect liquidity with ERC-4626 yield-bearing vault shares. BPT tracks the provider's fraction of pool assets and accrued pool value. BAL is different: it is the protocol's governance token, not a receipt for every liquidity position. Holding BAL alone does not grant ownership of a pool's reserves or its trading fees.

Returns remain tied to inventory changes. A provider earns fees because trades rebalance the pool, yet the ending token mix can underperform simply holding the original assets. Lower pool depth increases price impact and may reduce useful volume. Token yield, external incentives and pool fees also carry separate mechanisms, so they should be evaluated as distinct return sources.

Pool-specific risks and protocol status

Four layers deserve separate review in Balancer: token quality, pool mathematics, hook permissions and the specific Vault generation holding the assets.

A weight is an allocation rule, not protection against a token decline. Rate providers add reliance on their conversion logic, and ERC-4626 Boosted Pools add the underlying vault's contract and withdrawal conditions. Custom hooks expand pool behavior, so their permissions and fee logic matter as much as the base invariant. The v3 Vault accepts standard ERC-20 tokens but excludes rebasing and double-entry-point tokens because their accounting does not fit its balance model.

Balancer Labs began winding down as a company in 2026, while the Balancer Foundation, Balancer DAO, Balancer OpCo and service providers continued protocol operations. New pool development and documentation center on v3, although legacy v2 pools can remain on-chain. Users should distinguish v2 from v3 before approving any Router or evaluating a position. Another technical edge case matters to integrators: a Weighted Pool's direct BPT rate call reverts, so compatible Chainlink-based LP oracle tooling is used where external valuation is required.

When does Balancer fit a liquidity strategy?

Three conditions make Balancer a strong fit: custom asset weights matter, the chosen pool has useful depth and its Vault-plus-hook design matches the position.

The protocol is especially distinctive when a two-token equal split is too restrictive or several assets belong in one invariant. It is less compelling when a concentrated range on Uniswap v3 or a specialized Curve market offers materially deeper liquidity for the same pair. Pool selection matters more than brand selection because fees, hooks, reserves and token behavior live at pool level.

Use this short decision checklist before acting:

Confirm the pool is v3 and the wallet is connected to its deployed EVM network.
Match the listed weights to the exposure you intend to hold after trades rebalance inventory.
Compare quoted output, pool depth, swap fee and network gas for the exact transaction size.
Read any hook, rate-provider or ERC-4626 dependency attached to the pool's tokens.
Choose proportional entry when you already hold the required mix and want no embedded imbalance swap.

Once those conditions line up, start with a small quoted operation and read the resulting BPT balance and token amounts. The next decision is ongoing position management: compare the changing pool composition with the allocation you still want to own.

Balancer FAQ

Does Balancer accept native ETH or only ERC-20 tokens?: Balancer accepts native ETH through compatible Routers, while the Vault accounts for WETH as the pool token. The Router wraps ETH before settling a WETH debt and can unwrap WETH when delivering an ETH output. Other pool assets follow the ERC-20 transfer model. This convenience does not make ETH and WETH identical inside pool math: the invariant sees WETH, and the wallet still needs the chain's native asset to pay transaction gas.
How long does a Balancer swap take to settle?: A Balancer swap settles atomically in one blockchain transaction. The Router opens the Vault, records token debts and credits, settles every balance and lets the Vault lock again before the transaction succeeds. Wall-clock confirmation time comes from the selected network and its congestion rather than a Balancer waiting period. A pending transaction has not produced a final swap, and a reverted transaction leaves the intended token exchange unexecuted while still consuming network gas.
Are Balancer Pool Tokens transferable ERC-20 assets?: Balancer Pool Tokens are ERC-20 assets representing proportional ownership in a specific pool. BPT supports standard transfers and approvals, while the Vault manages its accounting and emits the required events through the pool-token contract. It also supports EIP-2612 permits for signature-based approvals. Transferability does not fix a BPT's value: its underlying token composition, pool balances, fees and market prices continue changing after the token moves to another address.
Why does a Balancer transaction revert before settlement?: A Balancer transaction reverts when its encoded conditions fail or the Vault finishes with a non-zero token delta. Common causes include an expired Permit2 allowance, insufficient token balance, a minimum-output limit the updated quote no longer satisfies, a network mismatch or a Weighted Pool operation exceeding its 30% swap bound. Querying again reveals the latest amounts. The user then chooses whether to adjust the amount, allowance, gas settings or slippage limit before resubmitting.
Where do ERC-4626 vault shares fit into Balancer?: ERC-4626 vault shares appear in Balancer Boosted Pools, liquidity buffers and Composite Liquidity Router workflows. A rate provider converts the share token into an 18-decimal value relative to its underlying asset, allowing pool math to account for yield accrual. Buffers support wrapping and unwrapping between the share and underlying token. The position therefore combines Balancer pool exposure with the separate rules, liquidity and contract behavior of the underlying ERC-4626 vault.