Robinhood Chain RPC for onchain finance

Yes. Robinhood Chain is fully EVM-compatible. Solidity and Vyper contracts deploy without modification, and it works with any standard Ethereum JSON-RPC clients and tooling. Some behaviors differ from Ethereum mainnet. Blocks are produced about every 100 milliseconds, and the sequencer orders transactions by the time of arrival, so paying a higher fee will not move a transaction ahead in the queue. The sequencer also applies compliance screening at inclusion, so a transaction involving a sanctioned address is never processed.

GetBlock provides managed access to Robinhood nodes via HTTPS and WebSocket endpoints. Instead of running their own Robinhood Chain node infrastructure, developers can send JSON-RPC requests to GetBlock's endpoints. Access is available on free, shared, Limitless and dedicated plans.

The chain is EVM-compatible, so it works with any wallet that supports custom Ethereum-compatible networks, including MetaMask and the native Robinhood Wallet. If your wallet doesn't detect it automatically, add the Robinhood Chain to a wallet by Chain ID with a correct RPC URL and ETH as the currency symbol.

Robinhood RPC nodes can submit transactions and access blockchain data (account balances, nonces, contract code, blocks, transactions, receipts, and event logs). For RWA applications, that includes ERC-20 balances and transfers for Stock Tokens, their onchain price feed values, and the ERC-8056 uiMultiplier() value for dividends and splits. An archive node is required for historical state at past blocks.

You can connect to Robinhood Chain using its JSON-RPC endpoint. Get an RPC URL and point any EVM client at it over HTTPS, or over WebSocket for subscriptions. Configure the client with Chain ID 4663 (0x1237) for mainnet. For testing, use the testnet Chain ID 46630 (0xb626), a testnet RPC endpoint, and test ETH available from the network's faucet. The free public RPC endpoint is suitable for testing and light usage. If you're building a production dApp or need high throughput, Robinhood recommends using a dedicated RPC provider.

The JSON-RPC method set is the standard Ethereum one: eth_call and eth_getBalance for reads, eth_getLogs for event queries, eth_getBlockByNumber and eth_getTransactionReceipt for block and transaction data, and eth_sendRawTransaction for submitting signed transactions. Some differences from Ethereum: eth_estimateGas shows both the L2 execution fee and the L1 data fee, and anything relying on block.number should instead call arbBlockNumber().

Yes. WebSocket endpoints support eth_subscribe, so applications can stream new block headers, pending transactions, and filtered event logs. Robinhood Chain also publishes a sequencer feed that broadcasts transactions as the sequencer orders them, ahead of block publication – useful for latency-sensitive trading and indexing. For historical backfills, an archive endpoint is the right tool.

Robinhood Chain uses numeric EVM Chain IDs: 4663 (0x1237) for mainnet and 46630 (0xb626) for the public testnet. The currency symbol is ETH on both networks. Configure the Chain ID in your wallet, deployment framework, or client library exactly as you would for any other EVM network.