op-node/v1.16.12

This release is optional, however we recommend updating as it includes stability fixes.

⚠️ Req/Res CL P2P Sync — By Default Is Disabled

As previously communicated, we are deprecating the Req/Res CL P2P sync protocol in op-node.

--syncmode.req-resp flag now defaults to false, meaning Req/Res CL P2P sync is disabled by default.

Operators that rely on Req/Resp sync should explicitly set the flag to true and also update their infrastructure with a healthy EL p2p network.

🤝 The corresponding op-geth version is v1.101702.1.

What's Changed in op-node/v1.16.12

• op-node: disable Req/Resp p2p sync by default (--syncmode.req-resp=false). Operators that rely on Req/Resp sync should explicitly set the flag to true (#18088)
• all: upgrade the bundled op-geth dependency for this release candidate (#19844)
• supernode: use denylist output when computing OptimisticOutputRoot, improving optimistic output behavior around invalidated blocks (#19880)
• op-service / flashblocks: refactor flashblocks coverage and fix a shutdown race in the flashblock client (#19942,
  #19950)
• feat(nuts): add update-nuts and verify-nuts commands for bundle snapshotting and provenance verification (#19463)
• fault proof test infra: migrate end-to-end fault proof coverage from CANNON to CANNON_KONA (#19791)
• contracts / dev tooling: remove legacy OPCMv1 Solidity paths and align related deployer/devstack code with OPCMv2-only flows (#19795)

Full Changelog: op-node/v1.16.11...op-node/v1.16.12

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.12

op-batcher/v1.16.7

This release is optional.

What's Changed in op-batcher/v1.16.7

• all: upgrade op-geth, including shared tx-submission compatibility updates used by the batcher (#19844)
• chore(deps): bump op-geth again to v1.101702.1-rc.1 for this release candidate (#19992)
• chore(deps): bump google.golang.org/grpc to v1.79.3 (#19749)

Full Changelog: op-batcher/v1.16.6...op-batcher/v1.16.7

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.16.7

kona-node/v1.2.15

This is a recommended release containing correctness and stability fixes for kona-node.

What's Changed in kona-node/v1.2.15

• fix(kona/protocol): add bounds checks in read_tx_data for truncated and oversized payloads, preventing malformed payload panics and aligning behavior with op-node
  (#19904)
• fix(kona/derive): reset the indexed traversal pipeline on Holocene activation so interop clients apply required system config updates correctly (#19905)
• fix(kona-node): handle a missing L1 origin block in the sequencer by recovering with an engine reset instead of panicking (#19945)
• fix(kona): use deterministic BTreeMap JSON serialization in the interop host to avoid cross-process divergence in serialized preimages (#19906)
• fix(kona): improve interop consolidation by sending the L2Transactions hint before trie walks, skipping re-validation of deposit-only replacement blocks, and removing an obsolete replacement deposit transaction
  (#19850, #19890, #19894)
• feat!(rust): upgrade core Rust dependencies, including alloy-evm and reth, for the kona workspace (#19854)
• refactor(kona): remove native rollup-boost support from kona-node; operators that rely on rollup-boost should run it as a standalone sidecar and point kona-node’s L2 engine URL at it
  (#19900)
• fix(kona-proof-interop): improve rollup config warnings to report only missing chain IDs (#19729)

Full Changelog: kona-node/v1.2.14...kona-node/v1.2.15

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/kona-node:v1.2.15

op-reth/v1.11.5

What's Changed in op-reth/v1.11.5

• fix(proofs-exex): error if state unavailable instead of falling back to historical provider by @dhyaniarun1993 in #19855
• fix(op-alloy): resolve NetworkWallet<Optimism> conflict with alloy 1.8 by @suchapalaver in #19756
• feat(op-reth): Drop interop transactions after reorg by @wwared in #19814

New Contributors

• @suchapalaver made their first contribution in #19756

Full Changelog: op-reth/v1.11.4-rc.5...op-reth/v1.11.5

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-reth:v1.11.5

op-node/v1.16.11

This release is optional, however we recommend updating as it includes stability fixes.

The corresponding op-geth version is v1.101701.0.

What's Changed in op-node/v1.16.11

• fix(op-node): guard SafeDB methods against use after Close by @ajsutton in #19824
• feat(op-node): batch safe-head FCU calls to one per derived L1 block by @sebastianst in #19638

Full Changelog: op-node/v1.16.10...op-node/v1.16.11

Docker image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.11

op-deployer/v0.6.0

Overview

op-deployer/v0.6.0 supports deploying, upgrading to, and producing calldata for op-contracts/v6.0.0 (u18). This release supports all of the following:

op-deployer bootstrap [options] // deploy superchain|implementations contracts at op-contracts/v4.1.0
op-deployer apply [options] // deploy new OPChain contracts at op-contracts/4.1.0
op-deployer upgrade v2.0.0 // upgrade from op-contracts/v1.8.0 -> op-contracts/v2.0.0
op-deployer upgrade v3.0.0 // upgrade from op-contracts/v2.0.0 -> op-contracts/v3.0.0
op-deployer upgrade v4.0.0 // upgrade from op-contracts/v3.0.0 -> op-contracts/v4.0.0 (not recommended, should upgrade straight to op-contracts/v4.1.0 instead)
op-deployer upgrade v4.1.0 // upgrade from op-contracts/v3.0.0|v4.0.0 -> op-contracts/v4.1.0
op-deployer upgrade v5.0.0 // upgrade from op-contracts/v4.1.0 -> op-contracts/v5.0.0
op-deployer upgrade v6.0.0 // upgrade from op-contracts/v5.0.0 -> op-contracts/v6.0.0

All other commands are only guaranteed to work with op-contracts/v6.0.0. So you must upgrade to op-contracts/v6.0.0 before doing the following:

op-deployer manage [options]
op-deployer verify [options]

Details

Additional changes outside of op-contracts/v6.0.0 support include:

• opDeployerVersion is now recorded in the intent and state files
• ongoing OPCMv2 work
• fixed Windows builds

kona-node/v1.2.14

What's Changed in kona-node/v1.2.14

• fix(kona/derive): use walked-back system config on pipeline reset by @sebastianst in #19792
• fix(op-alloy): resolve NetworkWallet<Optimism> conflict with alloy 1.8 by @suchapalaver in #19756
• feat(op-reth): Drop interop transactions after reorg by @wwared in #19814
• feat(kona-host): add directory-based kv store compatible with op-program by @ajsutton in #19803
• chore(kona): remove dead interop_message_expiry_window from RollupConfig by @digorithm in #19810
• fix(kona): use configurable message expiry window in MessageGraph by @digorithm in #19765
• fix(kona/proof): several fixes to kona-proof. by @theochap in #19775
• chore(rust): misc clippy fixes on crates by @mablr in #19736
• ci: use cargo-auditable for Rust image builds by @falcorocks in #19770
• feat(op-alloy-evm): add OpEvm::into_inner method by @mablr in #19735
• feat(op-devstack): respect DEVSTACK_L2EL_KIND and DEVSTACK_L2CL_KIND in all single-chain runtimes by @joshklop in #19653

Operator note: interop_message_expiry_window was removed from RollupConfig. Any existing serialized configs or fixtures that still include this field may fail to deserialize and should be updated before rollout.

New Contributors

• @suchapalaver made their first contribution in #19756

Full Changelog: kona-node/v1.2.13...kona-node/v1.2.14

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/kona-node:v1.2.14

op-proposer/v1.16.2

This release is optional; however, we recommend updating as it includes a Go version upgrade addressing security fixes, along with enhanced container image hardening.

What's Changed in op-proposer/v1.16.2

• chore: bump Go to 1.24.13 and switch to DHI builder images by @falcorocks in #19666
• all: update op-geth by @wwared in #19643
• all: upgrade op-geth by @joshklop in #19433

Full Changelog: op-proposer/v1.16.1...op-proposer/v1.16.2

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-proposer:v1.16.2

op-node/v1.16.10

This release is optional; however, we recommend updating as it includes a Go version upgrade addressing security fixes, along with enhanced container image hardening.

🤝 The corresponding op-geth version is v1.101701.0.

What's Changed in op-node/v1.16.10

• interop: deploy and fund ETH bridge contracts at activation by @karlfloersch in #19648
• op-node: Drop Unsafe Payloads Denied by Superauthority by @axelKingsley in #19288
• chore: bump Go to 1.24.13 and switch to DHI builder images by @falcorocks in #19666
• fix(op-node): add SetCodeTxType check to span batch validation by @Theburaka in #19150

Full Changelog: op-node/v1.16.9...op-node/v1.16.10

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.10

op-conductor/v0.9.3

This release is optional; however, we recommend updating as it includes a Go version upgrade addressing security fixes, along with enhanced container image hardening.

What's Changed in op-conductor/v0.9.3

• feat(conductor): add demote-voter to conductor rpc by @KyrinCode in #18700
• chore: bump Go to 1.24.13 and switch to DHI builder images by @falcorocks in #19666
• all: update op-geth by @wwared in #19643
• all: upgrade op-geth by @joshklop in #19433
• all: update op-geth by @joshklop in #19414

New Contributors

• @KyrinCode made their first contribution in #18700

Full Changelog: op-conductor/v0.9.2...op-conductor/v0.9.3

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-conductor:v0.9.3