Skip to content

Releases: ethereum-optimism/optimism

Release op-contracts v1.4.0-rc.2 - Fault Proofs V1

03 May 17:21
@clabby clabby
op-contracts/v1.4.0-rc.2
a6d4eed
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release op-contracts v1.4.0-rc.2 - Fault Proofs V1 Pre-release
Pre-release

Overview

This release candidate enables fault proofs in the withdrawal path of the bridge on L1. It also modifies the SystemConfig to remove the legacy L2OutputOracle contract in favor of the DisputeGameFactory.

Specification here.

The full set of L1 contracts included in this release is:

  • AddressManager: Latest (this has no version) (No change from prior version)
  • AnchorStateRegistry: 1.0.0 (New Contract)
  • DelayedWETH: 1.0.0 (New Contract)
  • DisputeGameFactory: 1.0.0 (New Contract)
  • L1CrossDomainMessenger: 2.3.0 (No change from prior version)
  • L1ERC721Bridge: 2.1.0 (No change from prior version)
  • L1StandardBridge: 2.1.0 (No change from prior version)
  • OptimismMintableERC20Factory: 1.9.0 (No change from prior version)
  • OptimismPortal: 3.8.0 (Modified from prior version, with breaking changes)
  • SystemConfig: 2.0.0 (Modified from prior version, with breaking changes)
  • SuperchainConfig: 1.1.0 (No change from prior version)
  • ProtocolVersions: 1.0.0 (No change from prior version)

The L2OutputOracle is no longer used for chains running this version of the L1 contracts.

Contracts Changed

  1. L2OutputOracle
    • The L2OutputOracle has been removed from the deployed protocol.
  2. OptimismPortal
    • The OptimismPortal has been modified to allow users to prove their withdrawals against outputs that were proposed as dispute games, created via a trusted DisputeGameFactory contract. spec.
  3. SystemConfig
    • The SystemConfig has been changed to remove the L2_OUTPUT_ORACLE storage slot as well as the getter for the contract. To replace it, a new getter for the DisputeGameFactory proxy has been added.

New Contracts

  1. DisputeGameFactory
    • The DisputeGameFactory is the new inbox for L2 output proposals on L1, creating dispute games.
    • Output proposals are now permissionless by default.
    • Challenging output proposals is now permissionless by default.
  2. FaultDisputeGame
    • The FaultDisputeGame facilitates trustless disputes over L2 output roots proposed on L1. spec.
  3. PermissionedDisputeGame
    • A child of the FaultDisputeGame contract, that permissions proposing and challenging. Deployed as a safety mechanism to temporarily restore liveness in the event of the FaultDisputeGame's failure.
  4. MIPS
    • The MIPS VM is a minimal kernel emulating the MIPS32 ISA with a subset of available Linux syscalls. This contract allows for executing single steps of a fault proof program at the base case of disputes in the FaultDisputeGame. spec.
  5. PreimageOracle
    • The PreimageOracle contract is responsible for serving verified data to the program running on top of the MIPS VM during single-step execution. When data enters the PreimageOracle, it is verified to be correctly formatted and honest. spec.
  6. AnchorStateRegistry
    • The AnchorStateRegistry contract is responsible for tracking the latest finalized root claims from various dispute game types.
  7. DelayedWETH
    • DelayedWETH is an extension of WETH9 that delays unwrapping operations. Bonds that are placed in dispute games are held within this contract, and the owner may intervene in withdrawals to redistribute funds to submitters in case of dispute game resolution failure.

Full Changelog

op-contracts/v1.4.0-rc.1...op-contracts/v1.4.0-rc.2

Assets 2
Loading

op-node v1.7.5

02 May 18:22
@geoknee geoknee
op-node/v1.7.5
e87e5ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-node v1.7.5

⚠️ This is a recommended maintenance release of op-node. It fixes an ssz unmarshaling implementation in the p2p req-resp protocol (#10362).

Partial changelog (op-node)

New Contributors (all monorepo)

Full Changelog (all monorepo): v1.7.4...op-node/v1.7.5

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

Contributors

sebastianst, AaronChen0, and 4 other contributors
Assets 2
Loading

op-stack v1.7.4

26 Apr 18:09
@sebastianst sebastianst
v1.7.4
24a8d3e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-stack v1.7.4

⚠️ Strongly recommended maintenance release

🐞 op-node blob reorg bug fix (#10210)

If an L1 block got reorg'd out during blob retrieval, an op-node might get stuck in a loop retrieving a blob that will never exist, requiring a restart. This got fixed by internally signaling the right error types, forcing a derivation pipeline reset in such cases.

✨ op-batcher & op-proposer node sync start (#10116 #10193 #10262 #10273)

op-batcher and op-proposer can now wait for the sequencer to sync to the current L1 head before starting their work.
This fixes an issue where a restart of op-batcher/proposer and op-node at the same time might cause to resend duplicate batches from the last finalized L2 block, because a freshly restarted op-node resyncs from the finalized head, potentially signaling a too early safe head in its sync status.

🏳️ This feature is off by default, so we recommend testing it by using the new batcher and proposer flag --wait-node-sync (or its corresponding env vars).

Enabling this will cause op-batcher and op-proposer to wait for the sequencer's verifier confirmation depth for typically 4 L1 blocks, or ~1 min, at startup.

🏳️ To speed up this process in case that no recent batcher transaction have happened, there's another optional new batcher flag --check-recent-txs-depth that lets the batcher check for recent batcher transactions to determine a potentially earlier sync target. This feature is off by default (0) and should be set to the sequencer's verifier confirmation depth to get enabled.

Partial changelog

op-node

op-batcher & op-proposer

New Contributors (all monorepo)

Full Changelog: v1.7.3...v1.7.4

🚢 Docker Images:

Contributors

dome, geoknee, and 11 other contributors
Assets 2
Loading

op-contracts/v1.4.0-rc.1

23 Apr 14:39
@maurelian maurelian
op-contracts/v1.4.0-rc.1
802c283
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-contracts/v1.4.0-rc.1 Pre-release
Pre-release

This contracts release adds an optional DA Challenge contract for use with OP Plasma. If usePlasma is set to true in the deploy config, then the OP Plasma feature will be enabled.

The challenge DA contract is used to ensure that data posted as part of OP Plasma is made available. There are four deploy config parameters that must be set when using this feature: daChallengeWindow, daResolveWindow, daBondSize, daResolverRefundPercentage

Assets 2
Loading

Release op-node, op-batcher, op-proposer v1.7.3

11 Apr 23:35
@trianglesphere trianglesphere
v1.7.3
a3cc8f2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release op-node, op-batcher, op-proposer v1.7.3

⬆️ This is a recommended release for Optimism Mainnet, particularly for op-batcher operators.

This release contains general fixes & improvements to op-node, op-batcher, & op-proposer. This also update the monorepo op-geth dependency to https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101311.0

The most important change to be aware of is that the op-batcher is now significantly more performant in handling span batches that contain a large number of L2 blocks.

Partial Changelog

Full Changelog: v1.7.2...v1.7.3

🚢 Docker Images:

Contributors

ajsutton, zhiqiangxu, and 10 other contributors
Assets 2
Loading

op-node, op-batcher, op-proposer v1.7.2 - Batcher Improvements

22 Mar 19:01
@geoknee geoknee
v1.7.2
99a5338
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-node, op-batcher, op-proposer v1.7.2 - Batcher Improvements

⬆️ This is a strongly recommended release of op-batcher for all chain operators.

op-batcher changes

Multi-blob support in op-batcher

See release notes for v1.7.2-rc.3 for details on how to configure a multi-blob batcher.

Improved channel duration tracking

The batcher now tracks channel durations relative to the last L1 origin in a previous channel. The last channel's L1 origin is restored at startup and during reorgs.

This ensures that the desired channel duration survives restarts of the batcher, which is particularly important for low-throughput chains that use channel durations of a few hours.

There's a known quirk in the new tracking design, which leads to a slightly lower effective channel duration (~1min lower), related to how a channel timeout is determined relative to the current L1 head, not current channel's newest L1 origin. This will be improved in a future release.

Breaking compressor configuration change

The channel and compressor configuration got simplified by removal of the target-frame-size flag. The only configuration parameters left to configure the channel size are

  • max-l1-tx-size - default of 120k for calldata; for blobs this is overwritten to the max blob size
  • taget-num-frames - default of 1 for calldata; for multi-blob txs, set this to the desired amount of blobs per blob-tx (e.g. 6)
    The default compressor is the shadow compressor, which is recommended in production.

Overflow frames bug fix

The batcher now correctly estimates a channel's output size, fixing a rarely but regularly occurring bug that produced overflow frames, leading for example to a 7th blob that was sent in a second batcher transaction.

op-node changes

  • Improved peering behavior
  • Per-chain hardfork activation times via superchain-registry

Partial Changelog

New Contributors

Full Changelog: v1.7.0...v1.7.2

🚢 Docker Images

Contributors

ajsutton, danyalprout, and 11 other contributors
Assets 2
Loading

op-batcher v1.7.2-rc.3 - Multi-Blob Batcher

13 Mar 10:08
@sebastianst sebastianst
op-batcher/v1.7.2-rc.3
25985c1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-batcher v1.7.2-rc.3 - Multi-Blob Batcher Pre-release
Pre-release

🔴✨ Multi-Blob Batcher Pre-Release

The op-batcher in this release candidate has the capabilities to send multiple blobs per single blob transaction. This is accomplished by the use of multi-frame channels, see the specs for more technical details on channels and frames.

A minimal batcher configuration (with env vars) to enable 6-blob batcher transactions is:

      - OP_BATCHER_BATCH_TYPE=1 # span batches, optional
      - OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs
      - OP_BATCHER_TARGET_NUM_FRAMES=6 # 6 blobs per tx
      - OP_BATCHER_TXMGR_MIN_BASEFEE=2.0 # 2 gwei, might need to tweak, depending on gas market
      - OP_BATCHER_TXMGR_MIN_TIP_CAP=2.0 # 2 gwei, might need to tweak, depending on gas market
      - OP_BATCHER_RESUBMISSION_TIMEOUT=240s # wait 4 min before bumping fees

This enables blob transactions and sets the target number of frames to 6, which translates to 6 blobs per transaction. The min. tip cap and base fee are also lifted to 2 gwei because it is uncertain how easy it will be to get 6-blob transactions included and slightly higher priority fees should help. The resubmission timeout is increased to a few minutes to give more time for inclusion before bumping the fees, because current txpool implementations require a doubling of fees for blob transaction replacements.

Multi-blob transactions are particularly interesting for medium to high-throughput chains, where enough transaction volume exists to fill up 6 blobs in a reasonable amount of time. You can use this calculator for your chain to determine what number of blobs are right for you, and what gas scalar configuration to use. Please also refer to our documentation on Blobs for chain operators.

🚢 Docker image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.7.2-rc.3

A full v1.7.2 release of the op-stack follows soon.

Assets 2
Loading

Release op-node v1.7.1

06 Mar 17:57
@trianglesphere trianglesphere
op-node/v1.7.1
c87a469
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release op-node v1.7.1

⬆️ This is a recommended release for node operators using Snap Sync on Optimism Mainnet & Sepolia. For other users, this is a minor release. Node operators should be on at least v1.7.0.

Changes

  • This release contains a fix to snap sync to ensure that all blocks are inserted to the execution engine when snap sync completes. Previously once snap sync would complete, if blocks where received out of order, the op-node could have internally inconsistent state & the unsafe head could stall for a period of time.
  • This release also contains a safeDB feature which tracks the L1 block L2 blocks are derived from.

Partial Changelog

New Contributors

Full Changelog: op-node/v1.7.0...op-node/v1.7.1

🚢 Docker Images

Contributors

ajsutton, trianglesphere, and 2 other contributors
Assets 2
Loading

op-node, op-batcher, op-proposer v1.7.0 - Optimistic Ecotone Mainnet Release

26 Feb 13:39
@sebastianst sebastianst
v1.7.0
f707883
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-node, op-batcher, op-proposer v1.7.0 - Optimistic Ecotone Mainnet Release

✨🔴 Optimistic Ecotone Mainnet Release

❗ Mainnet operators are required to update to this release to follow the chain post-Ecotone. This release contains an optimistic Ecotone Mainnet activation time of Mar 14, 00:00:01 UTC.

⚠️ The old release v1.6.1 contained a different Ecotone Mainnet activation date, so it is particularly important for Mainnet operators to upgrade from this release.

Optimism Governance Voting Cycle 19

The Ecotone activation contained in this release is still subject to approval during the currently ongoing Optimism Governance voting cycle 19, see the Governance Proposal of the Ecotone Protocol Upgrade. The voting period ends on Mar 6 while the veto period ends on Mar 13, 19:00 UTC.

We will soon publish a Veto Release in advance with the Ecotone OP Mainnet activation removed so node operators can prepare for the unlikely event of a negative vote or a veto. We will also soon provide documentation on how to override the Ecotone activation included in this or future releases via command line flags or env vars. This leaves an emergency window of 5h to change the node configuration, or update to the Veto Release, in the unlikely event that the veto period ends in a veto.

New Beacon Endpoint

Node operators need to configure a Beacon endpoint for op-node, because soon after the Ecotone activation, batch transactions will be sent as 4844 blobs, and blobs can only be retrieved from Beacon nodes. If you're using Lighthouse, make sure to use at least version v5.0.0, which contains the Dencun upgrade for Mainnet.

The op-node provides a new command line flag & env var for configuring the Beacon endpoint: --l1.beacon and $OP_NODE_L1_BEACON. If you need to configure an HTTP header for authentication with the Beacon endpoint, you can use the flag --l1.beacon-header or $OP_NODE_L1_BEACON_HEADER.

❗ We encourage all node operators to already configure their Beacon endpoint to avoid interruptions after the Ecotone activation.

Experimental Snap Sync (execution-layer sync)

op-node 1.7.0 and op-geth v1.101308.2 now support Snap Sync. To enable snap sync set the --syncmode=execution-layer flag on op-node. op-geth should also be set to --syncmode=snap and must have discovery and be peered to the network for snap sync to work.

This feature is ready to be tested, but still may contain some bugs as it is rolled out.

Partial Changelog (affecting op-node)

Full Changelog (monorepo): v1.6.1...v1.7.0

🚢 Docker Images

https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.0
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.7.0
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-proposer:v1.7.0

Contributors

ajsutton, geoknee, and 2 other contributors
Assets 2
Loading

op-node, op-batcher, op-proposer v1.6.1 - OUTDATED Ecotone Mainnet Release

16 Feb 21:41
@sebastianst sebastianst
v1.6.1
08921d5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
op-node, op-batcher, op-proposer v1.6.1 - OUTDATED Ecotone Mainnet Release

❗ OUTDATED Ecotone Mainnet Release

❌ The Optimistic Ecotone Mainnet activation has been moved forward to Mar 14, 00:00:01 UTC! You MUST NOT use this release on Mainnet. Use v1.7.0 instead.

✅ You can safely use this release on all other testnets and devnets.

Old Optimistic Release Background Info

This release contained an optimistic Ecotone Mainnet activation time of Mar 18, 17:00:01 UTC. The purpose of this release was to have a reference for the Governance Proposal of the Ecotone Protocol Upgrade. The Ecotone Mainnet activation still needs to be approved during the currently ongoing Optimism Governance voting cycle 19 whose review and voting periods runs from Feb 15 to Mar 6. The veto period ends on Mar 13.

We will soon publish a Veto Release in advance with the Ecotone OP Mainnet activation removed so node operators can prepare for the unlikely event of a negative vote or a veto. We will also provide documentation on how to override the Ecotone activation included in this or the v1.7.0 release.

New Beacon Endpoint

Node operators who already wish to upgrade to this release need to configure a Beacon endpoint for op-node, because soon after the Ecotone activation, batch transactions will be sent as 4844 blobs, and blobs can only be retrieved from Beacon nodes. If you're using Lighthouse, make sure to use at least the finalized version v4.6.0 because the latest rc contains a bug in its blob_sidecars http endpoint.

The op-node provides a new configuration flag & env var for configuring the Beacon endpoint: --l1.beacon and $OP_NODE_L1_BEACON.

We encourage all node operators to already configure their Beacon endpoint to avoid interruptions after the Ecotone activation.

Ecotone Sepolia

This release is ready to be used by Sepolia node operators. Ecotone activated on Sepolia at Wed Feb 21 17:00:00 UTC 2024. The activation has been part of v1.5.1 as well.

🐞 Bug Fixes

  • op-node contained a bug that affected block gossiping for sequencers. This release fixes that bug (#9560). Because of this bug, we advice against usage of op-node v1.6.0 and this version has therefore not been published.
  • log: DynamicLogHandler to also capture derived handlers by @sebastianst in #9479

Partial Changelog - op-node

Partial Changelog - op-batcher & op-proposer

New Contributors

Full Changelog (monorepo): v1.5.1...v1.6.1

🚢 Docker Images

https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.6.1
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.6.1
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-proposer:v1.6.1

Contributors

sebastianst, d-roak, and 6 other contributors
Assets 2
Loading