Kyberswap Kyberswap zap checks before adding liquidity
Updated -
Kyberswap zap combines token conversion and liquidity entry, so a deposit needs checks on both the route and the resulting position. Before confirming, establish the supported pool and network, available input tokens, native gas balance, and any required price range. Review quoted output, slippage, Zap impact, and applicable fees before approving spending or signing the liquidity transaction.
KyberZap prepares the assets that a selected pool requires, while KyberEarn provides pool data and position management. Automatic ratio balancing reduces manual preparation. The pool still determines the exposure, fee opportunities, and conditions that govern the position.
A single-token deposit can become a multi-asset liquidity position, so the entry token does not define the exposure or exit assets.
Pool identity and network support
A usable Zap In route requires support for the selected pool on the network where the deposit assets sit. KyberEarn includes supported pools from Uniswap V3, Uniswap V4, PancakeSwap, Aerodrome, and other protocols. Each integration has its own scope. The same token pair appearing elsewhere does not establish that the same deposit action is available there. Match the protocol, pool, and network before comparing entry quotes.
Third-party protocols operate the pools. KyberEarn supplies discovery and management tools. The legacy Classic and Elastic liquidity products are deprecated, so their earlier pool instructions do not describe current third-party integrations. A current pool selection must support the intended liquidity action.
Single-token entry, mixed inputs, and direct deposits
KyberZap supports a single input token or a combination of up to five supported tokens for liquidity entry. The aggregator handles necessary conversions, and the Zap balances assets for the selected position. One token reduces the number of balances that you select; mixed inputs allow several existing holdings to contribute. Neither choice establishes a lower total cost without its quote. Direct entry through the underlying DEX remains an alternative, particularly when the wallet already holds the required pool assets. That route uses the protocol’s own deposit controls and requirements.
Trading activity and reward sources
A pool’s fee activity and incentive mix help determine whether its displayed annual percentage rate, or APR, matches the exposure under consideration. KyberEarn shows total value locked, or TVL, alongside trading volume, fees, rewards, and historical APR. High TVL with little trading can produce limited fee income. Low liquidity presents a different concern: a conversion that is large relative to available liquidity can move the price substantially.
LP Fees come from trading activity. Liquidity Mining Rewards and Bonus incentives may run for limited campaigns. Equilibrium Gain Sharing adds rewards in eligible pools that use FairFlow. Read the components separately before treating an aggregate APR as a reason to deposit. A campaign ending can reduce returns without ending the pool or its trading fees.
Range width and inactive liquidity
A concentrated liquidity position needs a price range that determines where its liquidity can earn trading fees. The selected range also affects the required token proportions. Automatic balancing handles that calculation; it does not decide whether the exposure suits the intended holding period. Compare the current pool price with the proposed boundaries before treating the position as ready.
A narrower range concentrates capital over fewer prices and can become inactive sooner when the market moves. A wider range can remain active over more price movement while spreading that capital more broadly. Once the market leaves the chosen range, the position stops earning new trading fees until price returns or you reposition into a range that includes the market price. That condition concerns trading fees; separate incentives follow their own eligibility rules.
Slippage and Zap impact
Slippage tolerance limits acceptable execution movement, while price impact concerns the effect of a trade relative to available liquidity. A Zap may involve swaps before the deposit, so both affect the entry. Zap enforces minimum swap output and minimum added liquidity, reverting if either result falls below its threshold. A low tolerance makes this more likely when conditions move. Raising tolerance permits greater variation and can accept a worse conversion.
Zap impact compares the estimated final USD value of added liquidity and returned tokens with the input’s USD value. Review it with the quoted output and fee breakdown. A route that successfully converts tokens can still produce an unattractive liquidity entry. A significant deviation in the pool price after zapping can expose the new position to immediate arbitrage. Review the estimated liquidity alongside the previewed change in the pool’s price.
Changing tolerance does not repair an incorrect pool, network, token selection, or price range.
Platform fees and the input amount
The Zap In platform fee applies to the input amount. The listed protocol fee categories are stable pairs at 0.01%, correlated pairs at 0.025%, common pairs at 0.1%, and exotic pairs at 0.25%. The selected pool’s classification matters, and the schedule can change. Read the applicable amount in the transaction preview. Network gas pays for blockchain execution and remains a separate cost. Any pool trading fees incurred during conversion also affect the economics of entry. A pool’s fee rate, the Zap platform charge, and network gas describe different charges.
Token allowances before deposit commitment
Token spending permission authorizes a particular spender to use a specified asset from a wallet on a particular network. An approval for another application or another network does not establish permission for this Zap route. Review the spender and allowance alongside the intended deposit amount. If an ERC-20 input lacks sufficient allowance, the flow may require a separate approval transaction before the main liquidity action.
Approval alone does not add liquidity. A successful approval can therefore appear in wallet history while the intended pool position remains absent.
A displayed quote allows a stop before granting new permission or submitting the deposit. An existing allowance has its own continuing scope, even when the user abandons that quote. Review each wallet request as an authorization with an amount and recipient contract. The gas estimate for an approval describes that transaction; it does not establish the cost or completion of the later Zap.
A Zap In readiness check with an early stop point
Single-token entry and mixed-token entry both require spendable inputs and native gas on the pool’s network. Consider a deposit whose wallet holds supported input tokens but lacks that gas balance. Neither input choice resolves the missing prerequisite. Stop before approval or deposit submission, then reconsider the entry when the wallet can cover execution costs.
- The wallet and selected pool show the same network; a mismatch means stop.
- Input balances cover the selected amounts while leaving enough native tokens for the required transactions.
- The preview identifies the intended pool assets, target range when required, and estimated liquidity.
- The quote shows conversion output, slippage, Zap impact, and the applicable fees for review.
- If the route needs a new approval or permit, its request matches the expected token, spender, allowance, and network.
After funding gas, repeat these checks against a refreshed quote. Choose single or multiple inputs based on the conversion and costs that you accept. Complete any required approval, review the main deposit again, and confirm it in the wallet. Reconcile the successful liquidity transaction with the resulting position in My Positions. A successful approval alone leaves this deposit unfinished.
Transaction status and the position record
Check that the liquidity transaction succeeded on-chain; a transaction identifier alone does not confirm the deposit. My Positions shows the resulting position, its status, accrued fees, rewards, and range activity where applicable. Match that record to the intended pool and network, and compare the deposit with its transaction details. Wallet balances can also reflect gas payments or returned tokens. An in-range status describes current eligibility to earn trading fees; it does not establish a particular amount of earnings.
Impermanent loss after a technically correct entry
A correctly executed Zap leaves the position exposed to the pool’s assets and smart contracts. Relative token-price movements can cause impermanent loss, meaning the liquidity position can underperform holding its underlying assets separately. The fees and rewards may or may not offset that difference. Token volatility also changes the position’s value independently of execution quality. A low-impact entry therefore answers a different question from whether providing liquidity will outperform holding. Pool selection and position management continue to matter after the initial conversion succeeds.
Withdrawal terms and the cost of changing course
Standard withdrawal and Zap Out produce different holdings on exit. Standard withdrawal returns the underlying pool assets in their current proportions. Zap Out adds conversion into a selected supported token. Review the intended exit asset before entering a position, particularly when retaining one token matters. An available withdrawal path does not reverse price changes, earlier conversion costs, or the economic effects of liquidity provision.
Repositioning can change the range of a supported position through withdrawal, fee collection, rebalancing, and redeposit in one transaction. It creates another liquidity action with its own quote, slippage exposure, and applicable costs. If the original range or assets no longer fit the intended exposure, compare that adjustment with withdrawal before committing further capital.
Kyberswap zap FAQ
Will a Zap deposit automatically compound its trading fees?
A Zap In deposit into a liquidity pool does not itself schedule ongoing fee compounding. KyberEarn offers a separate one-click compounding action for supported positions. That action reinvests accrued fees into the corresponding position in a transaction. An entry quote therefore does not establish an ongoing reinvestment schedule or a fixed compounded return.
Can every source pool also receive liquidity through Zap Migrate?
Support as a migration source does not establish support as a destination. In the Zap as a Service migration flow, Curve and Balancer pools can supply an outgoing migration but cannot serve as its destination. Destination support therefore needs a separate check before an existing position funds entry into another pool.
Are leftover tokens included in the liquidity position?
Leftover tokens that the Zap returns to the wallet remain outside the deposited liquidity position. A route preview can distinguish added liquidity from amounts that return to the user. Its combined final value may include both. Comparing that total directly with the position value alone can therefore suggest a shortfall that the returned balances explain.
Does Zap charge identical fees inside another application?
An application integrating Zap can configure an additional partner fee on top of the protocol fee. That charge depends on the integration’s configuration and is not universal. For Zap In, partner fees use the input token. The specific transaction’s fee breakdown matters when comparing an embedded flow with a direct liquidity entry.
When can a permit replace a separate token approval for Zap In?
A permit-enabled Zap flow can replace a separate approval transaction when its ERC-20 input supports ERC-2612 and the integration uses KSZapRouterPositionPermit. The wallet signs spending permission off-chain, and the router applies it during the Zap transaction. This does not make the deposit itself gasless or establish permit support for every token.
Which assets would Smart Exit return from a position entered through Zap?
Smart Exit returns the underlying pool assets in their current ratio when a supported withdrawal executes. It does not automatically consolidate them into the single token that a Zap Out can provide. Entering with one token therefore does not determine the assets that a later Smart Exit returns; the exit method governs that outcome.
How does adding liquidity affect an existing position’s range?
Increasing liquidity adds assets to the existing position using the token proportions that its current range requires. It does not by itself select a new range. Repositioning is the separate action that changes the range. Check which action the interface presents before treating an additional deposit as a way to reactivate an out-of-range position.