Summary
In v0.16.0, .env.sepolia sets BASE_NODE_L2_ENGINE_RPC=http://execution:8551, while .env.mainnet sets it to ws://execution:8551. The two should be consistent, and ws:// is the documented setup.
What I found
.env.mainnet:
BASE_NODE_L2_ENGINE_RPC=ws://execution:8551
.env.sepolia:
BASE_NODE_L2_ENGINE_RPC=http://execution:8551
The release that introduced WebSocket support for the engine RPC explicitly mentioned: "Fixes a small bug in base-consensus where the L2_ENGINE_RPC_URL didn't support websocket urls."
Expected behavior
Both .env.mainnet and .env.sepolia should configure the engine RPC the same way. Based on prior releases and the consensus entrypoint behavior, ws://execution:8551 is the intended value.
Suggested fix
Change .env.sepolia line 22 to:
BASE_NODE_L2_ENGINE_RPC=ws://execution:8551
Impact
Sepolia operators following the default config use a different transport than mainnet operators, which can cause subtle peering/engine reliability differences and inconsistent ops behavior.
Summary
In v0.16.0, .env.sepolia sets
BASE_NODE_L2_ENGINE_RPC=http://execution:8551, while .env.mainnet sets it tows://execution:8551. The two should be consistent, andws://is the documented setup.What I found
.env.mainnet:
BASE_NODE_L2_ENGINE_RPC=ws://execution:8551.env.sepolia:
BASE_NODE_L2_ENGINE_RPC=http://execution:8551The release that introduced WebSocket support for the engine RPC explicitly mentioned: "Fixes a small bug in base-consensus where the L2_ENGINE_RPC_URL didn't support websocket urls."
Expected behavior
Both .env.mainnet and .env.sepolia should configure the engine RPC the same way. Based on prior releases and the consensus entrypoint behavior,
ws://execution:8551is the intended value.Suggested fix
Change .env.sepolia line 22 to:
BASE_NODE_L2_ENGINE_RPC=ws://execution:8551Impact
Sepolia operators following the default config use a different transport than mainnet operators, which can cause subtle peering/engine reliability differences and inconsistent ops behavior.