Bridge ETH to Robinhood Chain: Routes, 7-Day Exit

Last updated: October 24, 2026

Endpoint and plans: Robinhood Chain RPC endpoint.

At a glance

What you see

You hold ETH on Ethereum and need gas on Robinhood Chain. Search results show several bridges and look-alike sites, a wallet asks you to sign a call to an address you cannot place, the deposit seems to vanish for several minutes, or you plan to move funds back and discover the canonical route takes a week.

Why this happens

Robinhood Chain is an Arbitrum-based Layer-2 whose native bridge is Arbitrum's. Robinhood's bridging page names the Arbitrum canonical bridge as the trustless route for ETH and ERC-20s, with deposits taking about 10 minutes and withdrawals about 7 days, and says programmatic bridging goes through the Delayed Inbox contract on Ethereum. The protocol-contracts page lists that Delayed Inbox at 0x1A07cc4BD17E0118BdB54D70990D2158AbAD7a2D on Ethereum mainnet. Arbitrum's messaging reference explains what happens on arrival: the ETH sent with Inbox.depositEth is held by the bridge contract on Ethereum and credited on the child chain to the same address when the sender is an externally owned account, or to the sender's aliased address when it is a contract (or an EIP-7702 account). The return trip has a different shape: a withdrawal is started on Robinhood Chain, waits the 7-day challenge period, and is then claimed on Ethereum, with the claim paying L1 gas. Robinhood's finality page keeps the two apart — "Finality is distinct from the withdrawal delay" — so a transaction can be final on Robinhood Chain while its withdrawal is still waiting. Third-party routes that Robinhood lists (intent-based bridges, token-bridge protocols, swap aggregators) settle in seconds to minutes in Robinhood's own table, but they are separate services with their own trust assumptions.

Deposit and withdrawal paths, step by step

What to do

1. Start from Robinhood's own bridging page (docs.robinhood.com/chain/bridging), not from a search result or a direct message, and follow its link to the bridge you choose.
2. Before signing a canonical deposit, compare the contract in the wallet prompt with the Delayed Inbox address on Robinhood's protocol-contracts page, and the function with depositEth() (0x439370b1). Any other address on a "Robinhood bridge" is not the canonical route.
3. Deposit from a regular wallet if you want the ETH at the same address on Robinhood Chain; a deposit sent by a contract lands at the contract's aliased address.
4. Record the receiving address's balance on Robinhood Chain before the deposit, then poll eth_getBalance on chain ID 4663 until it rises; allow about 10 minutes before suspecting a problem, and check that your wallet is connected to chain ID 4663, not to Ethereum.
5. If the L2 leg of a canonical deposit fails, for example for lack of gas, Robinhood's bridging page says it can be redeemed manually from the bridge interface within 7 days.
6. Plan exits before you deposit: the canonical withdrawal takes the 7-day challenge period plus a claim on Ethereum. Third-party routes listed by Robinhood settle in seconds to minutes by its table, but they are separate services; check their terms yourself.

ADDR=0xYourAddress
curl -s "$RH_RPC_URL" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["'"$ADDR"'","latest"]}'
# run once before the deposit and again after it; result is hex wei

cast balance "$ADDR" --ether --rpc-url "$RH_RPC_URL"   # same check with Foundry

cast chain-id --rpc-url "$RH_RPC_URL"   # 4663 on mainnet

When this is not our problem

The bridge contracts, deposit times and the 7-day withdrawal window belong to Robinhood Chain's Arbitrum bridge and to whichever third-party route you choose; no RPC provider, Triport included, operates them or can speed them up. Triport provides the read side for the arrival check on Robinhood Chain mainnet: set RH_RPC_URL to the keyed URL form https://triport.io/r/<YOUR_KEY>/robinhood.