op-deployer/v0.4.4

Overview

op-deployer/v0.4.4 supports deploying, upgrading to, and producing calldata for op-contracts/v4.1.0 (u16a).

Details

Additional changes outside of op-contracts/v4.1.0 support include:

• ability to specify a custom block GasLimit when deploying a new OPChain via the chainIntent.GasLimit field
• fusaka defense via reduction of default tx.GasPadFactor from 2.0 -> 1.2 (to allow opcm.deploy to work)
• modified contracts locator in intent.toml (deprecated tag:// locator in favor of embedded)
  1. embedded (default) - embeds artifacts.tgz file containing contracts artifacts from same branch as op-deployer, ensuring compatibility
  2. https:// - download artifacts.tgz from remote server
  3. file:// - point to local filepath of contract artifacts

op-deployer/v0.4.4-rc.2

Changelog

op-deployer/v0.4.4-rc.1

Changelog

• 35bb378 op-deployer: add upgrade v4_1_0 command (#17790)

op-node/v1.14.1 Fusaka Readiness Release (Sepolia)

Warning

This is an essential release to prepare for the L1 Fusaka fork on Sepolia. It supersedes op-node/v1.14.0 which had a bug. The corresponding op-geth release is v1.101603.1.
Node operators must also upgrade their batcher to op-batcher/v1.16.0 before Fusaka activates. See its release notes for further instructions.

With this release of op-node, the L1 Chain Configuration (namely, the fork activation times and blob parameters for each fork) form part of L2 consensus.

This release therefore introduces the --rollup.l1-chain-config flag and accompanying OP_NODE_ROLLUP_L1_CHAIN_CONFIG environment variable. This is not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi -- for those chains, the chain config is already baked into op-node and will be used automatically.

Note

Chains already running on Holesky are not supported since Holesky has already activated Fusaka. New chains deployed to Holesky are supported.

Warning

For chains deriving from an L1 other than Mainnet, Sepolia, Holesky or Hoodi: an up-to-date genesis.json or chain configuration file for the L1 must be provided. New L1 forks, including BPO forks, must be added to this file before they activate on L1.

For the "known" L1 chains, we will publish op-node releases with updated L1 configurations baked in due course.

This release also modifies the way op-node fetches and verifies blobs from beacon endpoints.

Important

It is required that the beacon node passed with --l1.beacon is configured to store all blobs.

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

• op-service: use correct response type in blob retrieval by @joshklop in #17779
• op-deployer: Do not create cache directory on import by @mslipper in #17776
• beacon client: use new fusaka endpoint to get blobs by @joshklop in #17736
• l1-beacon-client: verify blobs using commitment only (not the proof) by @geoknee in #17725
• op-node,op-program,kona: embed L1ChainConfig in configuration by @geoknee in #17568
• op-node: merge EngineResetDeriver with EngineController by @nonsense in #17662
• op-node: EngineController: Proper locking by @pcw109550 in #17648
• op-node: refactor EngineController by @nonsense in #17647
• op-node/rollup: remove ReceivedUnsafePayloadEvent event by @nonsense in #17530
• op-node/rollup/clsync: test for popping the same element by @nonsense in #17608
• op-service/httputil: move resp.Body.Close right after err check by @nonsense in #17611

Full Changelog: op-node/v1.13.7...op-node/v1.14.1

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

op-deployer/v0.4.3

Changelog

• 881dd74 Improve docs and invocation on just deploy-opcm (#16421)
• f229243 Update version (#16829)
• c8f2fdd [proposal/op-contracts/v4.1.0] op-deployer: support contracts v4.1.0 (#17733)
• aff5fbe chore: op-deployer prestate generation log change (#17058)
• 5a6ed16 ci: Move linter configuration to .golangci.yaml (#16935)
• d24cf93 ctb,op-deployer: Remove isRC() and L1_CONTRACTS_RELEASE (#17028)
• c65dd1d feat(op-deployer): Add a command for OPCM.migrate call (#16710)
• 7eedfce feat(txmgr / batcher): Rebroadcast transactions without bumping fees (#16310)
• c3233fc feat: dev feature flagging in OPCM (#17268) (#17341)
• 594bc93 fix: bug blocking op-deployer verify (#17503)
• ba50c0d integrate Standard Validator into OPCM (#16237)
• cedc4e9 op-deployer: Add docs on custom superchains (#16309)
• 187a61e op-deployer: Add support for upgrading and validating v4.0.0 (#16048)
• c7605f4 op-deployer: Add test for contract artifact integrity (#16568)
• e0c8917 op-deployer: Add tests for end-to-end bootstrap (#16575)
• 34a1ff9 op-deployer: Bundle artifacts inside binary (#16777)
• 51cb1a7 op-deployer: Fix l1 contracts release flag (#16316)
• 456a4cb op-deployer: Fix test that broke with U16 (#16657)
• 9d95e2f op-deployer: Improve add-game-type (#16373)
• a87c898 op-deployer: fix bootstrap implementations flags (#17090)
• 199b504 op-deployer: fix implementationsDeployment idempotency (#16567)
• ac0b434 op-deployer: opt by using prealloc slice (#16901)
• 70c0da3 op-deployer: remove AddGameType.DisputeGameType validation (#16453)
• 5fba9dc opd: Add just recipes for deployment and verification purposes (#16262)

op-challenger/v1.6.0

Overview

This release of op-challenger adds support for the Ethereum Fusaka upgrade. It's a required upgrade.

What's Changed

• Support for Fusaka with op-program v1.7.0
• If deriving from a chain other than Ethereum Mainnet, Sepolia or Hoodi then L1 chain config must be supplied via a new flag.
• Support for cannon-kona games
• New metrics: i-cache misses, number of consecutive failures

Full Changelog: op-challenger/v1.5.2...op-challenger/v1.6.0

🚢 Docker Image:

• https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-challenger:v1.6.0

op-batcher/v1.16.0 Fusaka Readiness Release (Sepolia)

Warning

This is an essential release to prepare for the L1 Fusaka fork on Sepolia.

Important

The new flagOP_BATCHER_TXMGR_ENABLE_CELL_PROOFS must be set to "true" immediately after the Fusaka activation on L1.

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

• txmgr: allow blobs to be sent with fusaka-compatible cell proofs (sidecar version 1) by configuration by @geoknee in #17620
• txmgr: fetch BlobBaseFee over RPC instead of computing from block header by @geoknee in #17566

Full Changelog: op-batcher/v1.15.0...op-node/v1.16.0

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

op-conductor/v0.8.0

What's Changed

• feat(op-conductor): rollup-boost partial unhealthiness tolerance by @yashvardhan-kukreja in #17633

New Contributors

• @devin-ai-integration[bot] made their first contribution in #17415
• @wlawt made their first contribution in #17330

Full Changelog: op-conductor/v0.7.3...op-conductor/v0.8.0

op-deployer/v0.3.4

Changelog

• de7ca5a [backports] op-deployer: support custom gasLimit (#17585)

op-node v1.13.7

Note

This is a required release for the arena-z-sepolia chain. It is optional otherwise.

🤝 The corresponding op-geth release is v1.101602.3.

What's Changed

• op-node: remove elSyncEnabled as it is a noop by @nonsense in #17425
• refactor: introduce IsFeature toggles for Jovian by @geoknee in #17424
• go: bump op-geth dependency to update SR for addresses cleanup by @serpixel in #17404
• chore: update SystemConfig doc for minimum base fee by @wlawt in #17481
• feat: add tests for min-base-fee by @wlawt in #17441
• chore: bump op-geth to include new superchain registry configuration of arena-z-sepolia isthmus hardfork by @jelias2 in #17437
• op-node: Skip L1 genesis hash check if block is not available from the L1 by @ajsutton in #17407
• min-base-fee: bring in op-geth code by @geoknee in #17307
• feat: bump op-geth by @jelias2 in #17323
• op-node: fix comment for l1.cache-size by @zhiqiangxu in #17107

New Contributors

• @devin-ai-integration[bot] made their first contribution in #17415
• @wlawt made their first contribution in #17330

Full Changelog: op-node/v1.13.6...op-node/v1.13.7

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