If your funds are on Ethereum and Arbitrum is not yet in your wallet, add the destination network first, then use the bridge’s official site and switch networks after the transfer completes. Chainlist supplies wallet network settings; it does not move funds.
Set up the destination network, then send
Follow these steps in order so the wallet can query the chain where the bridge will deliver your funds:
- Find the destination network on Chainlist and compare its chain ID with the ID in the bridge’s official documentation. A chain ID identifies the network, so the values should match.
- Add the network to your wallet and approve the request. The wallet may ask to add network settings through wallet_addEthereumChain. EIP-3085 defines that request, including fields such as chainId and rpcUrls, which tell the wallet how to identify and query the network. The ethereum-lists/chains GitHub repository is a public source of chain IDs and network metadata used by directories.
- Open the destination network’s official bridge, connect your wallet, and choose Ethereum as the source. Select the asset and amount, then review the destination network and confirm the transaction in your wallet.
- Wait for the bridge’s stated completion time for that direction. Timing depends on the bridge and the route between chains; changing the wallet’s RPC does not make the transfer settle faster.
- After the bridge reports completion, switch your wallet to the destination network. Look for the received asset there, rather than on Ethereum.
- Before moving the funds, confirm that your wallet holds the destination network’s native gas token. You need it to pay for transactions on that network.
You are done when the balance appears on the destination network and a small test transfer succeeds. If the destination network was already in your wallet, skip the add step and confirm its chain ID against the bridge’s documentation.
Network settings and bridge settlement do different jobs
- Network settings tell the wallet which chain to query and which RPC endpoint to use.
- The bridge handles the transfer between the source and destination chains.
- Native gas lets you send transactions once the funds arrive.
These parts work together, but they are not interchangeable. A correct RPC helps the wallet read the destination chain; it does not carry assets across chains. The bridge moves them, and the destination’s gas token lets you act on them.
The selected network determines what your wallet shows
Suppose the same Ethereum-to-Arbitrum transfer has completed in both cases. If your wallet is still set to Ethereum, it queries Ethereum and will not show the funds held on Arbitrum. Switch to Arbitrum, and the wallet queries that chain through its configured RPC; the destination balance can then appear. The transfer is the same—the selected network changes which chain the wallet reads.
If you are on Arbitrum and the balance still does not appear, confirm the network’s chain ID and that the wallet is using a working RPC for it. Then confirm the bridge reports completion and that you are viewing the asset delivered by that bridge. Completion time comes from the bridge route, while the RPC affects the wallet’s ability to read the destination chain.
Make repeat transfers easier to check
For future transfers, keep the destination chain ID from the bridge’s official documentation beside the network name you use in your wallet. If the network is already configured, comparing that ID takes the place of adding it again. When you need to add it, Chainlist supplies the destination network settings, while the official bridge remains responsible for moving your funds. This simple check helps avoid mistaking a wallet viewing the source chain for a failed transfer.
Comments
Post a Comment