op-reth (execution client, JSON-RPC and WebSocket) and op-node (consensus client, derives the chain from L1 and peers over libp2p). This section is for teams that want their own RPC endpoint, an indexer or explorer backend, or a private node instead of the public RPC.
Available on Whitechain Sepolia and Whitechain Mainnet.
How it works
The Whitechain sequencer is closed and is not reachable from the public internet. Your node never needs access to it. Instead, the node:- Reads L1 batches from your own Ethereum L1 RPC and Beacon endpoints.
- Pulls unsafe blocks from the network over libp2p.
- Forwards
eth_sendRawTransactioncalls to the public Whitechain RPC, which routes them to the sequencer.
This stack holds no project-side private keys. The sequencer, batcher, proposer, and challenger keys stay on the Whitechain side. You operate a follow-only node.
Concepts: storage vs. sync method
A node is defined by two independent choices. Each node profile is a fixed combination of them. Storage: how much stateop-reth keeps:
- Pruned (
--full): keeps only recent state, prunes history. Smallest disk footprint. Serves a complete public RPC for current data. - Archive (no
--full): keeps the full historical state. Largest disk footprint. Required for historical tracing andeth_callat old blocks.
op-reth obtains that state:
- consensus-layer (the
op-nodedefault):op-nodederives the chain from L1 and feeds blocks toop-rethone by one;op-rethre-executes every transaction from genesis. No EL P2P peer needed, but the initial sync is long on a chain with history behind it. - execution-layer (
--syncmode=execution-layer, “snap”):op-nodeonly drives the head;op-rethsnap-syncs the state directly from a trusted reth peer over EL P2P. Fast, but it requires a reachable seed peer (WHITECHAIN_RETH_TRUSTED_PEERS). Snap sync cannot build archive state, only pruned.
Node profiles
The stack ships three profiles. Pick one withPROFILE=<profile> or a per-profile make target.
full-snap-node is the recommended default: pruned execution state, bootstrapped by snap-syncing from a trusted reth peer (WHITECHAIN_RETH_TRUSTED_PEERS) instead of re-executing the chain. Use it when you have a reachable seed reth enode. full-node keeps the same pruned state but syncs in consensus-layer mode, re-executing the chain from L1. Use it when you have no trusted peer to snap-sync from, and expect a long initial sync on a chain with history behind it. archive-node keeps the full historical state, so it is the profile that can answer historical eth_call, debug_traceTransaction, and log-heavy indexing. Archive cannot snap-sync, so it always re-executes from L1, which makes its initial sync the longest of the three. It needs the most disk and RAM.
Whitechain publishes full (non-archive)
op-reth snapshots, so a full-node can start from a snapshot instead of syncing from genesis. See Restore from a published snapshot. archive-node always re-executes from L1.Available RPC namespaces
op-reth namespaces come from two .env variables that apply to all three profiles, and the two ports are configured independently:
archive-node is no exception: by default it serves the same read-only set as the pruned profiles. debug, trace, txpool, and reth are an explicit opt-in through HTTP_API or WS_API, and only archive-node holds the history those methods read. Enable them only behind a proxy that allowlists methods and rate-limits clients. See RPC namespaces.
op-reth exposes no admin namespace on any profile.
op-node exposes an RPC on port 9545, bound to loopback (127.0.0.1) only on every profile, reachable for local monitoring on the host, never from the network:
The
admin namespace is not enabled on op-node either, so no profile exposes administrative or state-mutating methods.
Sending transactions
Applications submit transactions to your localop-reth HTTP port. The node forwards them to WHITECHAIN_PUBLIC_RPC, which routes them to the sequencer. You need no direct access to the sequencer.
If you restart your node, in-flight transactions remain in the public RPC mempool, not in your local node.
What this node does not provide
This is a follow-only RPC node. It does not include block builder or sequencer roles, the batcher, proposer, or challenger, or the Flashblocks pre-confirmation stream. Flashblocks are not enabled on Whitechain Mainnet or Whitechain Sepolia, so there is no pre-confirmation stream to subscribe to today. When the rollout lands, the stream stays separate from the public RPC and thepublic-rpc-node stack does not carry it. See Flashblocks.

