---
title: "Connecting to Robinhood Chain"
type: concept
tags: [rpc, chain-id, wallet, block-explorer, endpoints]
created: 2026-09-09
updated: 2026-09-09
sources: ["raw/web_community-connecting-to-robinhood-chain-robinhood-chain-documentation.md", "raw/web_community-add-network-to-your-wallet-robinhood-chain-documentation.md", "raw/web_community-deploy-a-contract-robinhood-chain-documentation.md", "raw/web_community-run-a-robinhood-chain-full-node-robinhood-chain-documentatio.md"]
confidence: medium
---

# Connecting to Robinhood Chain

Every value on this page is reproduced verbatim from `docs.robinhood.com/chain` **as documented on 2026-09-09**. Check an address or URL against the live docs before moving funds.

## Network Configuration

| Property | Robinhood Chain | Robinhood Chain Testnet |
| --- | --- | --- |
| Chain ID | `4663` | `46630` |
| Currency Symbol | `ETH` | `ETH` |
| Block Explorer | `robinhoodchain.blockscout.com` | `explorer.testnet.chain.robinhood.com` |

The block explorer values are given by the docs exactly as shown — bare hostnames, no scheme. Elsewhere in the same doc set the explorer is used with a scheme, e.g. `https://robinhoodchain.blockscout.com/address/<contract_address>` and the Blockscout verification API at `https://robinhoodchain.blockscout.com/api/`.

## Public Endpoints

The docs are explicit about the tradeoff: "The following public endpoints are available but are rate-limited and not recommended for production use. For production, use a provider."

| Endpoint | Mainnet URL | Testnet URL |
| --- | --- | --- |
| RPC | `https://rpc.mainnet.chain.robinhood.com` | `https://rpc.testnet.chain.robinhood.com` |
| Sequencer Feed | `wss://feed.mainnet.chain.robinhood.com` | `wss://feed.testnet.chain.robinhood.com` |
| Sequencer | `https://sequencer.mainnet.chain.robinhood.com` | `https://sequencer.testnet.chain.robinhood.com` |

The full-node guide notes of the feed URL: "The feed URL must be `wss://`, not `https://`."

**Discrepancy worth knowing:** the Connecting page and the Deploy a Contract page both give the mainnet public RPC as `https://rpc.mainnet.chain.robinhood.com` (no trailing slash), while the Add-network-to-your-wallet page gives it as `https://rpc.mainnet.chain.robinhood.com/` (with a trailing slash). Both forms are documented; the testnet URL is given without a trailing slash on every page.

## Provider Endpoints

"Alchemy is the recommended infrastructure provider for building on Robinhood Chain." You create an app on Robinhood Chain to obtain an API key.

| Endpoint | Mainnet URL | Testnet URL |
| --- | --- | --- |
| RPC | `https://robinhood-mainnet.g.alchemy.com/v2/{API_KEY}` | `https://robinhood-testnet.g.alchemy.com/v2/{API_KEY}` |
| Websocket | `wss://robinhood-mainnet.g.alchemy.com/v2/{API_KEY}` | `wss://robinhood-testnet.g.alchemy.com/v2/{API_KEY}` |

"For historical reads and indexing, use an archive endpoint — available through providers such as Alchemy."

Alchemy's documented service surface on this chain: **Node API** (standard JSON-RPC and Websocket), **Data API** ("Instant, reliable access to indexed blockchain data like token balances, transaction history, NFTs, and portfolio activity"), and **Gasless Transaction Infrastructure** (programmable wallets with gas sponsorship, batched transactions, policies, spending controls) — see [account-abstraction.md](account-abstraction.md).

### Other providers

"Robinhood Chain is also supported by QuickNode, Blockdaemon, dRPC, and Validation Cloud. Sign up directly with your provider to get an endpoint."

QuickNode endpoints follow the template:

```
https://{ENDPOINT}.robinhood-mainnet.quiknode.pro/{TOKEN}
```

The full-node page lists a slightly longer provider set with landing pages: Quicknode (`https://www.quicknode.com/chains/robinhood`), Blockdaemon (`https://docs.blockdaemon.com/docs/how-to-connect-to-robinhood`), dRPC (`https://drpc.org/chainlist/robinhood-testnet-rpc`), Validation Cloud (`https://www.validationcloud.io/robinhood`), Chainstack (`https://chainstack.com/build-better-with-robinhood-chain/`), GlobalStake (`https://GlobalStake.io`).

## Adding the Network to a Wallet

### Robinhood Wallet

"Robinhood Wallet provides support for Robinhood Chain." The documented steps are: download Robinhood Wallet (requires iOS or Android), then create a wallet.

### Browser wallets

"Robinhood Chain is compatible with EVM Wallets (MetaMask and more)." The docs page offers a click-to-add widget; in the 2026-09-09 capture that widget had not rendered (the page shows only "Loading wallet connection..."), so the automatic-add targets are not recoverable from this source.

To add manually to MetaMask, the docs give these fields:

| Property | Robinhood Chain | Robinhood Chain Testnet |
| --- | --- | --- |
| Chain ID | `4663` | `46630` |
| Default RPC URL | `https://rpc.mainnet.chain.robinhood.com/` | `https://rpc.testnet.chain.robinhood.com` |
| Currency Symbol | `ETH` | `ETH` |
| Block Explorer | `robinhoodchain.blockscout.com` | `explorer.testnet.chain.robinhood.com` |

## Toolchain Configuration

The Deploy a Contract guide gives working configuration for both major toolchains.

Foundry (environment + verification):

```bash
export RH_RPC_URL=https://rpc.mainnet.chain.robinhood.com

forge verify-contract <contract_address> \
  src/HelloRobinhood.sol:HelloRobinhood \
  --chain-id 4663 \
  --rpc-url $RH_RPC_URL \
  --verifier blockscout \
  --verifier-url https://robinhoodchain.blockscout.com/api/
```

Hardhat network + custom-chain block:

```js
networks: {
  robinhood: {
    url: process.env.RH_RPC_URL,
    chainId: 4663,
    accounts: [process.env.PRIVATE_KEY],
  },
},
etherscan: {
  apiKey: { robinhood: "empty" },
  customChains: [
    {
      network: "robinhood",
      chainId: 4663,
      urls: {
        apiURL: "https://robinhoodchain.blockscout.com/api",
        browserURL: "https://robinhoodchain.blockscout.com/",
      },
    },
  ],
},
```

For testnet, the docs say: "set `RH_RPC_URL` to the testnet RPC, use chain ID 46630, and verify against `https://explorer.testnet.chain.robinhood.com/api/`."

## Running Your Own Node

If you need your own endpoint rather than a hosted one, the node is Nitro. Ports are `8547` (HTTP) and `8548` (WS); the container image documented is `offchainlabs/nitro-node:v3.11.2-3599aca`; the chain runs **ArbOS 61**. A node needs *both* an L1 execution RPC endpoint and an L1 beacon (consensus) endpoint, "required to read blob data". The docs' own caveat: "If you don't already know why you need your own node, you probably don't."

## Bringing Funds Onto the Chain

"To move funds onto Robinhood Chain, use the canonical Arbitrum bridge or one of several cross-chain routes." The canonical route deposits in roughly 10 minutes and withdraws subject to a ~7-day challenge period; see [transaction-finality.md](transaction-finality.md) for why the withdrawal delay is not the same thing as finality.

## Related Concepts

- [what-is-robinhood-chain.md](what-is-robinhood-chain.md)
- [gas-and-fees.md](gas-and-fees.md)
- [account-abstraction.md](account-abstraction.md)

## Sources

- `raw/web_community-connecting-to-robinhood-chain-robinhood-chain-documentation.md`
- `raw/web_community-add-network-to-your-wallet-robinhood-chain-documentation.md`
- `raw/web_community-deploy-a-contract-robinhood-chain-documentation.md`
- `raw/web_community-run-a-robinhood-chain-full-node-robinhood-chain-documentatio.md`