fermi swap routes token transfers between two blockchains and can exchange the token during that route when the pair is supported. You pay source gas plus any quoted bridge and trading costs. If an attempt stalls, check the source transaction, bridge status and destination receipt in that order.
Key points
- A confirmed token approval is not a completed transfer; look for the source deposit transaction.
- Compare the destination amount you will receive, including fees and price impact.
- Once the source deposit confirms, trace that route before submitting another swap.
How a cross-chain swap reaches the destination
A cross-chain swap connects a source-chain transaction to delivery on another chain, with a token trade before or after the bridge leg if needed. The route quote should identify the input token, destination chain, output token, recipient, estimated output and minimum output. Supported pairs and transfer limits depend on available liquidity and the bridge route at the time you request the quote.
For a fermi cross-chain swap, compare the live destination amount with fermiswap.pro when both show a route for the same tokens, chains and amount. Check the minimum received and estimated completion time alongside the headline fee. A route with a lower bridge fee can still deliver less if its token trade has greater price impact.
After you submit, the source transaction may swap the input into a bridgeable asset and deposit it. Depending on the route, a relayer can deliver liquidity on the destination chain before it is reimbursed, or a bridge can wait for a cross-chain message and release or mint the asset. Across is an example of the relayer model; the receipt for your chosen route determines which stage to track.
Use fermi swap to transfer tokens by checking the route first
To transfer tokens, select the source token and chain, then the destination token and chain, enter the amount and verify the receiving address. Read the route and minimum received before signing. If the token needs an allowance, its approval is a separate source-chain transaction; submit the actual swap transaction after that approval confirms.
- Check that the quote covers the exact token contracts and networks you intend to use.
- Confirm the recipient, estimated output, minimum output, fees, slippage tolerance and quote expiry.
- Sign the required approval, if any, then sign the source swap or deposit.
- Save the route or order ID and source transaction hash; track delivery on the destination explorer.
Consider two illustrative cases side by side. Case A: 1,000 USDC on Arbitrum becomes USDC on Base, so a quoted route may only need bridge delivery. Case B: 1,000 USDC on Arbitrum becomes SOL on Solana, so a quoted route also needs a token conversion. Case B has an exchange rate and slippage limit to assess, as well as a Solana recipient address; neither route should be assumed available until it returns a quote.
A fermi swap costs gas, route fees and sometimes price impact
The total cost is the difference between what you spend and the value you receive, plus any gas paid separately from your wallet. A quote can include source gas, a bridge or relayer fee, destination execution costs, and fees for source or destination trades. Some interfaces fold several components into the displayed rate, so compare net output for the same input amount.
For scale, an illustrative 0.3% route fee takes 3 USDC from a 1,000 USDC transfer before any gas or trading loss. Actual fees change with chain gas prices, liquidity, route size and the provider filling it; use the current quote for this route. Slippage tolerance is a separate limit on adverse execution, commonly set around 0.5% to 1% for liquid trades, and is not a fee charged automatically.
When you swap crypto with fermi, a small transfer can be dominated by fixed gas while a large transfer can suffer more price impact or exceed a route limit. If the quote says the amount is below a minimum or above a maximum, changing the amount or intermediate asset may produce a valid route. Requote after any change: an expired quote does not preserve its output amount.
A pending transfer needs a stage-by-stage check
A pending label tells you little until you locate the last confirmed event. First inspect the source hash: a successful approval alone means the bridge has received nothing. If the deposit succeeded, use the route tracker or order ID to look for a destination fill, release or refund status, then inspect the destination token contract and recipient on its explorer.
A common edge case is successful bridge delivery followed by a failed destination trade. The wallet may then hold the intermediate asset rather than the requested output token; its balance and the destination transaction explain what arrived. If the source transaction reverted, gas may have been spent but the tokens usually remain in the source wallet. If the deposit confirmed and no destination event appears, the route operator needs the source hash and order ID to investigate or identify its refund process.
Allow for the completion estimate to slip when confirmations, relayer liquidity or destination gas are delayed; cross-chain routes can take minutes and sometimes longer. Keep recovery details to the transaction hashes and order ID. A request for a seed phrase or private key is never part of resolving a bridge transfer.
The practical check is simple: establish what confirmed on the source chain, what the route promises to deliver, and whether a destination transaction or refund exists. Those records tell you whether to wait, use an intermediate token already received, or contact the route operator with a precise failure stage.