What You Need Before Bridging
Prepare three items before opening Rhino Bridge: a Web3 wallet connected to the source chain, the tokens you want to transfer, and enough of the source chain’s native token to pay the network fee. Install a wallet such as MetaMask, Rabby, or a WalletConnect-compatible wallet. The official MetaMask site provides the browser extension and mobile app directly.
Switch the wallet to the chain that currently holds your ETH, USDC, or ERC-20 token. If the network is missing from the wallet, use the Chainlist network directory to locate its chain ID and add the correct RPC configuration. Keep native gas funds on that source chain: ETH pays gas on Ethereum, Arbitrum, Base, Optimism, and other Ethereum rollups, while each non-Ethereum network uses its own native gas asset.
- Confirm that the wallet address controls the tokens on the source chain.
- Check that the intended token appears in the wallet on that network.
- Reserve native gas funds in addition to the amount being bridged.
Connect Your Wallet to Rhino Bridge
Open app.rhino.fi, select Connect Wallet, choose your wallet provider, and approve the connection request inside the wallet. A connection approval authorizes Rhino to read the public address and request transactions; it does not move tokens. The Ethereum.org wallet guide explains how wallets manage accounts and sign actions.
Rhino detects the chain currently selected in the wallet and displays it as the source network. If the bridge interface shows a different source, switch networks in the wallet and approve the network change. Match the abbreviated wallet address shown in Rhino with the address holding the tokens before selecting a route.
Select Source and Destination Chains
Set the From field to the chain holding your tokens and set the To field to the chain where you want to receive them. This direction controls where the transaction starts and where Rhino delivers the destination asset. The Ethereum.org bridge overview describes the cross-chain transfer model and the role of bridge routes.
Select ETH, USDC, or another supported ERC-20 token from the asset menu. Token availability depends on liquidity for the chosen chain pair, so the asset list updates when either network changes. Rhino then displays the routes available for that pair, along with the expected fees and delivery estimate. Verify the source, destination, token symbol, and receiving wallet address as one complete route before entering an amount.
Enter Amount and Review the Quote
Enter the amount to bridge and read every quote field before continuing. Review the exchange rate, bridge or liquidity fee, source-chain network fee, minimum amount received, and estimated completion time. The Ethereum gas documentation explains why the network fee changes with block demand and transaction complexity.
Rhino aggregates routes across available liquidity sources and selects the cheapest available path for the requested transfer. Route quality changes with token liquidity, chain conditions, and transfer size. Use the live quote shown in Rhino as the transaction-specific cost record; the Rhino protocol page on DeFiLlama provides independent protocol data for additional context.
- Check that the input amount leaves enough native token for gas.
- Compare the total fees against the minimum received, not the headline rate alone.
- Refresh an expired quote before signing so the displayed route matches current liquidity.
Confirm and Track Your Transfer
Select Bridge, review the wallet transaction, and confirm it on the source chain. The wallet shows the contract interaction, spending amount, and network fee before signature. After broadcast, Rhino displays a source transaction hash and transfer status while the route settles on both chains.
Open the source hash in Etherscan for Ethereum or the appropriate source-chain explorer. For an Arbitrum destination, use Arbiscan to verify the receiving transaction and final token balance. A completed source transaction proves the funds left the sending chain; the destination hash confirms delivery to the same wallet address on the receiving chain.
When to Use Stack Mode
Use Retail Mode for standard transfers that need a direct, one-click route. Retail Mode handles route selection, fee comparison, and normal slippage settings automatically, which keeps the workflow to wallet connection, route selection, quote review, and confirmation.
Use Stack Mode for transfers above $10,000 or when the route requires manual control. Stack Mode exposes custom slippage and multiple liquidity sources, allowing you to compare route construction before signing. Review the wider bridge market through DeFiLlama’s bridge liquidity data, then select the Rhino route whose fees, minimum received, and execution settings match the transfer. Recheck the final wallet prompt after changing slippage or liquidity sources because each adjustment creates a new transaction quote.