omnichain lets you swap a token in your wallet for a token on another blockchain through one cross-chain transaction. For an omnichain token swap, omnichain combines the exchange and transfer in one interface. Choose the input and output networks, check the quoted amount and receiving address, then sign from your wallet.
A cross-chain swap spends a token on a source chain and delivers a token on a destination chain. The tokens can have the same ticker, such as USDC on two networks, or be different assets. In this sense, omnichain describes a route between separate blockchains; it does not give your wallet one balance shared by every chain.
Think of a currency exchange that delivers what you bought to an address in another country. You specify what you are paying with and what should arrive, while the route handles the exchange and delivery. Unlike a trade on a centralised exchange, the starting tokens leave your own wallet and the result arrives at a wallet address you control.
The route begins with a transaction on the source chain. Depending on the token and route, that transaction may deposit tokens into a contract, lock them, or burn them. A destination-side action then releases or mints tokens, or pays the recipient from liquidity already available there. Tokens do not literally travel between ledgers.
The mechanism behind omnichain interoperability depends on the route. With an intent-based route such as Across, you specify the outcome and a relayer can supply the destination tokens from its own funds, then get reimbursed later. Other transfer systems use a verified cross-chain message to trigger delivery; Circle CCTP, for example, burns native USDC on one supported chain and mints it on another.
For a swap between different assets, the route also needs an exchange on the source or destination chain. That is why “bridge” and “cross-chain swap” are useful distinctions: a bridge moves value between chains, while a cross-chain swap also changes what you receive. The quoted output tells you the practical result, regardless of which steps the route uses.
The amount you receive depends on the exchange rate, available liquidity, route fees and any price movement before execution. Compare routes by their quoted destination amount for the same input, rather than by a fee percentage alone. In an illustrative same-token transfer, 1,000 USDC sent and 998 USDC received is a 2 USDC difference, or 0.2%; source-chain gas may be paid separately.
A swap quote may also show a minimum received amount. If the rate moves beyond the allowed slippage before the swap executes, the transaction may fail or return funds according to that route’s rules. Check the minimum, especially when swapping a thinly traded token: a low headline fee cannot make up for a poor exchange rate.
Timing depends on source-chain confirmation, the route’s finality requirements and whether a relayer has destination liquidity ready. A relayer may deliver before its own reimbursement settles; a message-based route may wait for more confirmations. Treat an estimated arrival time as an estimate, and use the destination transaction to verify delivery.
Start with the input token in a self-custody wallet on its current network and enough of that network’s native coin to pay gas. Choose the destination network, output token and receiving address, then read the quote as a complete trade: input amount, expected output, minimum output and any separately paid gas. omnichain.network is a service for swapping and moving tokens across blockchains from one interface.
If the input is an ERC-20 token, your wallet may first ask you to approve spending by the route’s contract. Approval permits a later transaction to use the token; it is not the swap itself. After the source transaction is signed and confirmed, keep its transaction hash until the destination transfer is visible.
Receiving an ordinary token transfer generally does not require you to hold the destination chain’s gas coin. Spending or swapping that token later does. If you plan to use the received funds immediately, account for that next transaction before choosing a destination asset.
Confirm the result by checking the recipient address, token contract and received amount on the destination chain. A matching ticker is not enough: native USDC and a bridged version of USDC can be different tokens on the same network. The check that most often prevents a costly mistake is confirming the exact destination network and token, particularly when sending to an exchange deposit address.
Keep this short checklist beside the quote: