Ape swap
Ape swap supported networks and token swap limits
Ape swap began as a decentralized exchange; its successor, ApeBond, offers token swaps through a multichain aggregator. A swap requires a supported combination of networks, tokens, and amount, plus the permissions and transaction fees needed for execution. Network support alone does not establish that a particular pair has an available route or sufficient liquidity.
A quote describes an available exchange path at the time of the request. Completion requires a separate check of the resulting tokens and their network, especially when the path includes a bridge between blockchains.
A supported network does not guarantee a usable swap: the selected tokens, amount, liquidity, and spending permission must also fit the route.
A usable quote with missing spending permission
Consider a wallet holding the intended input token on the selected starting network. The swap returns a quote for the requested output. Before execution, the spending contract needs sufficient permission to use that input token when the route requires an allowance. An allowance is the amount that a token holder authorizes a particular contract to spend.
Use these conditions to decide whether this quoted swap can proceed:
- The selected account holds enough input tokens on the starting network for the quoted amount.
- The quote identifies the intended output token and receiving network.
- The minimum output and route costs fit the intended exchange.
- The selected spender has sufficient allowance when required, and the wallet has enough gas for approval and execution.
- No earlier submission of this same exchange remains unresolved.
When those conditions hold, the wallet can authorize the exchange transaction. After execution, compare the transaction result with the receiving balance before using the output elsewhere. A successful approval alone does not complete the swap.
If allowance is missing, stop before submitting the exchange. Check the quoted spender and approval amount before signing, wait for the approval to confirm, and refresh the quote. Proceed only if the refreshed terms remain acceptable and the allowance covers the refreshed quote’s spender and input amount. This recovery addresses the missing permission; it does not repair an unavailable route.
Network selection and token identity
Compatibility involves both sides of the exchange. The starting network must contain the spendable input, and the receiving network must support the intended output through an available route.
The network on each side
ApeBond’s published swap network coverage includes BNB Chain, Polygon, Ethereum, Arbitrum, Avalanche, Optimism, and Gnosis. Treat this as network coverage, not a promise that every combination remains available. The selected swap must return its own quote. A network offered for another platform product does not automatically establish swap support.
The token on each network
Check the selected network and, for a non-native token, its contract address. Matching symbols can identify different contracts, and a balance on one blockchain cannot fund a transaction on another merely because the wallet displays the same account address. The receiving token also matters: a bridged representation can differ from the token that another application accepts.
What determines the minimum and maximum swap amount?
The selected route determines usable amount limits through its liquidity, provider restrictions, and costs. A platform-wide number would conceal these differences.
The routing system can reject an amount because it falls below a provider’s minimum, exceeds available capacity, or leaves too little after fees. Insufficient liquidity presents another constraint: a token may be recognizable without a route that can exchange the requested amount. These conditions can change independently of the wallet balance.
A missing quote also needs interpretation. An unsupported pair differs from a temporary timeout or a failure to retrieve blockchain data. Repeating an unchanged request cannot resolve a genuinely unsupported connection. Likewise, raising the amount does not cure every minimum-related failure, and reducing it does not guarantee liquidity. Use the returned reason to identify the actual constraint.
Spending permission before token movement
For a conventional ERC-20 transaction route, the relevant allowance belongs to a specific owner, token, and spending contract on the starting network. ERC-20 is a standard for fungible tokens. Existing permission for another contract does not authorize the selected route, and a previous trade may have consumed an earlier allowance.
A token approval grants spending permission to a contract without performing the swap itself. The approval request and exchange request therefore require separate attention. Inspect the spending contract and authorized amount before signing. Native network assets follow a different path and do not require an ERC-20 allowance for their transfer.
The quoted route determines the appropriate spender. Reusing a remembered contract address can authorize the wrong contract or leave the intended transaction without permission. Where the wallet offers an allowance amount, a limited approval restricts the remaining spending permission compared with an unlimited approval.
Estimated output, minimum output, and price impact
The estimated output describes the quoted exchange result, while the minimum output expresses the lower bound accepted under the route’s slippage settings. Slippage covers movement between the quoted terms and execution. A higher tolerance accepts a wider difference; it does not improve the exchange rate.
Price impact concerns how the trade interacts with available liquidity. A larger request can receive a worse effective rate when the route cannot absorb it at similar prices. The quote may already reflect that difference before any later market movement occurs. This explains why an unattractive estimate cannot necessarily be repaired by changing slippage.
Apply minimum-output protection to the step that enforces it. A cross-chain route may finish its bridge transfer even when the final conversion cannot meet its conditions. Treating every multichain operation as one reversible transaction would hide that possibility.
Gas balances and route charges
ApeBond’s swap routing can involve a routing charge, exchange charges, and a bridge charge when the path crosses networks. Their combination depends on the selected route. Network gas pays for blockchain execution and requires separate attention to the wallet’s available fee balance.
A wallet can hold enough input tokens while lacking the native asset needed to authorize or execute a transaction. Approval transactions can require gas before the exchange starts. When the input itself is the native asset, spending the entire balance can leave too little for execution.
Receiving tokens on another network also does not establish that the wallet can transact there afterward. Some routing arrangements can provide destination gas, but that capability must belong to the selected route. Future transfers or contract interactions may still require a native-asset balance on the receiving network.
Same-chain swaps and bridge routes have different dependencies
A same-chain swap keeps its input and output on one blockchain. A cross-chain route adds a transfer between networks and can include a conversion before or after that transfer. ApeBond supports both forms through its aggregation service.
The distinction changes the cost drivers and completion checks. A same-chain exchange relies on liquidity and transaction execution within its network. A bridge route also relies on the chosen transfer mechanism and destination processing. Its source transaction can succeed while later work remains pending. Compare the route’s output, costs, and required operations rather than treating every displayed exchange as an identical transaction.
How can a completed bridge leave the wrong output token?
A bridge can deliver an intermediate token when the destination conversion cannot execute within its liquidity or slippage conditions. That outcome differs from receiving the requested final asset.
Source confirmation and destination processing
A successful source transaction establishes only the result of that transaction. A cross-chain transfer can still await source confirmations or destination execution. The route status connects those separate records. A delay or unavailable status service does not, by itself, establish failure or justify submitting the original exchange again.
A partial result and the received balance
The received token may therefore require a separate conversion before it suits the intended use. That conversion has its own available liquidity, permissions, and execution costs.
Compare the actual token contract, network, recipient, and amount with the original request. A general completion label can cover a different result from the one expected. A refund also differs from a completed exchange: it returns funds under the route’s refund process rather than delivering the requested output. The transaction records and resulting balances distinguish these outcomes.
Liquidity provision and bonds serve different purposes
The earlier exchange centered on liquidity pools, which hold assets available for trading. Adding liquidity creates a pool position instead of simply exchanging an input token for a spendable output token. A swap quote therefore does not describe the conditions or value of a liquidity position.
ApeBond’s broader product focus includes bonds. Liquidity bonds accept eligible liquidity-provider tokens in exchange for tokens that vest over time. The bond’s terms determine when those tokens become claimable. This differs from a swap’s intended immediate exchange result, and bond availability on a network does not establish that every associated token pair has a usable swap route.
Records and permissions after the exchange
Keep the source transaction identifier and any destination transaction identifier with the requested and received token details. These records preserve the distinction between a successful swap, an intermediate-token result, and a refund. They also help separate blockchain execution from a wallet display that has not refreshed.
Unused spending permission can remain after trading. Disconnecting a wallet ends the interface connection; it does not revoke an existing token allowance. Reducing or revoking that allowance requires a separate blockchain action. Review the specific token and spender rather than assuming that the exchange consumed all permission.
The earlier exchange name and the ApeBond service
Ape swap’s transition to ApeBond changed the product emphasis toward bonds while retaining a swap offering. Older pool instructions, reward descriptions, and token-migration announcements describe their own periods and products. They do not establish today’s route availability or reopen a historical migration window.
The rebrand announcement dates to October 10, 2023. For an exchange now, the operative details are the selected route and the tokens it actually delivers. A historical network listing cannot substitute for that route’s quote, and a previous approval authorizes it only if the current allowance still covers the selected token, spender, and amount.
Common questions, answered
Can closing the browser cancel a submitted swap?
Closing the browser does not cancel a transaction that the wallet has already broadcast. The blockchain can continue processing it without the interface remaining open. Reopening the application may restore progress information, but the transaction record determines its execution state. Check that record before submitting another exchange.
Does a failed transaction still cost gas?
An on-chain transaction that executes and reverts can still consume gas. Its failure does not mean that the network performed no work. A quote request that returns no route is different because it does not itself submit a blockchain transaction. Separately confirmed approval transactions also retain their own gas costs.
Which balance matters when several wallet accounts are connected?
The account authorizing the transaction must hold the required input and gas on the starting network. Balances in another account do not combine with it automatically. Token allowances also belong to the account that granted them, so switching accounts can change both the available balance and the permission state.
Is a token with a transfer tax automatically compatible?
A token with a transfer tax is not automatically compatible with a quoted route. Transfer deductions can cause the receiving contract to obtain less than the amount expected during execution. Compatibility depends on the token’s behavior and the contracts handling the route. Increasing slippage does not establish that those contracts support the token.
How long does a cross-chain swap take?
Completion time depends on the selected bridge, source confirmations, and destination processing. A displayed duration is an estimate for that route, not a deadline shared by every swap. Pending destination execution, unavailable network data, and an active refund process describe different states and can require different amounts of time.
What information helps investigate an unresolved swap?
The transaction identifier, starting and receiving networks, token contracts, and displayed route status help identify an unresolved swap. Include any separate approval or destination transaction records so the operations remain distinguishable. Public transaction identifiers can expose account activity, but troubleshooting never requires a wallet’s recovery phrase or private key.