U17 notice #1795
U17 notice #1795
Conversation
❌ Deploy Preview for docs-optimism failed. Why did it fail? →
|
| * Update `op-node` to [NEED VERSION] | ||
| * Update `op-geth` to [NEED VERSION] |
There was a problem hiding this comment.
We will want to call out versions for
- op-reth
- kona node/host/client
- op-challenger.
There was a problem hiding this comment.
Do we have these yet or will we have them once we're code complete?
| As of upgrade 14, the 64 bit multi-threaded version of cannon is utilized. | ||
| </Info> | ||
|
|
||
| The absolute prestate is generated with the [op-program/v1.6.1-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.6.1-rc.1). You can use this new absolute prestate `0x03eb07101fbdeaf3f04d9fb76526362c1eea2824e4c6e970bdb19675b72e4fc8` for the following chains: |
| * Update `op-node` to [NEED VERSION] | ||
| * Update `op-geth` to [NEED VERSION] |
|
|
||
|
|
||
| Cannon64 Absolute prestate hash: | ||
| 0x03eb07101fbdeaf3f04d9fb76526362c1eea2824e4c6e970bdb19675b72e4fc8 |
| * **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.
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.
| Upgrade 17 introduces the following changes: | ||
|
|
||
| * **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. |
There was a problem hiding this comment.
I would split these up into two bullets.
Be good to clarify default behavior for chain operators:
- da footprint: this can be disabled by setting a zero scalar on chain, but it will be enabled by default (see the specs)
- min base fee is disabled by default
| @@ -0,0 +1,91 @@ | |||
| --- | |||
| title: Upgrade 17 - Jovian Hard Fork | |||
There was a problem hiding this comment.
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.
|
|
||
| For more information on the Jovian implementation details, please review the [Jovian specifications](https://specs.optimism.io/protocol/jovian/overview.html). | ||
|
|
||
| ## For node operators |
There was a problem hiding this comment.
In our slack comms we had
⚠️ Breaking Changes - Block header changes:
extraData field is extended (for the min base fee)
blobGasUsed may become nonzero when the DA footprint feature is enabled
Please ensure your nodes and tooling can handle these updated header semantics. This applies to all node operators, particularly those running nodes for SCR chains with special steps for chain operators running permisionless fault proofs. Non-SCR chains are unaffected unless they independently choose to schedule the fork.
Which I like.
2 participants
No description provided.