You have 250 USDC on Arbitrum, need it on Base now, and the bridge form will not produce a usable quote. This is not a “wait longer” problem. A bridge can only complete a route it can price, fund, and deliver. Think of it like a courier counter: the parcel, collection depot, and destination must all be accepted before a label exists.
The fast answer is to verify the exact token-and-network pair before approving anything. An Across Bridge route should show the asset you will receive, the amount after fees, and the source and destination networks. The other side is a USDC balance on Base in the same wallet address—not USDC trapped on Arbitrum, a new wallet, or a token with the same ticker but a different contract.
Match the token you hold to the token the destination needs
In this case, choose Arbitrum as the source, Base as the destination, and USDC as both the input and output. The key figure is 250 USDC: it is the exact amount being routed, but it is not the amount you should expect to receive. The decision turns on the quoted destination amount, which must be displayed before you sign; it accounts for relay, liquidity, gas, and any swap costs.
Across is designed for supported chain-and-token pairs, including routes involving Ethereum, Arbitrum, Base, Optimism, Polygon, zkSync, Linea, Solana, BSC, Hyperliquid, and other currently listed networks. It can bridge or swap among supported assets such as USDC, USDT, ETH/WETH and other tokens available in its live route selector.
It will not take a random token simply because the symbol matches. It will not recover tokens already sent to an unsupported contract or wrong network, bridge assets from an unsupported chain, turn a seed phrase into a transfer, or make an insufficient balance usable. A balance labelled “USDC.e,” “USDC,” or “USDC0” may be a different asset; use the displayed token selection and contract details rather than its ticker alone.
Leave enough ETH on Arbitrum to pay for the transaction
This is the step that most often breaks a transfer that otherwise looks valid. USDC pays the bridge amount; Arbitrum ETH pays the wallet transaction fee. Do not enter the full wallet value if that leaves no ETH for approval or deposit. If the form reports insufficient gas, buy or move a small amount of native ETH to Arbitrum first, then request a fresh quote.
Use Across Bridge only after checking that the connected wallet is on Arbitrum and that its displayed address is yours. A correct quote with the wrong wallet network is still the wrong transaction.
Approve USDC only when the wallet names the expected contract
- Connect the wallet that holds the 250 USDC on Arbitrum.
- Select Arbitrum as the source network.
- Select Base as the destination network.
- Choose USDC as the input and output asset.
- Enter 250 USDC, while retaining enough Arbitrum ETH for gas.
- Read the output amount, fee, minimum received amount, and destination before signing.
- Approve USDC if the wallet asks for approval.
- Confirm the separate bridge deposit transaction.
- Wait for the destination fill, then switch the wallet to Base and check USDC.
Approval and deposit are often two transactions. Approving allows the bridge contract to spend the selected USDC; it does not move funds. Closing the wallet after approval is safe. The actual transfer starts only after the deposit transaction is confirmed.
Choose the bridge only when speed outweighs route availability
| Use this route when | Use another route when |
|---|---|
| The live quote supports Arbitrum USDC to Base USDC, the received amount is acceptable, and you need funds quickly. | The pair is absent, the quote is zero, the minimum exceeds 250 USDC, or you need a token not offered on the destination. |
| You want one quoted action rather than manually bridging, swapping, and paying destination gas separately. | You require a chain’s canonical bridge, have a compliance restriction, or cannot accept the quoted fee or execution conditions. |
Trace the deposit instead of sending a second transfer
If Arbitrum shows the deposit confirmed but Base has not updated, do not repeat the transfer. Copy the origin transaction hash, check the bridge history or status tool, and confirm that the destination is Base and the recipient address is correct. A pending fill needs investigation; a second deposit creates a second transfer, not a repair.