Developers

Run a Node

Anyone can run a StonkBrokerChain node. Because every transaction batch is posted to Robinhood Chain, a node can reconstruct and verify the entire chain from parent-chain data — you do not have to trust the public RPC.

Requirements

Software	Arbitrum Nitro node (Docker image)
CPU / RAM	4+ cores, 16 GB RAM
Disk	NVMe SSD; size with chain growth
Parent RPC	A reliable Robinhood Chain RPC endpoint
Ports	8547 (HTTP), 8548 (WS)

Run it

docker run --rm -it \
  -v /data/stonkbrokerchain:/home/user/.arbitrum \
  -p 8547:8547 -p 8548:8548 \
  offchainlabs/nitro-node:latest \
  --parent-chain.connection.url=https://rpc.mainnet.chain.robinhood.com \
  --chain.info-json="$(cat chain-info.json)" \
  --http.addr=0.0.0.0 --http.port=8547 \
  --http.api=net,web3,eth,arb \
  --ws.addr=0.0.0.0 --ws.port=8548

chain-info.json

Nitro needs a chain-info file describing the rollup: chain ID, parent chain ID, and the rollup contract addresses. It is published alongside the network configuration.

Pending

The canonical chain-info.json for StonkBrokerChain is published with the contract addresses at launch. Do not hand-assemble one from third-party sources.

Verify your node

curl -s -X POST http://localhost:8547 \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Operating notes

A full node is read-only — it does not sequence transactions or post assertions. Transactions you submit are forwarded to the sequencer.
Keep the parent-chain RPC healthy: if it lags, your node lags with it.
Archive mode (--execution.caching.archive) is required for historical state queries and most indexers.