Balancer weighted pools extend the familiar two-token, equal-weight AMM by allowing other proportions and multiple assets. An illustrative 80/20 pool targets a different value relationship from a 50/50 pool, changing its price response and the liquidity available on each side. The weights describe the pool's pricing model rather than fixed quantities of tokens that can never change. Trades alter reserves, and arbitrage connects the pool's quoted prices to outside markets. Weight selection therefore changes exposure instead of eliminating the consequences of relative price movement.

Balancer's Vault holds and accounts for tokens while individual pool contracts implement their pricing and liquidity rules. This allows several pool designs to use shared infrastructure. In the v3 architecture, more common behavior is handled by the Vault, while routers provide the entry points for user actions. That separation is useful when investigating a transaction: token custody and accounting may occur in the Vault even though the price was determined by a particular pool's contract. The appropriate contracts must be checked together.

A heavily weighted asset can produce less divergence loss than an equal-weight exposure under some price paths, but the less-funded side can create greater trade slippage. Neither feature guarantees that fees outweigh losses. Integration details also matter: the v3 Vault documentation excludes rebasing tokens from its supported standard-token model, so a wrapper may be needed for an asset whose balance changes automatically. A protocol-wide description cannot replace checking the pool version, token behavior, fee configuration, and any additional components used by that specific position.