Robinhood Chain Nodes

Overview

OrbitFlare provides node infrastructure for Robinhood Chain, the EVM-compatible Ethereum Layer 2 that Robinhood launched on mainnet in July 2026. The chain is built on the Arbitrum Orbit (Nitro) stack, uses ETH for gas, and is home to Robinhood’s tokenized stocks, which trade around the clock and integrate with DeFi protocols such as Uniswap and Chainlink from day one. If you are building trading systems, indexers, or DeFi integrations around tokenized equities, OrbitFlare gives you direct node access without operating Nitro infrastructure yourself. Because the chain is fully EVM-compatible, standard tooling like Hardhat, Foundry, ethers.js, viem, and Wagmi works against the endpoint without modification, and the chain has first-class support for ERC-4337 account abstraction.

Robinhood Chain node access is available for purchase directly from the OrbitFlare dashboard. Learn more on the product page.

Robinhood Chain access is also included with the OrbitFlare Pass NFT, capped at 100 RPS for Pass holders and renters.

Endpoints

Mainnet
Testnet

Robinhood Chain mainnet runs in two regions. Use the endpoint closest to your servers.

Region	JSON-RPC (HTTP)	WebSocket
US (Ohio)	`https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY`	`wss://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY`
Amsterdam (EU)	`https://ams.robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY`	`wss://ams.robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY`

Robinhood Chain mainnet uses chainId: 4663 with ETH as the gas token.

Access

Authenticate with your OrbitFlare license key, passed as the ?api_key= query parameter on both the HTTP and WebSocket URLs (the same key format, ORBIT-XXXXXX-NNNNNN-NNNNNN, used across OrbitFlare products). A license can optionally be placed in IP-whitelist mode, where only whitelisted source IPs may connect and requests still carry the key; manage the mode and whitelist from the dashboard.

Robinhood Chain also runs a public testnet (chainId: 46630), an Arbitrum Orbit chain settling to Ethereum Sepolia with ETH as the gas token:

Resource	Location
Faucet	faucet.testnet.chain.robinhood.com
Explorer	explorer.testnet.chain.robinhood.com
Bridge (from Sepolia)	Arbitrum Bridge

Generate a throwaway keypair, request testnet ETH from the faucet, and you can exercise the full transaction lifecycle end to end.

The OrbitFlare endpoint serves mainnet only.

Making RPC Calls

Robinhood Chain is EVM-compatible and speaks standard JSON-RPC 2.0. Pass Content-Type: application/json with a POST body:

curl -X POST "https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_blockNumber",
    "params": [],
    "id": 1
  }'

import { createPublicClient, defineChain, http } from "viem";

const robinhoodChain = defineChain({
  id: 4663,
  name: "Robinhood Chain",
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: {
    default: { http: ["https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY"] },
  },
});

const client = createPublicClient({
  chain: robinhoodChain,
  transport: http(),
});

const block = await client.getBlockNumber();
console.log("Latest block:", block);

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY"))

print("Connected:", w3.is_connected())
print("Chain ID:", w3.eth.chain_id)       # 4663
print("Latest block:", w3.eth.block_number)

WebSocket Subscriptions

Real-time subscriptions run over the WebSocket endpoint. In Node.js, install the ws package (npm install ws):

import WebSocket from "ws";

const ws = new WebSocket("wss://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY");

ws.on("open", () => {
  ws.send(JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "eth_subscribe",
    params: ["newHeads"],
  }));
});

ws.on("message", (data) => {
  const msg = JSON.parse(data);
  console.log("New block header:", msg.params?.result);
});

Robinhood Chain produces blocks roughly every 100 milliseconds, so expect a much faster newHeads cadence than on Ethereum mainnet or most L2s.

Supported Methods

The node exposes the standard EVM JSON-RPC surface, including:

Category	Methods
Blocks	`eth_blockNumber`, `eth_getBlockByHash`, `eth_getBlockByNumber`
Transactions	`eth_sendRawTransaction`, `eth_getTransactionByHash`, `eth_getTransactionReceipt`
Accounts	`eth_getBalance`, `eth_getCode`, `eth_getStorageAt`, `eth_getTransactionCount`
Contracts	`eth_call`, `eth_estimateGas`, `eth_getLogs`
Network	`net_version`, `eth_chainId`, `eth_gasPrice`, `eth_feeHistory`
WebSocket	`eth_subscribe` (newHeads, logs, newPendingTransactions)

As an Arbitrum Nitro chain, the node also serves the arb_* extension methods alongside the standard eth_* set. For the full method reference, see the Ethereum JSON-RPC specification.

Rate Limits and Quotas

These limits apply to all OrbitFlare EVM chains (Robinhood, Polygon, BSC). They are enforced per license, and HTTP and WebSocket traffic on the same key share a single rate limit and in-flight budget.

Control	Free	Paid
Requests / second	plan RPS	plan RPS
Batch size (HTTP + WS)	1 item	100 items
`eth_getLogs` in flight	1	10
`eth_getLogs` block range	150 blocks	10,000 blocks
`debug_` / `trace_` methods	blocked	allowed
WebSocket connections	1	from 10
Subscriptions per WebSocket connection	5	25
`logs` subscription without a filter	refused	allowed
WebSocket data per connection	1 GiB	unlimited

Applies to both tiers: WebSocket connection lifetime of 24 hours; idle timeout of 30 minutes with no data frames; frame size of 4 MiB inbound and 32 MiB outbound; each batch item counts as one request.

Error Codes

HTTP	JSON-RPC	Meaning
429	`-32429`	Rate limit exceeded
429	`-32005`	Concurrent, batch, connection, or subscription limit exceeded
400	`-32602`	`eth_getLogs` block range too large (the message names the span)
403	`-32601`	Method not available on this plan
403	`-32406`	WebSockets not enabled for this key

-32005 and -32429 are transient. Retry with exponential backoff. If -32005 persists on isolated calls, another client is likely using the same key concurrently, since HTTP and WebSocket share one in-flight budget.

Example: Reading a Tokenized Stock

The chain’s flagship assets are Robinhood’s tokenized stocks, which are standard ERC-20 contracts. Here is the NVIDIA token (NVDA) read directly from chain state:

import { createPublicClient, defineChain, erc20Abi, http } from "viem";

const robinhoodChain = defineChain({
  id: 4663,
  name: "Robinhood Chain",
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: {
    default: { http: ["https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY"] },
  },
});

const client = createPublicClient({ chain: robinhoodChain, transport: http() });

const NVDA = "0xd0601CE157Db5bdC3162BbaC2a2C8aF5320D9EEC";

const [name, symbol, decimals, totalSupply] = await Promise.all([
  client.readContract({ address: NVDA, abi: erc20Abi, functionName: "name" }),
  client.readContract({ address: NVDA, abi: erc20Abi, functionName: "symbol" }),
  client.readContract({ address: NVDA, abi: erc20Abi, functionName: "decimals" }),
  client.readContract({ address: NVDA, abi: erc20Abi, functionName: "totalSupply" }),
]);

console.log(`${name} (${symbol}), ${totalSupply / 10n ** BigInt(decimals)} shares tokenized`);
// NVIDIA • Robinhood Token (NVDA), 26419 shares tokenized

# symbol() on the NVDA token contract
curl -X POST "https://robinhood.rpc.orbitflare.com?api_key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [{
      "to": "0xd0601CE157Db5bdC3162BbaC2a2C8aF5320D9EEC",
      "data": "0x95d89b41"
    }, "latest"],
    "id": 1
  }'

Search the explorer carefully before hardcoding token addresses: many copycat tokens use the NVDA symbol. The official Robinhood stock tokens carry the • Robinhood Token naming, and the address above is the one held by tens of thousands of accounts.

Use Cases

Tokenized Stock Trading

Trade and monitor on-chain equities like NVDA and AAPL 24/7, without market-hours limits.

DeFi Integrations

Build against Uniswap pools and Chainlink feeds live on the chain since launch.

Indexers & Analytics

Follow 100ms blocks in real time over WebSocket and keep your own view of chain state.

Get Started

Purchase from the Dashboard

Buy Robinhood Chain node access directly from the OrbitFlare dashboard and grab your license key.

Rust SDK

Typed RPC and WebSocket clients for Robinhood Chain, built on alloy with retry and failover out of the box.

Product Page

Learn more about Robinhood Chain RPC access, pricing, and what’s included.

Get Started

Agents

Products

Solutions

Fetching Data

RPC

Data Streaming

Trading APIs

Robinhood Chain Nodes

Overview

Endpoints

Access

Making RPC Calls

WebSocket Subscriptions

Supported Methods

Rate Limits and Quotas

Error Codes

Example: Reading a Tokenized Stock

Use Cases

Tokenized Stock Trading

DeFi Integrations

Indexers & Analytics

Get Started

Purchase from the Dashboard

Rust SDK

Product Page

Official Resources

​Overview

​Endpoints

​Access

​Making RPC Calls

​WebSocket Subscriptions

​Supported Methods

​Rate Limits and Quotas

​Error Codes

​Example: Reading a Tokenized Stock

​Use Cases

Tokenized Stock Trading

DeFi Integrations

Indexers & Analytics

​Get Started

Purchase from the Dashboard

Rust SDK

Product Page

​Official Resources

Overview

Endpoints

Access

Making RPC Calls

WebSocket Subscriptions

Supported Methods

Rate Limits and Quotas

Error Codes

Example: Reading a Tokenized Stock

Use Cases

Get Started

Official Resources