When you want to move crypto from a wallet you control, use Rhino Bridge after confirming the exact source-to-destination route and the amount you will receive. Unlike a centralised exchange withdrawal, a bridge transfer is signed from your wallet, and the source and destination networks process separate transactions.

How to prepare your wallet and route

Start by checking that the bridge supports your specific asset on both networks and that you can use the destination wallet there. A token ticker such as USDT or ARB does not prove that two tokens on different chains are the same asset: check the network and, where shown, the token contract address.

Before you begin, have the wallet holding the source funds, its recovery method, and the source network’s native token for gas. For example, Ethereum and Arbitrum use ETH for ordinary network gas; ARB is a token, not Arbitrum gas. Ethereum’s documentation explains gas as the fee paid to have a transaction processed.

Step by step: make the transfer

Follow the route shown for your chosen asset pair. Each step below has a separate purpose, so check the wallet prompt before signing it.

1. Connect your wallet. Open Rhino Bridge and connect the wallet that holds the asset. Confirm that the connected account and displayed source network match where your funds are now.
2. Choose the source and destination networks. Select the network the asset is currently on as the source, then choose the network where you want to receive it. Check the direction carefully: reversing the pair changes the route and may change the available assets, fees, and timing.
3. Select the asset, amount, and recipient. Choose the supported token and enter the amount. If you can specify a recipient, use an address you control on the destination network; paste it carefully and verify its first and last characters. A familiar-looking address format does not guarantee the network is correct.
4. Review the quote. Compare the amount sent with the estimated amount received, and check the route fee, any minimum or maximum, and quote expiry if shown. For an illustrative example, a 100 USDT send might quote 99 USDT received after fees; the actual amount depends on that route’s live quote, not this example.
5. Approve the token if asked. For many ERC-20 tokens, the wallet first asks you to approve a contract to spend tokens; this approval is a separate transaction and does not send the bridge transfer. Check the spender and amount, then approve only if they match the route you selected. Native assets such as ETH do not need an ERC-20 approval.
6. Confirm and track the transfer. Read the final wallet transaction, including its network and fee, then sign it. Save the transaction hash and follow the source transaction and destination delivery separately; wait for the destination balance to update before trying again.

What affects fees, timing, and delivery?

Rhino Bridge fees depend on the selected route and quote; your total can also include source-chain gas and, when needed, approval gas. The source gas price changes with network demand, while bridge fees, route minimums, liquidity, and destination execution depend on the route. Check the displayed total immediately before signing rather than relying on a fee from an earlier transfer.

A bridge may use liquidity on the destination chain, or it may rely on a chain’s own bridge and settlement process. Those mechanisms have different waits and assumptions. For example, Arbitrum’s official documentation describes a challenge period for certain withdrawals through its native bridge; that timing does not apply to every route offered through an interface.

One edge case is receiving a token with the right ticker but the wrong network representation. A bridged version of USDT may have a different contract from the token an app expects. Verify the destination network and contract before sending a large amount, and keep some of that network’s native token available if you will need to move or swap the funds afterward.

Common questions

Why has my source balance changed, but the destination balance has not?

The source transaction can confirm before the bridge’s relayer, liquidity provider, or destination chain finishes its part. Check the source hash and the route’s status first. If the transfer remains pending, use the route’s stated recovery or support process; sending the same amount again can create a second transfer rather than fix the first.

Do I need to approve USDT every time?