.env variables, network ports, and data paths used by the Whitechain public-rpc-node stack.
Required variables
The
full-snap-node profile also requires WHITECHAIN_RETH_TRUSTED_PEERS, a trusted reth enode to snap-sync from, in the form enode://<pubkey>@<ip>:30303.
Optional variables
Optional variables
Optional variables
Archive-only RPC limits
Archive-only RPC limits
Archive-only RPC limits
Network ports
Only one profile runs at a time, so all profiles share the same host ports. Each is remappable through the env var in parentheses.
The Engine API (
8551) stays on the internal Compose network and is never published. op-node RPC (9545) is bound to loopback only on every profile, so it is reachable for local monitoring on the host but never from the network. The EL P2P port is only mapped for full-snap-node, which needs it to snap-sync state over devp2p from WHITECHAIN_RETH_TRUSTED_PEERS. Its mapping is commented out in docker-compose.yml for full-node and archive-node; those profiles sync over L1 derivation and libp2p only and never use EL P2P. To run two profiles side by side on one host, override one profile’s ports in .env.
Data layout
Each profile keeps its data in its own subtree, so profiles never clash:data/<profile>/op-reth/.

