Robinhood Chain Robinhood RPC & WebSocket

Standard Ethereum JSON-RPC and WebSocket on Robinhood Chain (Arbitrum L2, chain ID 4663): HTTPS and WSS endpoints, x-token auth, debug tracing, logs from genesis. Backend use, token in a header.

// updated 2026-09-24

Robinhood Chain is an Ethereum-compatible Arbitrum Layer 2, chain ID 4663, using ETH for gas. Our node speaks standard Ethereum JSON-RPC over HTTPS and eth_subscribe over WebSocket, so ethers, viem and web3.py work after you change the URL and add one header.

NOTE

Token auth, one header. Send your token as x-token on every HTTPS request and on the WebSocket handshake. Nothing else is accepted: Authorization: Bearer, x-api-key and a token in the URL all return 401.

Endpoints

Transport	URL
HTTPS JSON-RPC	`https://ny01.rh.supanode.xyz:8545`
WebSocket	`wss://ny01.rh.supanode.xyz:8546`

US East (New York). TLS only: plain http:// is not served. Keep the port in the URL, it is required. One token covers both transports.

What you get

Standard Ethereum JSON-RPC: eth_*, net_version, web3_clientVersion, filters, eth_simulateV1, eth_getProof, batch requests up to 1,000 calls.
Debug tracing: debug_traceTransaction, debug_traceBlockByNumber, debug_traceBlockByHash, debug_traceCall with callTracer and prestateTracer, plus debug_getRaw*.
WebSocket subscriptions: newHeads at the chain's ~10 blocks per second, and logs filtered by address and topics. Plain JSON-RPC calls work on the same connection.
Full history of blocks, transactions, receipts and logs since the chain started on 30 April 2026.
Recent state: eth_call, eth_getBalance and eth_getStorageAt at a past block reach back about 5 days. See What's available.

WARNING

Server-side only for now. A browser cannot send the x-token header on a WebSocket handshake, and the HTTPS endpoint does not answer CORS preflight requests. Call the node from your backend and serve your frontend from there.

Quick check

curl -s https://ny01.rh.supanode.xyz:8545 \
  -H "x-token: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Expected answer: {"jsonrpc":"2.0","id":1,"result":"0x1237"} (0x1237 is 4663). The Content-Type: application/json header is mandatory: without it the node returns 415.

Errors you may see

Response	Meaning
`401` `{"error": "Header x-token is missing"}`	No `x-token` header. Bearer, `x-api-key` and URL tokens land here too.
`403` `{"error": "Invalid x-token"}`	The header is there, the token is not valid.
`415` `invalid content type, only application/json is supported`	`Content-Type: application/json` is missing.

These errors come from the gateway, not the node: 401 and 403 are plain JSON without jsonrpc or id, and 415 is plain text.

Pricing

$389 / mo, flat, one token for HTTPS and WebSocket. Crypto-only, monthly and prepaid. See Robinhood pricing.

Free trial

Up to 24 hours, no card. Start it in the portal before you subscribe.

Getting access

Start in the portal, signed in with a Solana wallet, and you get your token. Questions? Telegram support.

Where to next

What's available

Methods, subscriptions, history depth and Arbitrum specifics.

Limits

Batches, timeouts, eth_getLogs ranges, connection habits.

Examples

curl, ethers, viem, web3.py and wscat, all run against the node.

Indexer

Decoded Uniswap and launchpad history in SQL.