Biswap V2 vs V3 liquidity pools explained
If you are building on Biswap, V2 pools spread liquidity across the full price curve and issue fungible LP tokens; V3 pools concentrate it inside a chosen price range and issue position NFTs. V2 suits simple share accounting and unattended liquidity. V3 suits integrations that can monitor ranges and want more depth near the trading price.
The deciding constraint is how your app represents and maintains a position. For a BNB Smart Chain vault that expects interchangeable LP shares, choose Biswap V2; for a market-making service that can track individual NFTs and reset ranges, choose Biswap V3. In either case, compare actual trading volume and operating costs before treating a displayed APR as expected income.
When does Biswap V2 fit?
V2 fits an integration that needs a full-range automated market maker (AMM) pool and a fungible claim on its reserves. Its constant-product curve, commonly written x × y = k, adjusts the price as traders change the two token balances. Supply both assets at the pool’s current ratio and you receive LP tokens representing your share; when you withdraw, you receive that share of the reserves’ then-current mix.
That model works well for a vault that holds or stakes LP tokens and does not run a price-range keeper. It does not mean the asset mix stays fixed: sustained buying of one token leaves the pool holding more of the other. The first deposit to a new pool also sets its starting price, so an incorrect deposit ratio can be traded against immediately.
The documented V2 swap fee is typically around 0.1%–0.2%, depending on the pair, with roughly three-quarters going to liquidity providers. V2 Farms require a separate LP-token staking step, adding transactions and reward accounting. BNB Chain documentation is the reference for estimating gas for approvals, deposits, staking and withdrawals on this chain. V2 fits poorly when your app needs concentrated depth or liquidity on Arbitrum.
When does V3 fit?
V3 fits an integration that can select a fee tier and price range for each position, then respond when that range stops covering the market price. Consider two services holding USDC and USDT: a passive vault may value V2’s interchangeable shares, while a market maker with a keeper might place V3 liquidity, say, between $0.99 and $1.01. That illustrative band needs a plan for a depeg, not just a timer for routine resets.
On deposit, V3 records the pair, tier and range in a position represented by an NFT token ID. Swaps pay fees to liquidity active at the traded price; beyond either boundary, the position ends up in one asset and stops earning swap fees until price returns or the manager repositions it. Repositioning means withdrawing and adding liquidity again, with network costs, while accrued trading fees require collection. Ethereum Improvement Proposal 721 explains NFT ownership and token IDs, but an indexer also needs the position’s range, balances and uncollected fees.
The published V3 swap tiers typically run from 0.015% to 1%. Each tier is a separate pool for the same pair, so its active depth matters as much as its stated fee:
- 0.015%: closely priced stablecoin pairs.
- 0.08%: a stable asset paired with a more volatile one.
- 0.28%: pairs of volatile assets.
- 1%: less common pairs where liquidity providers seek more fee per swap.
V3 is a poor fit for a vault that assumes every LP share is interchangeable or cannot detect inactive positions. On BNB Smart Chain, Farm rewards may apply automatically to selected V3 fee tiers; do not assume every tier or chain qualifies. Before deploying, quote the same swap size against each live pool for your pair and chain, then compare execution and expected fee income with the gas cost of one range reset.