-
Notifications
You must be signed in to change notification settings - Fork 276
U17 notice #1795
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.
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
U17 notice #1795
Conversation
❌ Deploy Preview for docs-optimism failed. Why did it fail? →
|
notices/upgrade-17.mdx
Outdated
| * Update `op-node` to [NEED VERSION] | ||
| * Update `op-geth` to [NEED VERSION] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will want to call out versions for
- op-reth
- kona node/host/client
- op-challenger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have these yet or will we have them once we're code complete?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO We also need to release a new op-conductor and place the version here.
notices/upgrade-17.mdx
Outdated
| * Update `op-node` to [NEED VERSION] | ||
| * Update `op-geth` to [NEED VERSION] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Versions still TBC
notices/upgrade-17.mdx
Outdated
| * **Cannon is being updated to support Go 1.24**, which allows the OP Stack to stay up to date with upstream changes to go-ethereum (which are included in op-geth) | ||
| * **Minimum Base Fee and Data Availability Footprint Block Limit** which allows the L2 base fee to respond more rapidly to changes in block composition, particularly when this implies an increased demand on the rollup’s capacity to batch blocks to the data availability layer. | ||
| * **Operator Fee Fix** which modifies the existing, optional “operator fee” feature. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also make a special callout for anyone running operator fee with nonzero scalars. They need to adjust the scalars before activating the fork to avoid overcharging users. Recommend they examine the specs to understand what adjustment to make.
| @@ -0,0 +1,91 @@ | |||
| --- | |||
| title: Upgrade 17 - Jovian Hard Fork | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to check in whether we need to use the numerical label here. @sbvegan any thoughts? There is a push to not use numbers going forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the governance team is still collecting feedback and I don't think a decision has been made yet
Updated activation times and chains for Upgrade 17.
Upgrade 17 introduces support for Go 1.24, configurable minimum base fee, and data availability footprint block limit. It also includes an operator fee fix for more flexible configurations.
Clarified language regarding on-chain upgrade requirements.
notices/upgrade-17.mdx
Outdated
|
|
||
| Chain operators must complete the following tasks: | ||
|
|
||
| * Update `op-challenger` to [NEED VERSION] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <Steps> | ||
| <Step title="Verify the new absolute prestate"> | ||
|
|
||
| The absolute prestate is generated with the [op-program/v1.8.0-rc.3](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.8.0-rc.3). You can use this new absolute prestate `0x03799051d2bfe459127d4597f469f535ff1bd2a6e1e2134443167620871c11f3` for the following chains: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
notices/upgrade-17.mdx
Outdated
|
|
||
| The absolute prestate is generated with the [op-program/v1.8.0-rc.3](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.8.0-rc.3). You can use this new absolute prestate `0x03799051d2bfe459127d4597f469f535ff1bd2a6e1e2134443167620871c11f3` for the following chains: | ||
|
|
||
| * Mainnet and Sepolia: `OP`, `Base`, `Soneium`, `Ink`, `Unichain`, `Metal`, `Mode`, `Zora`, `Arena-Z`, and `Swell` (Swell Mainnet only). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The prestate review was done for these chains:
op-sepolia,ink-sepolia,base-sepolia,unichain-sepolia,soneium-minato-sepolia,op-mainnet,ink-mainnet,base-mainnet,unichain-mainnet,soneium-mainnet
The others are permissioned, and probably aren't running a challenger. (Soneium is also permissioned for now, but permissionless soon).
| During the previous step, you also generated the preimage of the absolute prestate, which is the op-program serialized into a binary file. You'll find that new file at `optimism/op-program/bin/prestate-mt64.bin.gz`. Rename that file to have the absolute prestate hash as the filename so it looks like `PRESTATEHASH.bin.gz`. | ||
|
|
||
| Upload that file to where you're storing your other absolute preimage files. This should be the location where you're pointing your `--cannon-prestates-url` at. The `op-challenger` will grab this file and use it when it needs to challenge games. | ||
| </Step> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The prestate section looks good.
notices/upgrade-17.mdx
Outdated
| * **Cannon Go 1.24 support:** upgrading the on-chain fault proof virtual machine implementation to support Go 1.24. | ||
| * **Configurable Minimum Base Fee:** allows chain operators to specify a minimum base fee to shorten the length of priority fee auctions (disabled by default). | ||
| * **Data Availability Footprint Block Limit:** adds an in-protocol limit to estimated DA usage of transactions to prevent DA spam and priority fee auctions. (enabled by default; can be disabled via zero scalar on-chain). | ||
| * **Operator Fee Fix:** enables more flexible fee configurations for rollup operators and lays groundwork for future custom gas token support. If you are running operator fee with nonzero scalars, make sure to adjust them before activating the fork to avoid overcharging users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this should be a callout since it is a specific call to action?
No description provided.