Robinhood chain

Robinhood Chain

Use this skill as a routing guide for Robinhood Chain work: mainnet/testnet configuration, RPC discovery, ChainList, Blockscout, Stock Tokens, bridges, oracles, account abstraction, connected services, node operation, wallet setup, and app or contract integration. Do not teach generic Solidity, EVM, ERC-20, Hardhat, Foundry, viem, ethers, or wallet basics unless the user asks for them; Robinhood Chain is EVM-compatible, so standard EVM knowledge applies.

Source Order

Prefer live, source-linked data over memory. Robinhood Chain is new enough that provider support and token lists can change quickly.

1. Treat Robinhood Chain docs as canonical for chain IDs, public endpoints, bridges, contracts, Stock Tokens, oracles, account abstraction, node operation, notices, and terms.
2. Use ChainList mainnet, ChainList testnet, and the ChainList API to discover current wallet/RPC metadata.
3. Use provider/vendor docs to confirm connected-service support such as RPCs, subgraphs, indexing, data APIs, bridges, AA, wallet infra, analytics, compliance, DEX/liquidity, and oracles. Do not treat the seed list in chain-resources.md as exhaustive.
4. If data conflicts, prefer Robinhood docs for Robinhood-operated endpoints and chain identity, then the vendor's own docs for that vendor's support.

Stable Network Facts

Verify before production use, but these are the current official basics:

Network	Chain ID	Hex	Gas	Public RPC	Explorer
Robinhood Chain	4663	0x1237	ETH	https://rpc.mainnet.chain.robinhood.com	https://robinhoodchain.blockscout.com
Robinhood Chain Testnet	46630	0xb626	ETH	https://rpc.testnet.chain.robinhood.com	https://explorer.testnet.chain.robinhood.com

Native currency is Ether: { name: "Ether", symbol: "ETH", decimals: 18 }. The official testnet faucet is https://faucet.testnet.chain.robinhood.com, but check live availability before promising access.

Do not use third-party references that claim testnet chain ID 46646 / 0xb636; the official testnet chain ID is 46630 / 0xb626. Confirm any endpoint with eth_chainId before use.

Robinhood public RPCs are rate-limited and not recommended for production. ChainList is wallet/RPC discovery, not a production SLA source. For production traffic, use a provider endpoint, verify eth_chainId, check provider status/limits, and use archive endpoints for historical reads or indexing.

Robinhood-Specific Checks

When helping with contracts or apps, check Robinhood-specific behavior before writing code:

• Arbitrum Nitro L2 differences: block.number, blockhash, block.coinbase, randomness, gas accounting, address aliasing, precompiles, transaction screening, contract-size limits, and first-come first-served ordering differ from Ethereum mainnet. Read Differences from Ethereum, Gas & Fees, and Transaction Finality.
• Stock Tokens: use Stock Tokens, Building with Stock Tokens, and Token Contracts. Note product/legal restrictions, canonical-address-only identity, 18 decimals, ERC-8056 scaled UI amounts, uiMultiplier(), pending multiplier fields, and indexer impact. Do not copy token address tables into generated docs; link to the current official page.
• Price feeds: use Oracles & Price Feeds and Chainlink's current Robinhood feed pages. Stock Token feeds already include the multiplier; do not multiply feed price by uiMultiplier() again. Check sequencer uptime, feed staleness, decimals, 24/5 updates, and oraclePaused() behavior before rendering prices.
• Cross-chain work: use Bridging, Cross-Chain Messaging, and Protocol Contracts. Programmatic Arbitrum SDK work must register Robinhood Chain as a custom network; L1 -> L2 uses retryable tickets via Delayed Inbox, L2 -> L1 requires Outbox execution after the challenge period, and L1 contract senders require alias handling.
• Account abstraction: use Account Abstraction for ERC-4337, EIP-7702, Alchemy, ZeroDev, Privy, bundler URL, and entry point addresses.
• Nodes and upgrades: use Run a full node, Notices & Upgrades, and the status page. Node work needs the Robinhood genesis config, L1 execution RPC, L1 beacon endpoint for blobs, large local NVMe storage, wss:// feed URLs, and current Nitro/ArbOS compatibility; validator operation is permissioned.
• Terms and public services: use Terms of Service when discussing public RPC, sequencer, snapshots, or testnet. Public services have no production uptime/data-completeness guarantee, may be throttled or changed, and testnet tokens have no value.

Connected Services

When the user asks whether a service works on Robinhood Chain, do current research. Examples include subgraphs, but also RPC providers, archive nodes, token APIs, data warehouses, bridges, oracles, wallets, AA/bundlers/paymasters, compliance tools, custody, explorers, DEXs, catalogs, and analytics.

Load chain-resources.md when you need a seed map of known sources and provider pages. Then verify current support with the service's own docs or support page before giving a definitive answer.

Use a support verdict, not vibes: Supported, Testnet-only, Partial, No published support found, or Unknown. Include the product surface, mainnet/testnet distinction, vendor source URL, and access date. Partial means only some surfaces, networks, APIs, or access tiers are supported. No published support found means you checked the vendor's published docs/support pages and found no support claim. Unknown means evidence is insufficient, inaccessible, or conflicting. EVM compatibility alone is not proof that a third-party service supports Robinhood Chain.

Practical Workflow

For any Robinhood Chain task:

1. Identify whether the user targets mainnet or testnet.
2. Pull current network/provider facts from Robinhood docs and ChainList if the answer depends on live endpoints.
3. Route Robinhood-specific logic to the docs linked above.
4. Use normal EVM tooling for the actual implementation once the Robinhood-specific config is known.
5. Cite sources and avoid pasting large copied tables from docs.