You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
op-acceptance-tests: run TestELSyncSafeRetractedByOffset against kona-node #23828
TestELSyncSafeRetractedByOffset is skipped when the acceptance suite runs against kona-node (sysgo.SkipOnKonaNode(t, "kona-node does not support OffsetELSafe"), added in #23827).
The test configures the verifier with OffsetELSafe, which maps to op-node's --syncmode.offset-el-safe. After EL sync completes, op-node holds the safe and finalized heads that far behind the synced tip. The flag defaults to 12h, matching the OP Mainnet sequencing window. kona-node has no equivalent option, and devstack rejects the setting for kona-node with unsupported L2CL option for kona-node (op-devstack/sysgo/l2_cl_kona_config.go).
Until #23827, the test was skipped on op-reth, and op-geth skips every chain that activates Karst. So this gap was never reached in any CI configuration.
Required work
Implement the EL-sync safe/finalized offset in kona-node with the same semantics and default as op-node. Wire it through the devstack kona-node config, then remove the kona-node skip.
Acceptance criteria
kona-node supports an EL-sync safe/finalized offset matching op-node's --syncmode.offset-el-safe semantics and default.
op-devstack/sysgo/l2_cl_kona_config.go accepts OffsetELSafe for kona-node.
The kona-node skip is removed and TestELSyncSafeRetractedByOffset passes against kona-node.
Activity
op-acceptance-tests: link kona-node OffsetELSafe skip to #23828
op-acceptance-tests: link kona-node OffsetELSafe skip to #23828
op-acceptance-tests: run TestELSyncSafeRetractedByOffset on kona-node