Overview
Important
This is a recommended release for op-supernode operators. It contains two fixes to how the safe head is tracked after an L1 reorg on chains with interop enabled.
Other changes
Safe head
- After an L1 reorg moves a chain's local-safe head below its last cross-verified block, the
safetag reported to the execution client and inoptimism_syncStatusnow holds at the last verified block instead of advancing onto blocks that have not been cross-verified. It also holds after a resync until local-safe catches up with the verified head. Theop_node_supernode_super_authority_reorg_signals_totalmetric gains areason="ahead_of_local_safe"label value for this case (#22982) - With
--safedb.pathset, a derivation reset now truncates the safe head database to the local-safe head rather than the cross-safe head. Previously, whenever cross-safe lagged local-safe at reset, the entries in between were deleted and never re-recorded, leaving a gap that madesuperroot_atTimestampandoptimism_safeHeadAtL1Blockanswer with a later L1 block than the correct one, without any error. New gaps no longer form, but an existing gap is not repaired: rebuild the safe head database to clear it (#22997)
Metrics
- Virtual nodes now record
op_node_supernode_unsafe_payload_arrival_delay_seconds, the delay between a block's timestamp and its arrival over p2p (#22967)
Full Changelog: op-supernode/v1.0.3...op-supernode/v1.0.4
🚢 Docker Image: