Robinhood Chain RPC Endpoint
Free Robinhood Chain mainnet RPC endpoint. No API key required for public access. Low-latency JSON-RPC with automatic failover — Chain ID 4663.
Connect to Robinhood Chain mainnet over HTTPS. Robinhood Chain is Robinhood's Arbitrum Orbit L2 for tokenized real-world assets — NodeFlare serves it from its own node.
Endpoint URL
https://rpc.nodeflare.app/robinhood/v1/{YOUR_KEY}Public endpoint (no API key)
https://rpc.nodeflare.app/robinhood/publicNo API key required. Rate-limited to 1 request per 10 s per IP, basic methods only. Heavy methods including eth_getLogs need a key — sign up for a free one to unlock them.
Quick Test
curl https://rpc.nodeflare.app/robinhood/v1/YOUR_KEY \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Supported Methods
| Category | Methods |
|---|---|
| Chain | eth_chainId → 4663, net_version, web3_clientVersion |
| Blocks | eth_blockNumber, eth_getBlockByHash, eth_getBlockByNumber |
| Transactions | eth_sendRawTransaction, eth_getTransactionByHash, eth_getTransactionReceipt, eth_getTransactionCount |
| State | eth_getBalance, eth_getCode, eth_getStorageAt, eth_call |
| Gas | eth_gasPrice, eth_estimateGas, eth_maxPriorityFeePerGas, eth_feeHistory |
| Logs | eth_getLogs, eth_newFilter, eth_getFilterLogs |
The debug_* and trace_* namespaces are not enabled on this chain. They are the direct cause of every crash we have seen on these nodes, so they stay off; calls to them return -32601.
WebSocket for Robinhood Chain is not wired through the gateway yet — HTTP polling covers most workloads. See the per-method reference for parameters, compute-unit costs, and copy-paste examples.
Chain Info
| Property | Value |
|---|---|
| Chain ID | 4663 |
| Native token | ETH |
| Block time | ~100 ms (~10 blocks/s) |
| Method reference | /chains/robinhood |
Rate Limits
Free keys include 3,000,000 CU/month at 10 req/s. eth_getLogs costs 25 CU. See rate limits for the full table.
eth_getLogs on this chain is also capped per call: 5,000 blocks when your filter names an address or a topic, 10 blocks when it names neither. At ~10 blocks per second an unfiltered scan has to decode every receipt in the range, which is why the unfiltered cap is small. Over the cap you get an immediate 400 explaining how to split or filter the query — never a hanging connection.