Syncswap pool share tokens represent a redeemable, pro-rata claim on the reserves and fee-bearing liquidity of one specific pool, not a slice of the SyncSwap protocol or its governance token; in the newer Range Pool design, that claim is position-specific rather than the interchangeable ERC-20 share familiar from Classic pools.

The confusion starts when a wallet shows an LP balance without explaining what that balance can actually buy back. Syncswap is a decentralized exchange where that balance is created when a user supplies liquidity to a pool.

The share is a changing claim, not a fixed deposit receipt

In practical terms, a Syncswap pool share token is a claim on a percentage of a pool’s current assets. It does not promise to return the same number of USDC and ETH that were deposited. The pool’s reserves change whenever traders swap, and the share changes with them.

Consider a Classic USDC/ETH pool. If an account owns 10% of the pool’s outstanding liquidity tokens, it is entitled to roughly 10% of the pool’s withdrawable USDC and ETH at that moment. If the pool contains 800,000 USDC and 400 ETH, the claim is approximately 80,000 USDC and 40 ETH before rounding and withdrawal details. If trading later leaves the pool with 700,000 USDC and 450 ETH, the same token balance represents the new mix.

That is why an LP token should not be judged like a normal standalone asset. Its useful quantity is the underlying claim per token, not merely its wallet balance or an assumed dollar price. Trading fees remain in the pool in the ordinary liquidity model, increasing the assets available to all outstanding shares, while price movement changes the composition of those assets.

How Syncswap creates and redeems the share

A Classic pool follows the familiar constant-product design, with the invariant x*y=k. The user sends the two pool assets through the router and vault flow. The pool observes the new balances, calculates the increase in liquidity, and mints pool tokens to the chosen recipient.

The first deposit is special: the Classic contract permanently locks a minimum amount of liquidity. Later deposits receive liquidity in proportion to the pool’s invariant growth, after the contract accounts for the existing reserves and any applicable mint or protocol-fee logic.

Withdrawal reverses the process. The user sends LP tokens to the pool, and the pool burns them. The contract calculates each output as the user’s liquidity divided by total supply, multiplied by the current balance of that asset. A single-asset withdrawal is different: the pool burns the share and swaps the other output internally, so the user receives one token rather than the proportional pair.

This mechanism also explains the practical edge that many descriptions miss: the token does not represent ownership of the pool contract, control over its parameters, or ownership of SyncSwap itself. It is an accounting unit for redeemable liquidity. Governance, protocol rewards, and pool shares are separate things.

What changed with Range Pools

SyncSwap V3 added Range Pools, and that changed the meaning of “pool share” for builders who had learned the older model. A Classic share is fungible because every unit has the same full-range exposure. A Range position includes a selected lower price boundary, upper price boundary, and liquidity amount, so two positions in the same pair may have materially different behavior.

Range liquidity is active only while the market price sits inside its chosen band. As the price moves, the position can become concentrated in one asset; once the price leaves the range, it no longer supplies liquidity to trades across the current price and stops earning the corresponding swap fees until it becomes active again.

The contract surface reflects that difference. Range Pools expose ticks, position state, fee-growth accounting, and a position-management or NFT layer rather than treating all providers as holders of one interchangeable ERC-20 balance. The old assumption—read total supply, calculate a universal percentage, and burn fungible LP tokens—therefore does not transfer cleanly to a Range Pool.

Which pool model fits the share you need?

The pool model decides both the pricing curve and the meaning of the liquidity position.