The network registry
The app uses a curated network and token registry. The live network selector is the current source of truth for enabled transfer pairs; a route must also be available from the routing provider at quote time.
| Network | Chain ID | Role |
|---|---|---|
| Ethereum | 1 | EVM workspace network |
| Base | 8453 | EVM workspace network |
| Arbitrum One | 42161 | EVM workspace network |
| Optimism | 10 | EVM workspace network |
| Polygon | 137 | EVM workspace network |
| Robinhood Chain | 4663 | Read-only asset data and ERC-20 balance inspection |
| Robinhood Chain Testnet | 46630 | External development network; not used by this app |
A symbol is not an identity
Move money routes native USDC. The separate USDG vault wraps canonical Robinhood USDG, supports atomic native USDG payments and redemptions, and offers an issuer-routed Ethereum exit. USDT is not enabled. Native issuance and bridged representations can have different contract addresses, liquidity, redemption paths, and trust assumptions even when their displayed symbols look similar.
The app must use the registered contract and its decimals when reading balances or constructing a quote. Verify the destination contract against the application where you intend to spend the funds.
When a transfer is eligible
- Both networks and the selected token pair are enabled in the application.
- The source account holds enough of the source asset and native gas token.
- The routing provider supplies a current executable quote.
- The connected wallet supports the source chain and transaction type.
- The destination is accessible by the recipient and supports the expected asset.
Robinhood Chain is a read-only integration
Robinhood's official documentation lists mainnet chain ID 4663 and testnet chain ID 46630, with ETH used for gas. The Asset layer reads mainnet metadata and imported ERC-20 balances.
This read-only integration does not enable stablecoin routes to Robinhood Chain. Route support, token contracts, liquidity, and execution must be verified separately before enabling transfers.
Adding a new network
Network admission should include verified chain metadata, token provenance, a production RPC, test transfers, monitoring, and a documented bridge risk assessment. The interface should expose unavailable routes clearly and remove an affected route if reliable execution cannot be maintained.