TECHNICAL REFERENCE
Robinhood Chain Dedicated Node - technical reference
Technical context for full-node and archive-node requirements on Robinhood Chain. The active Supanode Robinhood catalog contains RPC/WebSocket and Historical Indexer.
View active Robinhood products- Full nodes and archive nodes serve different historical-state requirements
- Ethereum JSON-RPC and WebSocket are the standard client interfaces
- Existing EVM clients include ethers, viem and web3.js
- Region, isolation and expected load are sizing inputs
- Scope
- Technical reference; not an active catalog product
- Chain
- Ethereum-compatible Arbitrum Layer 2; chain ID 4663; ETH gas
- Node concepts
- full-node current state; archive-node historical state
- Interfaces
- Ethereum JSON-RPC and WebSocket
How do full-node and archive-node requirements differ?
A full node serves current state and retained recent records. Archive state is needed for state queries at arbitrary older blocks, such as historical balances or contract storage. Specify the state history and methods your workload needs.
How do I discuss individual infrastructure requirements?
Describe the required state history, methods, region, isolation and expected load to Supanode. Availability, any partner, price, SLA and timing require separate confirmation. Current RPC/WebSocket and Indexer offers remain on the Robinhood pricing page.
Discuss requirements
Describe the interface, data history, region and expected load. Any individual infrastructure arrangement and its terms require separate confirmation.