Releases: ethereum-optimism/optimism
op-deployer/v0.0.7
op-deployer/v0.0.6
op-node v1.10.0 - Sepolia Holocene
Sepolia Holocene Release
❗ All node operators of Sepolia chains that follow the Sepolia Superchain must upgrade to this release of op-node and op-geth v1.101411.2.
The Sepolia Superchain activates Holocene on Tue Nov 26 15:00:00 UTC 2024
(unix ts 1732633200
). This comprises the op
, base
, mode
, metal
, and zora
Sepolia OP Stack chains.
What's Changed (op-node)
- holocene: load HoloceneTime from registry by @geoknee in #12890
- Prepare Holocene testnet & devnet release by @sebastianst in #12917
- adding conduit bootnodes by @sbvegan in #12534
- Update superchain-registry and op-geth to include metal-sepolia Holocene activation by @sebastianst in #12966
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.10.0
op-deployer/v0.0.5
op-deployer/v0.0.4
Changelog
- 7550853 Check
bcast.From
correctly (#12941) - fd1e062 Revert "feat: Isthmus Contracts (#12746)"git (#12870)
- 2c5f6ed feat(ct): DeployDelayedWETH script (#12662)
- 9e9effa feat: DeployDisputeGame script (#12641)
- dad1087 feat: Isthmus Contracts (#12746)
- f6810a4 feat: opcm mainnet deploy. (#12953)
- b5a2955 goreleaser: cleanup (#12856)
- 11843b4 op-deployer: Add deploy mips script (#12835)
- 1f335f1 op-deployer: Add support for Isthmus calls to OPCM (#12753)
- dec8c60 op-deployer: Add support for alt-DA deployments (#12798)
- 9bdcb02 op-deployer: Fix useInterop flag (#12813)
- 4e13b20 op-deployer: Reduce test code duplication, put test funcs first (#12751)
- f94151b op-deployer: Refactor semver inspector, add L2 genesis test (#12946)
- 50564d4 op-deployer: Support forking live chains (#12918)
- a68e3ef op-deployer: Support overriding proof parameters (#12732)
- cd2df97 op-deployer: Test mainnet deployment (#12958)
- caf63ce op-deployer: add 'inspect superchain-registry' subcommand (#12736)
- b46bffe op-deployer: use dev keys for vaults in new intent (#12679)
- 5e209a5 op-e2e: interop cross L2 inbox system test (#12754)
- 8f0a9b2 opcm-redesign: opcm targets a single release (#12851)
OP Contracts v1.8.0-rc.2
Overview
This release is suitable for the L1 contracts as part of the Holocene network upgrade.
Full Contract Set
A chain using this contracts release must be using the following contracts at the specified semvers.
The following contracts are included in this release:
- MIPS: 1.2.1
- SystemConfig: 2.3.0
- FaultDisputeGame: 1.3.1
- PermissionedDisputeGame: 1.3.1
Additional Information
There is no finalized v1.7.0
release. The release candidate for v1.7.0
was for generating L2 genesis.
op-stack v1.9.5 - Batcher Sequencer Throttling
❗ It is strongly recommended for all chain operators to upgrade to this release.
Highlights
Batcher Sequencer Throttling (ethereum-optimism/op-geth#421 #12735)
This release contains a new batcher-driven sequencer-throttling control loop. This is to avoid sudden spikes in L1 DA-usage consuming too much available gas and causing a backlog in batcher transactions. The batcher can throttle the sequencer’s data throughput instantly when it sees too much batcher data built up.
🎛️ There are two throttling knobs:
- transaction L1 data throttling, which skips individual transactions whose estimated compressed L1 DA usage goes over a certain threshold, and
- block L1 data throttling, which caps a block’s estimated total L1 DA usage and leads to not including transactions during block building that would move the block’s L1 DA usage past a certain threshold.
Upgrade path
This new feature is enabled by default and requires running op-geth version v1.101411.1
or later. It can be disabled by setting --throttle-interval
to 0
. The sequencer's op-geth node has to be updated first, before updating the batcher, so that the new required RPC is available at the time of the batcher restart.
op-conductor
It is required to upgrade to op-conductor/v0.2.0 if you are using conductor’s leader-aware rpc proxy feature. This conductor release includes support for the miner_setMaxDASize
op-geth rpc proxy.
Configuration
Batcher
The batcher can be configures with the following new flags and default parameters:
- interval at which throttling operations happen (besides when loading an L2 block in the batcher) via
--throttle-interval
:2s
(env varOP_BATCHER_THROTTLE_INTERVAL
)- This can be set to zero to completely disable this feature. Since it’s set to 2s by default, the feature is enabled by default.
- backlog of pending block bytes beyond which the batcher will enable throttling on the sequencer via
--throttle-threshold
:1_000_000
(batcher backlog of 1MB of data to batch)- env var
OP_BATCHER_THROTTLE_THRESHOLD
- env var
- individual tx size throttling via
--throttle-tx-size
:300
(estimated compressed bytes)- env var
OP_BATCHER_THROTTLE_TX_SIZE
- env var
- block size throttling via
--throttle-block-size
:21_000
(estimated total compressed bytes, at least 70 transactions per block of up to 300 compressed bytes each)- env var
OP_BATCHER_THROTTLE_BLOCK_SIZE
- env var
- block size throttling that’s always active via
--throttle-always-block-size
:130_000
- env var
OP_BATCHER_THROTTLE_ALWAYS_BLOCK_SIZE
- This block size limit is enforced on the sequencer at all times, even if there isn’t any backlog in the batcher. Normal network usage shouldn’t be impacted by this. This is to prevent a too fast build up of data to batch.
- env var
If the batcher at startup has throttling enabled and the sequencer’s op-geth node to which it’s talking hasn’t the miner_setMaxDASize
RPC enabled, it will fail with an error message like
lvl=warn msg="Served miner_setMaxDASize" reqid=1 duration=11.22µs err="the method miner_setMaxDASize does not exist/is not available"
In this case, make sure the miner
API namespace is enabled for the correct transport protocol (HTTP or WS), see next paragraph.
Sequencer
The new RPC miner_setMaxDASize
is available in op-geth since v1.101411.1
. It has to be enabled by adding the miner
namespace to the correct API flags, like
GETH_HTTP_API: web3,debug,eth,txpool,net,miner
GETH_WS_API: debug,eth,txpool,net,miner
It is recommended to add it to both, HTTP and WS.
Other
- A bug in the sequencer is fixed that may cause derivation to stall on flaky L1 connections (#12258).
- This release also contains many incremental changes regarding Holocene and Interop feature development.
What's Changed
- Interop: Update Inputs (rebased) by @axelKingsley in #12204
- [batcher] derive.ChannelOut factory by @mdehoog in #12344
- op-service: Add optional headers to the signer client by @trianglesphere in #12407
- [batcher] Cleanup batcher channel inclusion block logic by @mdehoog in #12363
- [batcher] Rename channel receiver by @mdehoog in #12453
- op-node/rollup/derive: Add Holocene Channel Assembler by @sebastianst in #12334
- op-node/rollup/sequencing: Fix temporary engine error handling by @sebastianst in #12258
- feat(op-batcher): wait for pre-genesis RPC request loop by @jsvisa in #12383
- op-node: Alphabetize CLI network lists by @mbaxter in #12522
- Holocene: initial op-node support for configurable eip-1559 params by @roberto-bayardo in #12497
- Holocene: SystemConfig contract changes for updating EIP-1559 params by @roberto-bayardo in #12498
- op-node/rollup/derive: Holocene Batch Stage by @sebastianst in #12417
- Holocene: e2e test for Holocene's configurable eip-1559 params by @roberto-bayardo in #12499
- rollup-client: Increase call timeouts in CI by @ajsutton in #12561
- op-service: Add omitempty to EIP1559Params by @mslipper in #12582
- chore(op-service): Add missing fields to blob API types by @clabby in #12602
- op-service/client: rm unnecessary type infer arguments by @jsvisa in #12651
- Interop: Fix DerivedFrom Client Signature by @axelKingsley in #12661
- op-node: disable finality based on local-safe when interop is active by @protolambda in #12690
- op-node/rollup/derive: Implement pipeline stage multiplexing by @sebastianst in #12506
- op-node/rollup: Implement Holocene invalid payload attributes handling by @sebastianst in #12621
- op-node/rollup: Promote all attributes to safe post-Holocene by @sebastianst in #12724
- Interop: Add error case for parent of start of database by @axelKingsley in #12818
- interop: Handle first L1 Parent Ref in CandidateCrossSafe by @axelKingsley in #12830
- interop: correct error in prior WithParent commit by @axelKingsley in #12832
- interop: Handle ErrParentToFirst from PreviousDerivedFrom by @axelKingsley in #12833
- op-batcher: Increase the pending_blocks metric when a channel times out by @geoknee in #12810
- op-batcher: control loop to throttle DA usage by @roberto-bayardo in #12735
- op-batcher: Enable throttling by default, shutdown on broken RPC by @sebastianst in #12840
- interop: Fix AtLeastAsSafe ; Geth Mempool Filter E2E Test by @axelKingsley in #12823
- [Batcher] Fix memory leak, reverse prepended blocks by @mdehoog in #12874
- op-conductor,op-node: allow system to select port, make op-node wait for conductor endpoint by @protolambda in #12863
New Contributors (full monorepo)
- @qizhou made their first contribution in #12310
- @gotzenx made their first contribution in #12514
- @meyer9 made their first contribution in #12576
- @klein818 made their first contribution in #11812
- @ashutoshvarma made their first contribution in #12679
- @ControlCplusControlV made their first contribution in #12727
- @sigma made their first contribution in #12856
Full Changelog: v1.9.4...v1.9.5
🚢 Docker Images:
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.9.5
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.9.5
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-proposer:v1.9.5
OP Contracts v1.8.0-rc.1
Overview
This release is suitable for the L1 contracts as part of the Holocene network upgrade.
Full Contract Set
A chain using this contracts release must be using the following contracts at the specified semvers.
The following contracts are included in this release:
- MIPS: 1.2.1
- SystemConfig: 2.3.0
Additional Information
There is no finalized v1.7.0
release. The release candidate for v1.7.0
was for generating L2 genesis.
op-dispute-mon/v1.2.0
Overview
This is a minor release of op-dispute-mon that includes minor new features and bug fixes. It is an optional upgrade for all users.
What's Changed
- Use game data from previous update cycle if fetching fails. This ensures aggregate metrics remain accurate when there are intermittent errors from source nodes. (#12481)
- Add
op_dispute_mon_oldest_game_update_time
metric to report the timestamp of the least recently updated game.
Full Changelog: op-dispute-mon/v1.1.0...op-dispute-mon/v1.2.0
🚢 Docker Image:
op-challenger/v1.2.0
Overview
This is a minor release of op-challenger that includes minor new features and bug fixes. It is an optional upgrade for all users.
What's Changed
- Allow op-challenger to startup when an enabled trace type does not have a game implementation set on chain (#12539)
- Use binary snapshots with Asterisc (#12586)
- Introduce
--prestates-url
option to specify a URL to download prestates for all trace types from. Can be overridden for specific VM types with--cannon-prestates-url
,--asterisc-prestates-url
and--asterisc-kona-prestates-url
(#12440) - All prestates URL options now accept
file
URLs in addition tohttp
andhttps
(#12441) op-program
log level is now automatically set to matchop-challenger
log level (#12379)
Full Changelog: op-challenger/v1.1.2...op-challenger/v1.2.0
🚢 Docker Image: