Robinhood Chain RPC endpoint: chain ID, public endpoints, and Edge setup
Robinhood Chain's chain ID, public RPC URLs, and explorer, then a Goldsky Edge RPC endpoint for mainnet and testnet and one call that checks the connection.

Software Engineer
A Robinhood Chain RPC endpoint comes from two places: the public endpoints that Robinhood publishes, and an RPC provider. The chain ID is 4663 for mainnet and 46630 for testnet, and ETH pays gas on both. Robinhood marks its public endpoints as rate-limited and not recommended for production. Goldsky Edge RPC serves both networks at one URL format with the chain ID in the path. This guide lists the network facts, then gets an Edge endpoint and checks the connection.
Network facts
Each value in this table comes from Robinhood's page on connecting to Robinhood Chain (opens in a new tab).
| Property | Mainnet | Testnet |
|---|---|---|
| Network name | Robinhood Chain | Robinhood Chain Testnet |
| Chain ID | 4663 | 46630 |
| Currency symbol | ETH | ETH |
| Block explorer | robinhoodchain.blockscout.com | explorer.testnet.chain.robinhood.com |
| Public 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 feed, delayed backup | wss://delayed-feed.mainnet.chain.robinhood.com | None |
Robinhood Chain is an Arbitrum Layer 2 on Ethereum and uses Ethereum blobs for data availability. Tooling that works with an Arbitrum chain works with these values.
The sequencer feed is a WebSocket stream and is separate from the JSON-RPC endpoint. On mainnet, the delayed backup feed runs about 500 ms behind the primary feed on separate capacity. Robinhood recommends it as the fallback for an app that reads the feed.
When a public endpoint is enough
Robinhood's page states that the public endpoints are rate-limited and not recommended for production. For production, it says to use a provider. The page gives no number for the rate limit, so this guide states none.
| Use | Public endpoint | Provider endpoint |
|---|---|---|
| A script, a demo, or a wallet network entry | Enough | Not necessary |
| A live app or a backend service | Robinhood does not recommend it | Use one |
| Historical reads and indexing | Robinhood points to an archive endpoint from a provider | Use one |
A team that plans a production app needs a provider endpoint before the first deploy.
Get a Goldsky Edge endpoint for Robinhood Chain
Goldsky Edge RPC supports Robinhood Chain Mainnet and Testnet. The Robinhood Chain page in the Goldsky docs (opens in a new tab) lists one endpoint for each network:
| Network | Chain ID | Edge RPC endpoint |
|---|---|---|
| Mainnet | 4663 | https://edge.goldsky.com/standard/evm/4663?key=YOUR_KEY |
| Testnet | 46630 | https://edge.goldsky.com/standard/evm/46630?key=YOUR_KEY |
The steps come from the Edge RPC quickstart (opens in a new tab):
- Create a Goldsky account. An account is free.
- Build the endpoint URL:
https://edge.goldsky.com/standard/evm/{chainId}?key={your-key}. - Send a JSON-RPC request to that URL.
The quickstart also accepts key=demo with no account, for demos and tests only.
The docs give these request examples for Robinhood Chain Mainnet:
curl "https://edge.goldsky.com/standard/evm/4663?key=YOUR_KEY" \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'import { createPublicClient, http } from 'viem'
const client = createPublicClient({
transport: http('https://edge.goldsky.com/standard/evm/4663?key=YOUR_KEY')
})
const blockNumber = await client.getBlockNumber()For testnet, change the chain ID in the URL to 46630. The request format and the key stay the same, so a move from testnet to mainnet is a change of one number.
Check the connection with one call
eth_chainId returns the chain ID of the network behind the endpoint. This is the request from the eth_chainId reference (opens in a new tab), with chain ID 4663 in the URL:
curl -X POST "https://edge.goldsky.com/standard/evm/4663?key=demo" \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "method": "eth_chainId", "params": [], "id": 1}'On 2026-11-18, this request returned 0x1237, which is 4663 in hex. Robinhood's public mainnet endpoint returned the same value. The testnet value is 0xb626. A different value in the response means that the URL points to a different network.
Limits and price
| Topic | What the Goldsky docs state |
|---|---|
| Price | $5 per million requests, with all methods priced equally |
| Rate limit | Set per API key in the Goldsky Dashboard, from about 100 to about 10,000 requests per second in total, or unlimited |
| Per-IP limit | Optional, about 1.7 or about 8 requests per second per IP address |
| Transport | JSON-RPC over HTTPS |
| Payment with no account | x402 nanopayments in USDC |
The rate limit options are on the page for Edge RPC security (opens in a new tab). To get new blocks or logs over HTTPS, poll with eth_newBlockFilter or eth_newFilter and then eth_getFilterChanges.
A per-IP limit protects a key that is in frontend code, where any visitor can read it.
What Edge adds to a Robinhood Chain endpoint
The Edge RPC introduction (opens in a new tab) lists what the service does for each request:
- Routing: edge infrastructure in 8 or more regions.
- Failover: automatic failover across multiple upstream providers, for 99.9% uptime.
- Caching: caching and request deduplication for frontend traffic.
- Observability: built-in Grafana dashboards (opens in a new tab) with request volume, error rates, and response time percentiles by network and by method.
Edge RPC is built on eRPC, an open source RPC proxy. This guide states no latency number. Goldsky's live RPC provider comparison shows latency, errors, and block lag by provider.
The team gets failover and caching with the endpoint and does not run a proxy of its own.
What else Goldsky runs on Robinhood Chain
Goldsky also supports Subgraphs, Turbo Pipelines, and Compose on Robinhood Chain Mainnet and Testnet. Goldsky's Robinhood Chain page showed 11 dataset types indexed live on 2026-11-18, with ERC-20 transfers, Stock Token transfers, raw logs, and raw traces among them. Robinhood Chain data is live on Goldsky covers the indexing products.
An app that needs decoded history or streams, not single RPC reads, uses those products with the same account.
FAQ
What is the chain ID of Robinhood Chain?
4663 for mainnet and 46630 for testnet. In hex, the values are 0x1237 and 0xb626.
Is the public Robinhood Chain RPC endpoint enough for a production app?
Robinhood states that its public endpoints are rate-limited and not recommended for production. For production, Robinhood says to use a provider.
Does one Goldsky key work for mainnet and testnet?
Yes. The key is the same, and the chain ID in the URL selects the network.
What does an Edge RPC request to Robinhood Chain cost?
$5 per million requests. All methods have the same price.
How does a team start with Robinhood Chain on Goldsky?
Create a free Goldsky account, put chain ID 4663 and the key in the Edge RPC URL, and send eth_chainId. The response 0x1237 shows that the connection works.