Bridge routes have different completion rules
Robinhood documents a canonical Arbitrum bridge and partner routes. They differ in supported assets, timing, liquidity and trust assumptions. The canonical L2-to-L1 withdrawal has a challenge-period process measured in days; a faster partner route follows a different mechanism. Do not promise the same completion time for every route.
Prepare an evidence checklist
- Open the route through Robinhood's official bridging documentation.
- Verify source and destination chain IDs and the actual token contract on each side.
- Review the route's current quoted fees, minimums and expected stages before signing.
- Keep enough native currency on the relevant chains for later required transactions.
- Record the source transaction and the bridge's message or withdrawal identifier.
Check arrival on the destination
{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["DESTINATION_ADDRESS","latest"]}For native ETH, compare the destination balance with a baseline and inspect the corresponding destination transaction when available. For a bridged ERC-20, inspect the correct token contract and transfer event instead. A source-chain receipt alone is not proof of destination delivery.
Track the full lifecycle
Model submitted, source included, message pending, destination executed and failed or delayed as separate states. Reconcile the bridge's documented finality requirements before treating funds as spendable. The canonical withdrawal process can require a later completion action. This article provides a verification workflow; it does not initiate a bridge or recommend moving a particular amount.