Optimism’s 22 October op-node v1.19.11 release is strongly recommended for all operators, combining certificate-security changes with sequencer and startup repairs.

Origin drift affects slower L2 chains

The notes describe a bug on chains whose L2 block time exceeds half the L1 block time. A 10-second chain could lag L1 by about 30 minutes, delaying deposits, leaving fee parameters stale and producing many single-block batches. The fix keeps the sequencer’s L1 origin current; shorter-block-time chains are unaffected.

Compatibility and trust changes

Beacon configuration now accepts SLOT_DURATION_MS with SECONDS_PER_SLOT as fallback. Startup also tolerates a pruned L1 genesis block when the client returns error 4444, skipping that validity check with a warning.

The image uses Go 1.26.10 and removes compromised eMudhra roots from its trust store. The release incorporates v1.19.10 changes, which were not separately published.

NetNapz assessment

Operators should distinguish a broadly recommended security upgrade from a sequencer repair whose impact depends on chain timing. A release tag alone cannot establish that any particular network experienced delayed deposits or completed an upgrade.

This is separate from the recently covered Kona-Host release: op-node handles a different part of the stack. Deployment verification requires checking the actual running version, client configuration and chain behaviour. No adoption, performance measurement or OP token-price effect is asserted here.

Sources and scope

Official op-node v1.19.11 release notes. Reported effects are the maintainers’ description, not NetNapz benchmark results.