How to bridge out of Robinhood Chain
This page is already set to bridge out — Robinhood Chain is the source. (The small reverse arrow next to the heading flips back to bridging in, if you need it.) Start by picking where the funds should land: Ethereum, Base or Solana. The source asset on Robinhood Chain is ETH today; USDG may be added as a selectable input later. Connect an EVM wallet that already holds funds on Robinhood Chain (chain ID 4663) — that wallet signs the outbound transaction. Enter or confirm the recipient on the destination network, since the address that receives is separate from the one that signs. Request a fresh live quote and review the output amount, the recipient, the estimated time and the network cost before you sign. Keep some ETH on Robinhood Chain to cover gas: the outbound transaction is paid in ETH on the source network, and without it the withdrawal cannot be sent.
Bridging out to Solana needs a Solana recipient
Solana is where directions cross virtual machines, so read this before you sign. You still sign with your EVM wallet on Robinhood Chain, but the recipient must be a Solana (SVM) address. An EVM 0x address cannot receive on Solana; funds sent to the wrong address type can be lost. Connect a Solana wallet — Phantom, Solflare or Backpack — or paste a Solana address into the recipient field. The interface validates the address format for the destination network and flags an entry that does not fit. Never send to an address on the wrong network. Native ETH bridged out to Solana is delivered as SOL: a conversion at the quoted rate, not the same token in a new place. The quote states the output token before you sign, so check it there.
Intent-based routes vs the canonical withdrawal
There are two ways off Robinhood Chain, and they behave differently. The routes quoted in this interface are intent-based, provided via Relay, and are typically settled in seconds to minutes when liquidity is available. They rely on third-party liquidity, so a route can quote for one amount and fail for a larger one at the same moment. Separately, Robinhood Chain is built with Arbitrum technology, and it keeps the canonical Arbitrum-style withdrawal to Ethereum. That path carries a challenge period of roughly seven days, followed by a final claim transaction on Ethereum (L1). It uses no third-party liquidity, so it does not depend on a route being available.
Which one fits depends on the transfer. Intent-based routes suit speed on supported destinations, amounts and available liquidity. The canonical withdrawal suits large amounts, or any time no intent route or liquidity is available and you can wait out the challenge period. It reaches Ethereum only; for Base or Solana, an intent-based route is the path.
| Method | Destinations | Typical time | Notes |
|---|---|---|---|
| Intent-based (Relay) | Ethereum, Base, Solana | Seconds to minutes, liquidity permitting | Integrated in this interface |
| Canonical Arbitrum-style withdrawal | Ethereum only | ~7 days + L1 claim | Native L2→L1 path, no third-party liquidity needed |
Fees and estimated time for bridging out
Bridging out breaks down into the same cost components as bridging in, and the quote names each one before you sign:
- Source gas on Robinhood Chain, paid in ETH.
- Bridge and protocol cost of the route that executes the transfer.
- Price impact, where the route involves a swap between assets.
- Slippage tolerance and minimum received — the quote applies your slippage setting and states the minimum you should receive.
The estimated time comes from the live quote and is an estimate, not a guarantee; liquidity, finality and congestion all shift real delivery times. For the canonical withdrawal, the roughly seven-day challenge period applies before you can claim on Ethereum.
Safety when bridging out
A few habits remove most of the ways an outbound transfer goes wrong. Confirm the recipient is on the correct destination network before signing: an EVM address for Ethereum or Base, a Solana address for Solana. Send a small first test transaction, confirm it arrives, then move the rest. After the transfer completes, verify it on the destination network's explorer, so you can see the received token and amount for yourself. This interface never asks for your seed phrase or private key; treat any such request as a scam. If the funds do not appear in your wallet, the network or the token may need to be added manually before the balance shows. Keep your transaction hash: it is the record of what happened on chain, and it is what any support conversation will start from.