Skip to content

adding the release tags and binaries #1353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Feb 11, 2025
Merged

adding the release tags and binaries #1353

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
99b2507
just waiting for release notes
sbvegan Feb 11, 2025
3e1a593
making feedback adjustments
sbvegan Feb 11, 2025
b283204
updating timestamps
sbvegan Feb 11, 2025
066eb0e
adding op-node release
sbvegan Feb 11, 2025
98e9da4
adding reth and op-batcher
sbvegan Feb 11, 2025
c686313
Apply suggestions from code review
sbvegan Feb 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 17 additions & 48 deletions pages/notices/pectra-changes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,36 +36,30 @@ Pectra contains a variety of EIPs, some of which apply to the OP Stack; others d
* [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md)
* [EIP-7840: Add blob schedule to EL config files](https://github.com/ethereum/EIPs/pull/9129)

## For chain operators
## For node operators

The OP Stack is dividing the Pectra upgrade into two parts:
Node operators will need to upgrade to the respective releases before the activation dates.These following steps are necessary for every node operator:

1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below.
2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this[issue](https://github.com/ethereum-optimism/specs/issues/499).

These following steps are necessary for every chain operator:
### Update to the latest release

<Steps>
### Update to the latest releases
<Callout type="warning">
Full node operators, meaning those who are running op-geth with `gc-mode=full`, will need to reference the [`op-geth v1.101411.8`release notes](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.8) to handle an intermediate upgrade step before upgrading to the latest release. Archive node operators, `gc-mode=archive`, can skip this step and upgrade directly to the latest release.
</Callout>

<Callout type="info">
The software is currently being tested and we expect the releases to be cut by the end of this week (Feb 3rd to 7th). These [release candidates](https://github.com/ethereum-optimism/optimism/issues/13627#issuecomment-2627347212) are currently baking on devnet.
</Callout>
* `op-node` at [`v1.11.0`]()
* `op-geth` at [`v1.101500.0`]()

* `op-node` at `vTBD`
* `op-geth` at `vTBD`
* `op-batcher` at `vTBD`
## For chain operators

### Verify Your Configuration
The OP Stack is dividing the Pectra upgrade into two parts:

Make the following checks to verify that your node is properly configured.
1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below.
2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this[issue](https://github.com/ethereum-optimism/specs/issues/499).

* `op-node` and `op-geth` will log their configurations at startup
* Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs
* Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs
</Steps>
Every chain operator will need to first follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases.

### For fault proof enabled chains
## For fault proof enabled chains

<Callout type="info">
The following instructions assume your chain is on the latest contract release `op-contracts/v1.8.0` and have Holocene activated.
Expand All @@ -83,7 +77,7 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai
### Verify the new absolute prestate

<Callout type="info">
The following is based on the [op-program/v1.5.0-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.1) which is wrapping up testing and the official release will be out soon.
The following is based on the [op-program/v1.5.0-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.1) which will be included in the `op-challenger` release.
</Callout>

You can use this new absolute prestate (`0x03dfa3b3ac66e8fae9f338824237ebacff616df928cf7dada0e14be2531bc1f4`) for the following chains:
Expand Down Expand Up @@ -125,31 +119,6 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai
Once your challenger is ready, you can execute the "Set Dispute Game Implementation" transaction. Please simulate and validate that the expected output prior to executing the transaction.
</Steps>

### For OP Stack forks
## For OP Stack forks

We are working on a PR that will include the ability to sync L1 after the Pectra upgrade. The commits from the PR will need to be applied to your chain before Pectra goes live on L1. We will provide a link to the PR after it is complete.

## For node operators

Node operators will need to upgrade to the respective releases before the activation dates.

These following steps are necessary for every node operator:

<Steps>
### Update to the latest release

<Callout type="info">
The software is currently being tested and we expect the releases to be cut by the end of this week (Feb 3rd to 7th). These [release candidates](https://github.com/ethereum-optimism/optimism/issues/13627#issuecomment-2627347212) are currently baking on devnet.
</Callout>

* `op-node` at `vTBD`
* `op-geth` at `vTBD`

### Verify Your Configuration

Make the following checks to verify that your node is properly configured.

* `op-node` and `op-geth` will log their configurations at startup
* Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs
* Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs
</Steps>
We are working on a PR that will include the ability to sync L1 after the Pectra upgrade. The commits from the new node releases will need to be applied to your chain before Pectra goes live on L1. We will provide a link to the PR after it is complete.