fermi swap moves crypto between blockchains and can exchange it for another token along the way. In the fermi swap flow, choose the sending and receiving networks, review the quoted amount and time, then sign. Check the token you will receive before starting, and follow the transfer until it reaches your wallet.
It finds a route from your token on one network to a token on another. A bridge handles the move between networks. If you want a different token at the end, the route may include an exchange before or after that move.
Say you hold USDC on Base and want SOL on Solana. If that pair is available, you can request one route instead of arranging the bridge and exchange yourself. A fermi cross-chain swap still has several steps behind the screen: your USDC leaves, the transfer is confirmed, and SOL is delivered.
The route depends on which networks, tokens, and amounts are supported when you request it. Two tokens can share a name yet have different issuers or forms on the receiving network. Check the token’s unique identifier: its contract address on Base, or its mint address on Solana, as Solana’s token documentation calls it.
Start by selecting the network and token you hold, then the network and token you want. Enter the amount and your receiving wallet address. Confirm that the address belongs to a wallet you control on the receiving network.
Next, read the quote as an outcome, not just a rate. Check the amount you should receive, the minimum amount, the estimated arrival time, and every fee shown. The minimum matters because the exchange rate can move before the route finishes.
You may first need to approve a token. Approval lets the route’s contract spend the amount you allow from your wallet; it can require a separate transaction. You also need the sending network’s native coin to pay gas, the network charge for processing transactions. Leave enough behind for the approval and transfer.
Once you sign the transfer, save its transaction ID or route reference. The sending transaction must be confirmed before the receiving step can finish. A completed sending transaction alone does not mean the new token has reached your wallet, so keep following the route status.
The cost comes from network gas, the bridge route, and any token exchange. The exchange rate may worsen for a large trade if there is little liquidity, meaning few tokens are available at that price. An extra approval can add gas even when the route itself takes one transfer.
Here is an illustrative quote. You enter $1,000 in USDC and receive about $994 worth of SOL. Suppose $2 is a route fee and $4 reflects the exchange rate. If you pay $3 in sending gas separately, your total cost is about $9, or 0.9% of the input.
Compare the amount arriving in your wallet, including gas paid outside the quote. A route estimated at four minutes may deliver less than one estimated at twenty minutes. For an active user, the useful choice is often the fastest route that still meets your minimum amount and cost limit.
Times are estimates because networks must confirm transactions and the receiving side must complete its step. Gas also changes with network demand; Ethereum mainnet can cost much more than a low-fee network. Ethereum.org’s bridge documentation identifies cost, speed, and the number of transactions as practical trade-offs.
Check the receiving wallet on the correct network, then match the token’s identifier to the quote. A wallet may hide a token until you add it to the display. If the route shows completion but the balance looks empty, check the receiving transaction before starting another transfer.
If the sending transaction is confirmed and the route is still pending, use its reference to check which step is waiting. Do not repeat the transfer just because the estimated time has passed. If the route reports a failure, keep both transaction IDs and follow its stated refund or support process.
Keep the main safety check brief but firm: verify the receiving address, network, token identifier, and minimum amount before signing. If you swap crypto with fermi often, those four fields are quicker to check than recovering from a wrong destination. Before acting, ask yourself: Will this route deliver the exact token I need, at a total cost and wait I accept?