PancakeSwap Infinity offers two pool models that can quote the same token pair while exposing liquidity providers to different mechanics. CLAMM concentrates liquidity across a continuous price range. LBAMM divides liquidity into discrete price bins and applies constant-sum pricing inside an active bin. Choosing between them requires more than comparing the displayed APR: range width, bin step, inventory conversion, fees, rebalancing and hooks can change the result.
Last reviewed: October 3, 2026. PancakeSwap Infinity deployments, supported chains, pool types, interfaces, hooks and fee settings can change. Anyone can create tokens and pools, so appearance in the interface is not an endorsement. Verify current contracts, token addresses and official documentation before signing. This independent guide is educational and is not financial advice.
What is PancakeSwap Infinity?
PancakeSwap Infinity is a modular decentralized-exchange architecture. Unlike earlier designs where each pool required a separate contract, Infinity uses a shared PoolManager, commonly described as a singleton. Individual pools are identified within that system.
Infinity supports multiple pool types and optional hooks. At launch, its principal liquidity models were:
- CLAMM: Concentrated Liquidity Automated Market Maker.
- LBAMM: Liquidity Book Automated Market Maker.
A swap interface can route through Infinity, v3 or v2 liquidity. The trader may not choose the pool model manually when the router finds a better route, while an LP must select a specific pool and understand its rules.
CLAMM vs LBAMM at a glance
| Area | CLAMM | LBAMM |
|---|---|---|
| Price organization | Liquidity concentrated across selected continuous ranges | Liquidity assigned to discrete price bins |
| Pricing inside active liquidity | Concentrated constant-product behavior | Constant-sum behavior within an individual bin |
| LP configuration | Lower and upper price boundaries | Bin step and liquidity distribution across bins |
| Position representation | Non-fungible position with unique range settings | Fungible claims for matching bin allocations under the model |
| Out-of-range behavior | Position becomes one-sided and stops earning swap fees | Inactive bins wait until market activity reaches them |
| Single-sided liquidity | Possible outside the current price range | Native distribution can place one-sided liquidity in selected bins |
| Management style | Choose and rebalance price ranges | Choose bin step and distribution shape |
| Main misunderstanding | Narrow range is assumed to mean higher guaranteed yield | “Zero price impact” is assumed to mean zero LP loss |
How CLAMM works
A CLAMM lets an LP deploy assets only over a selected price interval. Capital inside that interval participates in swaps and can earn fees. Concentrating the same deposit near the current price can provide deeper effective liquidity than spreading it across every possible price.
The trade-off is range dependence. If market price moves below or above the selected interval, the position becomes inactive. It will generally consist almost entirely of one token and no longer earn normal swap fees until price returns or the LP repositions.
Concentrated constant-product behavior
The familiar constant-product relationship is often summarized as:
x × y = k
Concentrated liquidity modifies how LP capital participates by allocating it between boundaries rather than across the entire positive price curve. Within the active range, swaps continuously change the token composition.
The formula does not promise a constant dollar value. It defines pricing behavior. Asset prices, fees and the chosen range determine the financial outcome.
How LBAMM works
LBAMM divides the price curve into discrete bins. Each bin corresponds to a specific price level determined by the pool’s bin step. Liquidity can be distributed across one or many bins.
Inside an individual active bin, the model uses constant-sum behavior, commonly summarized as:
x + y = k
Trades can exchange the two assets at that bin’s fixed price until one side of its available liquidity is depleted. The active trading point then moves into another bin with a different price.
What “zero price impact inside a bin” means
A trade contained entirely within one sufficiently funded LBAMM bin can execute at the bin’s price without moving along a continuous curve inside that bin. This is the basis for the “zero price impact” description.
It does not mean:
- every trade has zero slippage;
- the route cannot cross multiple bins;
- the market price cannot change;
- fees are zero;
- an LP cannot end with an unfavorable inventory;
- there is no loss relative to holding.
A trade larger than available liquidity in one bin moves through additional bins. Its average execution price changes as it crosses them.
Price range versus price bins
| Decision | CLAMM | LBAMM |
|---|---|---|
| Where should capital work? | Between lower and upper boundaries | Across selected discrete bins |
| How precise is the placement? | Determined by ticks and range | Determined by bin step and distribution |
| How does price advance? | Continuously through active range segments | Fixed inside a bin, then moves bin to bin |
| When does capital become inactive? | When price leaves the range | When trading is occurring in other bins |
What is bin step?
Bin step defines the price spacing between adjacent LBAMM bins. A smaller step creates more granular price levels; a larger step separates them more widely. Pool configuration and fee behavior can be connected to this design.
Do not select a pool solely because its bins appear more precise. Evaluate active liquidity, volume, fee parameters, volatility and how much of the position is likely to remain near the active bin.
CLAMM range selection
A narrow range concentrates capital and can capture more fees per deposited dollar while price stays inside. It also becomes inactive sooner and converts inventory more aggressively as price approaches an edge.
A wide range is less capital-efficient near the current price but tolerates larger movement before becoming inactive. It is not automatically passive: fees may still fail to compensate for asset-price changes.
| Range | Potential advantage | Main cost |
|---|---|---|
| Narrow | High concentration near current price | Frequent out-of-range events and rebalancing |
| Medium | Balance between concentration and tolerance | Still requires a market view |
| Wide | Remains active through broader movement | Lower capital efficiency near spot |
| One-sided outside spot | Can act like a conditional conversion zone | Earns only when price enters the selected range |
LBAMM distribution shapes
An LBAMM position can distribute liquidity across bins using shapes offered by the interface. Names and availability can change, but common concepts include:
- Spot or uniform: spreads liquidity relatively evenly across selected bins.
- Curve: concentrates more liquidity near the active price and less toward the edges.
- Bid-Ask: places more liquidity away from the active center, reflecting buy and sell inventory intentions.
- Custom: allows a more deliberate bin-by-bin distribution where supported.
A shape is not a risk rating. A concentrated curve can become inventory-sensitive quickly, while a wider distribution can leave much of the capital inactive.
Position tokens and ownership
CLAMM positions have unique range, fee and liquidity parameters and are represented as non-fungible positions. Two deposits in the same pair can have different boundaries and therefore different results.
LBAMM liquidity is designed around fungible representations for equivalent allocations within bins. This can simplify composition and adjustments in compatible workflows, but users must still understand which bins and pool parameters their claim represents.
Never transfer an LP position token unless the recipient and consequence are understood. It represents a claim on the underlying liquidity.
Active and inactive liquidity
Liquidity earns ordinary swap fees only when trades interact with it.
In CLAMM, the position is active while market price lies within its range. Outside it, the LP typically holds one asset and earns no new swap fees from that position.
In LBAMM, bins away from current trading are inactive until the active price reaches them. A distribution can therefore contain substantial deposited value that is not currently earning.
Single-sided liquidity
Both designs can support one-sided strategic placement, but the mechanism differs.
In CLAMM, a range entirely above or below the current price can begin with one token. As price moves through the range, swaps convert it toward the other token.
In LBAMM, liquidity can be allocated to bins on one side of the active price. This can resemble a ladder of limit orders, but execution, fees and smart-contract behavior differ from a centralized limit-order book.
“Single-sided” does not mean exposure to only one asset forever. The purpose of liquidity is to trade inventory as price reaches it.
Impermanent loss in CLAMM
Impermanent loss is the difference between the LP position and the value of simply holding the original assets, measured at the same later prices. Concentration can magnify this difference because the position converts more inventory within a narrower interval.
If price leaves the range, a CLAMM LP may hold mostly the asset that underperformed relative to the other. Fees can offset part or all of this difference, but that is an outcome to measure, not a guarantee.
Does LBAMM eliminate impermanent loss?
Official descriptions sometimes say constant-sum trading inside a bin eliminates price impact and impermanent loss within that bin. This statement must be interpreted narrowly.
While the bin trades at a fixed price, an LP’s inventory can be converted as traders consume one side. When the market advances across bins, the LP can end with a different asset mix than a holder. That creates inventory and divergence risk across the full position and time period.
Therefore, do not translate “no IL inside one bin” into “the LBAMM position cannot underperform holding.” Compare deposited quantities, withdrawn quantities, fees and current prices.
A simple CLAMM inventory example
An LP deposits Token A and USDC around a current price of $10, using a range from $8 to $12.
- Near the lower boundary, the position contains more Token A.
- As price rises, swaps convert Token A toward USDC.
- Above $12, the position is mostly or entirely USDC and inactive.
- If Token A continues rising to $20, the LP misses further upside compared with holding the original Token A amount.
Fees earned between $8 and $12 must be compared with that opportunity cost and gas.
A simple LBAMM inventory example
An LP distributes Token A and USDC across bins surrounding $10.
- Trades within the active bin occur at its set price while liquidity remains.
- As buyers consume Token A, that bin becomes more USDC-heavy.
- When the bin is depleted, activity moves to an adjacent price bin.
- A continuing trend can convert multiple bins and leave the LP concentrated in one asset.
The path is discrete rather than continuous, but the LP still acts as a counterparty to market flow.
Fee tiers and fee income
Pools can use different fee configurations. A higher percentage does not automatically produce higher LP income because traders and routers consider total execution quality.
Estimate:
Net LP result = fees earned − gas − hook charges − divergence from holding − other incentives or costs
APR is backward-looking or estimated and can change quickly when volume, liquidity, token price or incentives change.
Dynamic fees
An Infinity pool can use a hook that changes fees according to configured logic, such as market volatility. Dynamic fees may charge more when adverse-selection risk is higher and less during calmer periods.
The displayed base fee may not describe every future swap. Inspect whether the pool uses a hook, who deployed it, what permissions it has and how fees are calculated.
Hooks add features and risk
Hooks are smart-contract modules that can run around pool actions. They can implement dynamic fees, discounts, incentives, order-like behavior and other custom logic.
A hook-enabled pool introduces code and assumptions beyond the core pool model. CLAMM versus LBAMM does not determine whether a hook is safe. Evaluate the exact pool and hook address, audit information, permissions and upgradeability.
Singleton architecture
Infinity stores many pools in one PoolManager rather than deploying a complete contract for every pool. PancakeSwap states that this can dramatically reduce pool-creation cost and improve complex routing efficiency.
For users, the main practical lesson is not to send tokens directly to an address copied from a block explorer. Interact through the verified interface or audited integration so the correct pool identifier and settlement logic are used.
Flash Accounting
Flash Accounting tracks intermediate balance changes during a transaction and settles net token movement at the end. Multi-hop routes can avoid repeatedly transferring tokens between separate pool contracts.
This can reduce gas, but it does not remove price impact, token taxes, hook fees or slippage. The transaction preview remains essential.
Native token support
Infinity can support native gas tokens directly in eligible pools, reducing the need for explicit wrapping and unwrapping in some routes. The exact chain and pool determine whether the native or wrapped version is used.
Never assume two assets with similar symbols are interchangeable. Verify the network and contract address for every ERC-20 or equivalent token.
Trader perspective: which pool is better?
A trader usually wants the best net output, not a favorite AMM label. The router may compare CLAMM, LBAMM, v3, v2 and other routes.
| Factor | What to inspect |
|---|---|
| Quoted output | Minimum received after route and fees |
| Price impact | Effect of trade size on pool prices and bins |
| Gas | Network fee for the complete route |
| Pool fee | Static or dynamic fee on each hop |
| Hooks | Extra logic, discounts or charges |
| Token risk | Contract, transfer behavior and authenticity |
| Slippage | Difference allowed before transaction reverts |
Universal Router and split routes
PancakeSwap’s router can search multiple liquidity sources and may split or combine routes. A swap can pass through more than one pool version or intermediate token.
Review the route when the interface exposes it. A better quoted output may involve more smart contracts, gas or token approvals. Avoid manually forcing a pool unless there is a documented reason.
Price impact versus slippage
Price impact is the change caused by the trade relative to available liquidity. Slippage tolerance is the maximum unfavorable movement the user permits before the transaction should revert.
An LBAMM trade can have zero price impact within one bin and still experience a different final result if it crosses bins, pool state changes before execution or fees apply. Setting extreme slippage does not improve liquidity; it increases the range of outcomes accepted.
LP perspective: choose the market-making rule
Providing liquidity is an active market-making decision even when the interface makes it look like a deposit product. The LP chooses where to sell one asset for another and receives fees for taking that inventory risk.
CLAMM asks: within which continuous price interval should my inventory trade?
LBAMM asks: in which discrete bins, and with what distribution shape, should my inventory trade?
Which model fits stablecoin pairs?
A tight CLAMM range can concentrate capital near parity, while LBAMM can place deep liquidity in nearby bins. Either can be efficient when the assets remain correlated.
The main risk is not ordinary small movement but a depeg. A tight position can convert strongly into the weakening asset. Do not assume stablecoin symbols guarantee equal redemption quality or issuer risk.
Which model fits volatile pairs?
Volatile pairs require a wider tolerance or frequent management. A narrow CLAMM range can generate fees during sideways movement but become inactive quickly in a trend.
LBAMM can distribute inventory across many bins and use a shape matched to a view, but a strong directional move can consume successive bins. Wider distribution reduces concentration and may leave capital inactive.
Which model fits correlated assets?
Wrapped versions of the same asset or liquid staking tokens may trade within a relatively narrow relationship. Concentrated strategies can be efficient, but bridge, wrapper, validator, oracle and redemption risks remain.
A divergence caused by a security or liquidity event can move through every range or bin far faster than expected.
Which model fits a new token?
Neither model makes a new token safe. New-token pools can have thin liquidity, transfer taxes, mutable code, concentrated ownership, fake symbols and malicious hooks.
Verify:
- contract address from an independent official source;
- ability to buy and sell;
- holder distribution and liquidity ownership;
- mint, pause, blacklist and fee permissions;
- pool and hook deployers;
- audit scope and known limitations.
Rebalancing
Rebalancing means removing, converting and redeploying liquidity into a new range or bin distribution. It can restore activity but crystallizes the current asset composition and incurs gas, fees and possible taxes.
Measure whether additional expected fees justify:
- withdrawal and collection costs;
- swap cost to restore the intended ratio;
- new approval and deposit gas;
- time spent monitoring;
- execution risk during the adjustment.
Do not chase APR by constantly moving
Displayed APR can rise because recent volume spiked or liquidity fell. Moving after the spike can expose the LP after activity normalizes. Frequent rebalancing may transfer most income to gas and arbitrage.
Use a written rule: price boundary, time interval, fee threshold or risk event that justifies repositioning. Record every cost.
How to compare two real pools
- Confirm chain, pair and token contracts.
- Identify CLAMM or LBAMM.
- Inspect fee configuration and hooks.
- Compare current active liquidity, not only total value.
- Review volume over multiple periods.
- Estimate fee share for the chosen range or bins.
- Model a rising, falling and sideways market.
- Estimate gas for deposit, collection, rebalance and withdrawal.
- Compare against simply holding the tokens.
- Start with an amount small enough to treat as a test.
Metrics for CLAMM
- current price relative to lower and upper boundaries;
- percentage of time in range;
- active liquidity near current price;
- fee tier and volume;
- token quantities at current price and range edges;
- unclaimed fees;
- gas and rebalancing frequency;
- performance versus holding.
Metrics for LBAMM
- active bin and selected bin step;
- liquidity distribution shape;
- inventory in each relevant bin;
- number of bins crossed by typical trades;
- static or dynamic fee behavior;
- active versus inactive capital;
- fees and incentives by bin exposure;
- performance versus holding.
Security checklist before adding liquidity
- Open PancakeSwap through a verified bookmark.
- Confirm network and token contract addresses.
- Identify pool type, fee, bin step or range.
- Inspect every attached hook.
- Read token approval amount and spender.
- Avoid unlimited approvals when unnecessary.
- Simulate the position under large price moves.
- Reserve native gas token for removal.
- Use a separate wallet for experimental DeFi activity.
- Deposit a small test before scaling.
- Save transaction hashes and initial token quantities.
- Review and revoke obsolete approvals later.
Common CLAMM mistakes
- Selecting the narrowest range because displayed APR is high.
- Forgetting that out-of-range liquidity earns no ordinary swap fees.
- Ignoring how inventory changes near each boundary.
- Rebalancing without counting swap and gas costs.
- Comparing fee income without comparing against holding.
- Assuming an NFT position has a fixed asset composition.
Common LBAMM mistakes
- Reading “zero price impact” as “zero investment risk.”
- Ignoring trades that cross multiple bins.
- Selecting a distribution shape without understanding inventory.
- Assuming inactive bins continue earning.
- Ignoring bin step and dynamic fee logic.
- Treating a bin ladder exactly like cancellable limit orders.
Troubleshooting CLAMM positions
The position stopped earning fees
Check whether price is outside the selected range. The position may be inactive even though the assets remain visible.
The position contains only one token
This is expected near or beyond a range boundary. Swaps have converted the inventory according to the pool curve.
Collected fees are lower than the APR estimate
APR may use recent volume and assume active liquidity. Check time in range, actual fee share, token values, incentives and gas.
Troubleshooting LBAMM positions
Most liquidity is inactive
The active market may be trading in bins different from those holding the deposit. Review the distribution and whether repositioning is worth its cost.
The asset composition changed sharply
A directional move may have consumed consecutive bins. Compare the active-bin path and distribution with the original quantities.
A swap had price impact despite LBAMM
The trade may have exceeded liquidity in one bin and crossed several price levels, or the route may include another pool. Review route and execution details.
Frequently asked questions
Is CLAMM better than LBAMM?
No model is universally better. CLAMM offers familiar concentrated ranges; LBAMM offers discrete bins and distribution shapes. The better fit depends on pair behavior, management style, fees and pool liquidity.
Does LBAMM have zero slippage?
A swap can have zero price impact while fully contained within one sufficiently funded bin. Larger trades, state changes, fees and multi-bin routes can still produce a different result.
Can LBAMM LPs lose money?
Yes. Token prices can fall, inventory can be converted, bins can become inactive, hooks or contracts can fail and fees may not compensate for divergence from holding.
What happens when CLAMM price leaves the range?
The position becomes inactive, generally holds one token and stops earning normal swap fees until price returns or the LP repositions.
Can both pool types use hooks?
PancakeSwap Infinity is designed to support hooks with CLAMM and LBAMM pools. Inspect the specific hook rather than assuming every pool uses the same logic.
Can the router use both CLAMM and LBAMM?
Yes. The PancakeSwap routing system can consider multiple liquidity sources and pool versions when constructing an eligible swap route.
Which pool is more passive?
Neither is inherently passive. Wide CLAMM ranges or broad LBAMM distributions may require fewer adjustments, but they still carry inventory, fee and smart-contract risks.
Should stablecoin liquidity use LBAMM?
LBAMM can be efficient for low-volatility pairs, but CLAMM can also concentrate liquidity near parity. Depeg and issuer risks matter more than the label alone.
Decision matrix
| Preference | Likely starting model | Qualification |
|---|---|---|
| Continuous custom price range | CLAMM | Monitor boundary and inventory conversion |
| Discrete liquidity ladder | LBAMM | Understand bin crossing and shape |
| Very precise active management | Either | Compare actual gas and tools |
| Limit-order-like one-sided placement | LBAMM or one-sided CLAMM | Neither is identical to a centralized order |
| Simple passive yield | Neither automatically | All LP positions require risk monitoring |
| Lowest risk | Neither automatically | Token, pool, hook and range matter more |
Final verdict
CLAMM and LBAMM are two ways of defining where an LP is willing to exchange inventory. CLAMM uses continuous concentrated ranges; LBAMM uses discrete bins with fixed pricing inside each bin. Both can be capital-efficient, and both can convert the position into the asset that subsequently underperforms.
Select a real pool only after reviewing token contracts, active liquidity, fees, hooks and the cost of management. Measure performance against holding, not only against the starting LP value or displayed APR. For traders, let net output and verified route quality—not the pool label—drive the comparison.
Official sources
- PancakeSwap — Infinity and its CLAMM and LBAMM pool types
- PancakeSwap — Introducing Infinity
- PancakeSwap Docs — Infinity key features