Releases: ethereum-optimism/optimism
op-deployer/v0.2.4
op-deployer/v0.3.3
op-batcher/v1.14.0
This release contains:
- a transaction rebroadcasting feature which helps batcher transactions get included with less delay and lower cost.
- changes in the way the batcher interprets the sync status reported by the
op-node
- other small bugfixes
Warning
Operators should upgrade sequencers to at least op-node/v1.13.4 when updating to this version of the batcher. See #16413.
Warning
The transaction rebroadcasting feature is enabled by default. To disable this feature, set TXMGR_REBROADCAST_INTERVAL
to 0
. See #16310.
Warning
Rebroadcasting transactions can make memory spikes more likely. We recommend at least 4GB of memory for production deployments.
What's Changed
- fix(txmgr): Ignore certain errors on tx resubmission by @BrianBland in #16566
- txmgr and op-node p2p key management: enhance error check by @zhiqiangxu in #16542
- op-service,op-supervisor: Correctly detect ethereum.NotFound in RPCs by @sebastianst in #16555
- feat(txmgr / batcher): Rebroadcast transactions without bumping fees by @BrianBland in #16310
- op-batcher: remove
preferLocalSafeL2
flag by @geoknee in #16413 - op-batcher: more robust detection of not-ready
syncStatus
by @geoknee in #16298
Full Changelog: op-batcher/v1.13.2...op-batcher/v1.14.0
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.14.0
op-deployer/v0.4.0-rc.5
op-node/v1.13.4
This is a recommended release for all node operators and contains bugfixes and optimizations.
In particular it fixes a bug where the sequencer's sync status could become inconsistent, which would overwhelm the batcher (depending on how it is configured). See #16296.
What's Changed
- op-node: Handle duplicate outgoing supervisor events by @sebastianst in #16441
- op-node/rollup/status: ensure
localSafeL2
is never behindsafeL2
afterForkchoiceUpdateEvent
by @geoknee in #16296 - rollup: Set the interop time when loading from superchain-registry by @ajsutton in #16409
- op-node/rollup: binary search for latest valid local unsafe block by @nonsense in #16276
- op-node: Search valid unsafe head backwards by @sebastianst in #16312
- op-node: derivation: warn about inconsistent l1 traversal by @protolambda in #16285
- op-node: Fix pipeline transformer by @sebastianst in #16282
- op-node/rollup/interop: do not ignore local unsafe reset by @nonsense in #16052
- op-node: managed mode pre-interop by @protolambda in #16071
- op-node: fix log level of p2p peering by @protolambda in #16212
- op-supervisor,op-node: Handle non-genesis Interop by @sebastianst in #16008
- op-node: Only deploy CrossL2Inbox if there is more than one chain in the dependency set by @ajsutton in #16042
- op-service: ref-metrics safe for concurrent use by @protolambda in #16159
- op-node: Add RPC api to retrieve the current dependency set config by @ajsutton in #16117
- events: Add Event Dequeued Metric by @axelKingsley in #16133
- op-node: Add dependency set flag by @ajsutton in #16094
- op-node: fix reset-confirmed metadata by @protolambda in #15588
- op-node: remove incomplete interop StandardMode by @protolambda in #15996
- op-node: disable per-topic peer scoring entirely by @geoknee in #15719
Full Changelog: op-node/v1.13.3...op-node/v1.13.4
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.4
op-deployer/v0.4.0-rc.4
op-challenger/v1.5.1
Overview
This is a minor release of op-challenger that includes important bug fixes. It is a required upgrade for all users.
What's Changed
- Bug fix for Go 1.23 support: Return EAGAIN error when writing to an eventfd file descriptor and fix registers used in the case of errors.
Full Changelog: op-challenger/v1.5.0...op-challenger/v1.5.1
🚢 Docker Image:
op-contracts/v4.0.0-rc.8
This is the op-contracts release intended for the forthcoming Upgrade 16 protocol upgrade.
For contract versions and implementation addresses in this release; please refer to the superchain-registry:
The associated governance proposal can be found here.
Deployment and upgrade operations should be executed using the associated op-deployer release (link to be updated after this PR is merged)
op-conductor/v0.7.0
What's Changed
- add conductor support for flashblocks websocket by @angel-ding-cb in #15681
New Contributors
Full Changelog: op-conductor/v0.6.0-rc.1...op-conductor/v0.7.0
op-challenger/v1.5.0
Overview
This release of op-challenger
adds support for a new version of Cannon that is compatible with Go 1.23. It is a required upgrade for all users.
What's Changed
- Cannon supports Go 1.23 by implementing noop syscalls
eventfd2
andmprotect
. - Cannon implements
dclo
/dclz
instructions which adds support for kona compiled down to mips64r1.
Full Changelog: op-challenger/v1.4.0...op-challenger/v1.5.0
🚢 Docker Image: