On Syncswap, liquidity ownership moves with the position token, not with the assets sitting in the pool.
Syncswap is a decentralized exchange and liquidity hub built on Ethereum zero-knowledge rollups, primarily serving ZKsync Era. Ethereum Mainnet provides the settlement security behind the system, while Zero Knowledge Proofs let the rollup process activity at lower cost.
The mistake on a first attempt is treating “moving liquidity” as one action. It is two. You can move the claim on a position, or you can withdraw the underlying tokens and create a new position. Those actions produce different results.
What actually owns a SyncSwap position?
In a Classic or Stable pool, the pool contract mints an ERC-20 LP token to the address supplied during deposit. That balance represents a pro-rata claim on the pool reserves.
The pool still holds the ETH, USDC, or other assets. Your wallet holds the claim. The claim grows in value as fees accumulate and the reserve balances change. It is not a receipt for the exact tokens you deposited.
Range Pools use a different model. A position has its own price range and is represented by a non-fungible position token. That token carries the position identity. Sending a generic LP token will not move it. Aqua deployments can also differ from the older Classic and Stable pattern, so check the pool’s actual position contract before signing a transfer.
That distinction is the part most short guides miss. The wallet address is not the important object. The important object is whatever token the pool uses to authorize withdrawal.
For the current pool interface and position entry points, use Syncswap.
Way one: transfer the position token
Use a direct transfer when the goal is to give another wallet the same pool exposure. The pool does not rebalance. No tokens leave the pool. No new liquidity is minted.
- Identify the exact pool and the token contract representing its position.
- Check that the position is in your wallet and is not deposited in a farm, gauge, or staking contract.
- Transfer the full or partial ERC-20 LP balance, or transfer the Range Pool NFT.
- Let the receiving wallet approve the router or position manager before removing liquidity.
For a fungible LP token, a partial transfer splits the claim. If you send 40 percent of your LP balance, the recipient receives 40 percent of that wallet’s claim at the time of transfer. The pool’s total liquidity is unchanged. The recipient later receives the corresponding share of reserves when those LP tokens are burned.
A Range Pool position is indivisible in the same way an ERC-20 balance is not. Its price band, fee configuration, and accrued position state travel with the NFT. The receiving wallet owns that specific range position after the transfer.
This is the clean method for changing custody, moving a position to a treasury wallet, or handing control to a strategy contract. It preserves the position’s existing exposure. It also avoids turning the transfer into a taxable or economically meaningful withdrawal and redeposit event, subject to local rules.
Way two: withdraw, then deposit again
The second method is to burn the old position and mint a new one for the recipient. This moves the underlying assets, not the original position.
When an LP token is redeemed, the pool calculates the holder’s share from current reserves and total supply. The wallet receives the two pool assets in their current proportions. The result may be very different from the original deposit because swaps have changed the reserve ratio and the asset prices.
A single-sided withdrawal adds another step. The pool or router converts one side into the requested output asset, applying the relevant swap logic and fee. That is a withdrawal plus a trade, not a simple transfer.
The new wallet then deposits those assets into a pool. It receives newly minted LP tokens, or a new Range Pool NFT with a newly selected price band. The new position begins with the market conditions and fee accounting that exist at that moment.
This route is necessary when you are changing pools, changing networks, changing a Range Pool price band, or converting the position into spendable tokens. It is also the route to use when the original position is held by a contract that cannot transfer its position token directly.
Where the line falls
Use this rule: if you want to change who controls the same claim, transfer the claim. If you want the assets themselves, or want a different pool position, withdraw and redeposit.
Curve Finance makes the same distinction visible through gauges. A user may hold a pool LP token directly, or deposit it into a gauge and hold a separate accounting position. Moving the wallet balance does not automatically move the gauge deposit. SyncSwap farming creates the same practical question: find where the position token is held before assuming a wallet transfer is enough.
The cost difference matters. A direct transfer does not alter pool reserves. Withdrawal and redeposit create liquidity events, can realize impermanent loss, may require several approvals, and can expose the transaction to price movement. On a Range Pool, redepositing also discards the original price band unless you deliberately recreate it.
So the useful answer is simple. Transfer the LP token or position NFT when ownership is the thing changing. Exit and re-enter when the liquidity, pool, or strategy is changing.
FAQ
Does transferring an LP token move the assets in the pool?
No. It moves the redemption right. The assets remain in the pool until the new holder burns the position.
What if the LP token is staked?
Withdraw it from the farm or gauge first, unless that contract provides its own transfer mechanism. The wallet may show no LP balance while the staking contract holds the token.
Can I transfer a Range Pool position like a Classic LP token?
No. A Range Pool position is non-fungible. Transfer its position NFT, and verify whether any farm or manager currently has custody of it.