acrossbridge explained: moving crypto between blockchains
If you need crypto on a different blockchain, acrossbridge lets you bridge or swap it in one flow. acrossbridge moves your asset between chains and can change it into the asset you need there. You receive crypto on the destination network, ready to use with a compatible wallet or app.
How does the transfer work?
A cross-chain bridge moves value between blockchains that cannot directly share balances. You send an asset on the source chain. The bridge checks that transaction, then arranges a payout on the destination chain. No coin physically travels between the two networks.
The bridge may hold the original asset and issue a matching token elsewhere. It may instead pay you from liquidity, meaning tokens already available on the destination chain. If you also want a different asset, a swap trades at an exchange rate before or after the move.
That difference matters when you check the result. A token issued against an asset held elsewhere is called a wrapped token; its value depends on that backing. A payout from available liquidity depends on how much the route has and the price offered for your amount.
What will arrive on the other chain?
A cross-chain bridge and swap should leave you with the asset and network you selected, if that route is available. A familiar asset name alone is not enough. Check the destination network and the token contract, which is the token’s unique identifier on that network.
Say you hold native Bitcoin but need ETH for an Ethereum app. Bitcoin itself cannot arrive on Ethereum. A route could deliver a wrapped token representing BTC, or swap your BTC into ETH. I would choose ETH if the next action needs gas, the network fee paid in ETH.
Layer 2 networks, or L2s, handle transactions away from Ethereum’s main chain. ETH on an L2 is a separate balance from ETH on Ethereum mainnet, even when your wallet shows the same symbol. Before sending, use the network and asset named by the app that will receive the funds.
What will it cost, and how long will it take?
The useful cost figure is what reaches your destination wallet. For acrossbridge, compare the input with the quoted output in the same currency, and check which parts of the quote may change. For example, $50 sent and $47 received is a $3 difference, or 6%.
That difference can contain several costs. Look for these when judging a route:
- Source network fee: the cost of recording your send, which rises when that chain is busy.
- Bridge or routing fee: payment for arranging the transfer between chains.
- Swap spread: the difference between the market price and the rate offered for your trade.
- Slippage: a change between the quoted rate and the final rate while the swap executes.
- Destination network fee: a payout cost that may reduce the amount you receive.
Time depends on source-chain confirmation and when the destination payout is ready. Bitcoin produces a block about every 10 minutes on average, and a route may wait for several confirmations. Available destination liquidity can shorten some transfers; a native withdrawal from certain L2s can take days.
Neither the average block time nor an estimated arrival time is a deadline. A low source fee, a busy network, or thin liquidity can extend the wait. Check the quoted output and expected timing again just before you send.
How do you make the move?
Start with the receiving app’s required asset and network, then work backward to what you hold. That keeps you from receiving the right asset name on the wrong chain. Keep enough of the source chain’s native coin to pay its transaction fee.
- Confirm the destination network and exact asset with the app or wallet where you will use them.
- Enter a receiving address for that network; addresses from other networks may be unusable.
- Compare routes by the amount you will receive, expected time, and whether the output is native or wrapped.
- Review the wallet request before signing. If it asks for token approval, that grants spending permission to a contract.
- After sending, keep the source transaction record and check for the destination payout before trying again.
For a large transfer, a small test can confirm the address and delivered asset, though it adds fees. I would use a route only when its destination asset, network, received amount, and expected wait fit what I need to do next.