Skip to content

Conversation

@bradleycamacho
Copy link
Contributor

No description provided.

@bradleycamacho bradleycamacho requested review from a team and 0xmariniere as code owners October 20, 2025 03:58
@netlify
Copy link

netlify bot commented Oct 20, 2025

Deploy Preview for docs-optimism failed. Why did it fail? →

Name Link
🔨 Latest commit 26bdce1
🔍 Latest deploy log https://app.netlify.com/projects/docs-optimism/deploys/68fb9ed03ee2c30008c96397

@bradleycamacho bradleycamacho changed the base branch from main to mintlify October 20, 2025 03:58
Comment on lines 27 to 28
* Update `op-node` to [NEED VERSION]
* Update `op-geth` to [NEED VERSION]
Copy link
Contributor

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.

Copy link
Contributor Author

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?

Copy link
Contributor

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.

Comment on lines 27 to 28
* Update `op-node` to [NEED VERSION]
* Update `op-geth` to [NEED VERSION]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Versions still TBC

Comment on lines 18 to 20
* **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.
Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Collaborator

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.

Chain operators must complete the following tasks:

* Update `op-challenger` to [NEED VERSION]
Copy link
Contributor

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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


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).
Copy link
Contributor

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>
Copy link
Contributor

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.

* **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.
Copy link
Contributor

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?

@sbvegan sbvegan merged commit 98d6609 into mintlify Oct 31, 2025
6 of 7 checks passed
@sbvegan sbvegan deleted the u17-notice branch October 31, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants