Pancakeswap

Pancakeswap lets you trade tokens or earn from liquidity positions and eligible farms

Pancakeswap connects a wallet to decentralized token swaps, liquidity pools and farm incentives. Use a swap to exchange one asset for another. Providing liquidity creates an ongoing position whose outcome depends on trading activity, pool rules, market prices, network costs and any additional reward conditions.

Should you swap or provide liquidity?

Use a swap when the intended result is a different token in your wallet. Provide liquidity when you want a position that can collect trading fees and perhaps farm rewards. The second path exposes you to both pool assets and requires ongoing management, so it serves a different purpose from a direct exchange.

Swapping changes the asset you hold

A swap begins with an input token, an output token and an amount. The router searches available liquidity and produces a quote that includes the proposed route and expected output. Depending on the deployment, that route may draw from V2, V3, Infinity or StableSwap pools. The quote remains provisional until the transaction executes because pool balances and market prices can change between signing and confirmation.

Liquidity creates an ongoing position

Providing liquidity deposits assets into a pool and returns a record of the position. That record may be an NFT or an LP token, depending on the pool version. Trades against the active liquidity can generate fee income. A qualifying farm may add token incentives, but neither source fixes the final return. Asset prices, trading volume, the position’s share of active liquidity and any applicable range continue to affect the outcome.

Pool depth sets the practical boundary

Deeper pool liquidity near the requested price generally reduces how far a given order moves the execution price. With split routing enabled, a swap route can divide one order across multiple liquidity sources when that improves quoted output. Each hop may add a pool fee, while the network charges gas for execution. Restricting liquidity sources or multihop routing can worsen the quote or prevent execution. Review the displayed route rather than assuming one pool handles every trade.

How does a swap reach completion?

A swap is complete only after the network confirms the transaction and the expected output balance becomes observable. A connected wallet and a displayed quote are starting states, not evidence of settlement.

Quote and route

Start by checking the selected network, token identifiers and amounts. The quote should show the estimated output and the route’s fee information. Price impact describes how the order itself changes the pool price, while minimum received sets the execution boundary after permitted quote movement. Those values need a fresh review whenever the amount, route or market state changes.

Approval and signature

On an EVM deployment, an ERC-20 token may require a separate spending approval before the swap. Approval authorizes a specified smart contract and does not execute the trade by itself. The wallet must also hold enough of the network’s native gas asset for any on-chain approval and the swap transaction. Read the contract target, allowance and transaction details before authorizing either request.

Confirmation and balance

After the swap signature, the transaction moves from pending to success or failure. A success record should identify the executed transfers, and the output token should appear at the receiving address. A failed record means the intended exchange did not settle. Stop there and inspect the transaction state, balance, allowance and route settings before attempting another transaction. Repeated submissions can create additional gas costs without resolving the missing prerequisite.

Fees and incentives reward different work

Liquidity providers may receive pool trading fees, while farms add a separate incentive layer to qualifying positions. Each stream follows its own eligibility and accounting rules.

Trading fees follow active liquidity

A concentrated liquidity position earns trading fees only while the market price remains inside its selected range. A narrower range can give the position a larger share of active liquidity, yet it can also move out of range sooner. In V3, accrued fees require a claim rather than automatic compounding. V2 pool fees instead increase the reserves represented by LP tokens. Volume and competing liquidity make fee income variable.

Farm incentives add eligibility rules

Farm rewards apply only where a pool has an active incentive program. Some farm implementations require the LP position to be staked. Eligible Infinity farms can accrue rewards to an active, in-range position without separate LP staking. The position view should show whether it qualifies and what has accrued. Emissions, participation and token prices can change the displayed APR, while claiming rewards may require another transaction and network gas.

What changes after you provide liquidity?

The token composition, active status and claimable amounts of a liquidity position can all change after deposit. Ownership of the position does not preserve the original token ratio.

When the relative price moves, an automated market maker shifts the quantities of the two assets held by the position.

Concentrated liquidity adds a range boundary. A position within range can serve trades and collect applicable fees. If the price leaves that range, the position becomes inactive and stops earning those fees. Its holdings may then consist mainly or entirely of one asset. Fee earning can resume if the price returns within range.

Impermanent loss compares the position’s value with the value of simply holding the original assets. Trading fees and farm rewards may offset some of that difference, but they do not erase it by definition. Removing liquidity returns the position’s current token amounts, so compare them with the starting assets rather than looking only at accumulated rewards.

Before removing or adjusting a position, review its current range status, underlying token amounts, unclaimed fees and farm state. An adjustment can trigger fee collection or reward handling in some implementations. The wallet confirmation shows the immediate transaction, while the updated position record and returned balances show whether the change finished.

A decision checklist before any transaction

Match the transaction to your intended result, then check these conditions before requesting a wallet signature:

Open full-size image

• Confirm the selected network, token identifiers and available wallet balances.
• For a swap, compare expected output, route fees, price impact and minimum received.
• For liquidity, identify the pool version, how fees accrue, the selected range when applicable and any farm eligibility or staking rule.
• Keep enough native gas asset for approval, execution and a later claim or exit.
• Define the finish state: a confirmed output balance or a visible, owned liquidity position.

If a required balance, approval or supported route is missing, surface that gap before signing. A quote that cannot meet its execution boundary is not a completed trade. Likewise, a deposited position that remains inactive should not be counted as fee-earning liquidity.

Your next choice follows the visible state

A confirmed swap leaves a new token balance to hold, use or exchange. A confirmed liquidity deposit leaves a position whose range, fees and incentive eligibility need monitoring. If the expected transaction record or balance is absent, reconcile that state before starting another action. Once the evidence matches the intended result, decide whether the next task is holding the output or managing the position.

Open full-size image

Useful questions about Pancakeswap