If your goal is to connect a wallet to Robinhood Chain, the essential task is simple: use the documented network values, confirm the numeric chain ID, and know which endpoint is appropriate for a wallet versus an application. This guide stays focused on setup and first-use decisions. Deeper transaction forensics belong in the Blockscout guide, while malicious-RPC, phishing, approval, and fake-token threats are covered in the security verification guide.
https://rpc.mainnet.chain.robinhood.com, and robinhoodchain.blockscout.com as the documented explorer. Testnet uses chain ID 46630. Robinhood states that its public RPC is rate-limited and not recommended for production workloads. [official connection documentation]Robinhood Chain settings: mainnet and testnet
| Setting | Mainnet | Testnet |
|---|---|---|
| Network | Robinhood Chain | Robinhood Chain Testnet |
| Chain ID | 4663 | 46630 |
| Gas token | ETH | ETH |
| Default public RPC | https://rpc.mainnet.chain.robinhood.com | https://rpc.testnet.chain.robinhood.com |
| Explorer | robinhoodchain.blockscout.com | explorer.testnet.chain.robinhood.com |
These values identify the network connection. They do not authenticate a token, contract, bridge, or application. A copied network name is easy to imitate; the numeric chain ID and the endpoint you actually configured are the important checks.
Mainnet and testnet are separate environments. Mainnet assets may have real value. Testnet assets are intended for development and testing and should not be treated as having mainnet value. A wallet may remember both networks, so make the network selector part of every pre-signing review.
How to add Robinhood Chain to a wallet
- Open the wallet's network settings and choose the option to add a custom EVM network.
- Enter the mainnet values in the table above. For development, use the testnet values instead.
- Confirm that the wallet displays chain ID 4663 on mainnet or 46630 on testnet.
- Set the documented Blockscout explorer so transaction links open on the expected network.
- Before sending meaningful value, use a small test transaction and confirm the recipient, asset, network, and fee.
Robinhood Wallet supports Robinhood Chain natively, while other EVM-compatible wallets can connect manually. Robinhood Chain remains separate from Robinhood brokerage and crypto account balances; adding the network to a self-custodial wallet does not import or alter those accounts. [Robinhood support]
A native network entry reduces manual typing, but it does not remove the need to review what you are signing. A custom network entry creates more opportunities for a typo or a copied malicious endpoint, which is why the numeric chain ID and exact RPC host matter.
Public RPC or provider RPC?
Robinhood publishes a public RPC for wallets, basic reads, testing, and light interaction, but explicitly says that the public endpoint is rate-limited and is not intended for production-grade, high-throughput, or latency-sensitive applications. For production development, Robinhood currently recommends Alchemy and also lists QuickNode, Blockdaemon, dRPC, and Validation Cloud as supported providers. [endpoint guidance]
For an ordinary wallet user, the default public RPC is a reasonable documented starting point. For an application, choose a provider deliberately: review authentication, request limits, archive-data support, WebSocket availability, logging, retention, uptime commitments, and cost. If your product needs historical reads or indexing, use a provider capability designed for that purpose rather than assuming the public endpoint will behave like an archive node.
What the explorer is for
The documented mainnet explorer is Blockscout at robinhoodchain.blockscout.com. Use it to inspect a transaction hash, address, token transfer, contract bytecode, event logs, and verified source code where available. It is a reading and indexing interface over the chain, not the endpoint your wallet uses to submit ordinary JSON-RPC requests.
For a detailed walkthrough of transaction states, verified contracts, event logs, testnet, and the limits of explorer data, read Robinhood Chain Block Explorer: How to Read Blockscout. Keeping that deeper material in a separate guide avoids turning a setup page into a transaction-forensics manual.
Bridge only after the network is configured correctly
Robinhood documents the Arbitrum canonical bridge as the trustless default between Ethereum and Robinhood Chain, alongside partner routes with different speed, coverage, liquidity, and trust assumptions. Canonical deposits are described as taking about ten minutes, while a canonical withdrawal includes a roughly seven-day challenge period followed by a separate Ethereum claim transaction. [bridging documentation]
Do not choose a bridge solely because an interface shows the shortest estimated time. Check the source chain, destination chain, asset contract, recipient, expected fees, slippage where relevant, and the route's trust model. A bridged ERC-20 can have a different contract address on Robinhood Chain than on Ethereum.
Developer setup: use testnet first
Robinhood documents standard EVM deployment with Foundry and Hardhat and recommends deploying to testnet before mainnet. Testnet uses chain ID 46630 and its own RPC and explorer. Robinhood's deployment guide also shows how to verify contracts on Blockscout after deployment. [deployment documentation]
Keep private keys out of source control, use environment variables or a proper secret-management system, and prefer a throwaway deployer for experiments. Compilation and explorer source verification are useful checks, but neither is a security audit.
A safer first-transaction sequence
- Confirm chain ID 4663 and the selected account.
- Confirm the destination address from a primary source or a known recipient.
- Confirm that you have ETH on Robinhood Chain for gas.
- If a contract is involved, verify the contract address rather than relying on its displayed name.
- Send a small test amount when practical.
- Copy the resulting transaction hash and inspect it on the documented explorer.
If the transaction behaves unexpectedly, do not immediately repeat it. Preserve the hash, check the selected network, inspect the recipient and method, and determine whether the first transaction succeeded, reverted, or was never broadcast.
Common setup problems
| Problem | What to check first |
|---|---|
| Wallet shows the wrong network | Numeric chain ID, not only the displayed name. |
| RPC timeout or rate limit | Request volume and whether a provider endpoint is more appropriate. |
| Balance appears missing | Selected chain, address, token contract, and explorer record. |
| Deposit not visible | Source transaction, bridge status, destination address, and destination token. |
| Unexpected approval request | Contract address, token, allowance amount, and requesting site. |
For threat-model questions—malicious endpoints, phishing domains, fake tokens, approvals, and what an RPC can actually learn or falsify—use the dedicated security verification guide.
Sources, dates, and limits
Primary Robinhood Chain documentation and support material were rechecked on September 15, 2026. The network settings, public-RPC limitations, supported provider list, bridge timing, and testnet-first deployment guidance are all based on current primary documentation. The Blockscout explorer was used only for live explorer context; volatile statistics are intentionally excluded from this evergreen setup guide.
This is independent educational material, not Robinhood documentation, financial advice, legal advice, or a recommendation to use any particular wallet, RPC provider, bridge, token, or application.