op-node's default engine-API RPC timeout is short; on nodes whose EL responds
slowly to engine_newPayload/forkChoiceUpdated (e.g. boba-mainnet op-reth pruned
during catch-up) op-node times out driving the EL and the execution head freezes
while op-node keeps deriving from L1. Raising the engine RPC timeout to 120s
prevents this class of stall fleet-wide.
Regenerated from env/op/node.env: adds the env var to every op-node service
(116 geth + 40 reth + 22 erigon composes); additions only, no other changes.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Katana is not in the OP Stack superchain registry, so it needs
custom genesis.json and rollup.json files instead of the built-in
network name. Follows the same pattern as superseed-mainnet.
Changes:
- Remove GETH_OP_NETWORK env var
- Add genesis init in entrypoint (checks if /data/geth exists)
- Add --networkid=747474
- Mount op/katana/mainnet as /config in both geth and op-node
- Replace OP_NODE_NETWORK with OP_NODE_ROLLUP_CONFIG
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
