Skip to content

updating rust stack releases #1868

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 1 commit into from
Nov 14, 2025
+14 −14
Merged

updating rust stack releases #1868

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 7 additions & 7 deletions notices/fusaka-notice.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,14 @@

* [op-node/v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2)
* [op-geth/v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5)
* [op-reth/v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1)
* [op-reth/v1.9.2](https://github.com/paradigmxyz/reth/releases/tag/v1.9.2)

### Ensure your L1 beacon node endpoint can serve all blobs

**For operators using an external L1 Ethereum Beacon:**

Before the Ethereum Fusaka hard fork, ensure your external L1 Beacon Chain RPC provider has configured their node to subscribe to all subnets.

Check warning on line 52 in notices/fusaka-notice.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/fusaka-notice.mdx#L52 

Did you really mean 'subnets'?
If your external L1 Beacon Chain RPC provider doesn't subscribe to all subnets, migrate to one that does prior to these deadlines.

Check warning on line 53 in notices/fusaka-notice.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/fusaka-notice.mdx#L53 

Did you really mean 'subnets'?

**For operators running their own L1 Ethereum Beacon Chain Node:**

Expand All @@ -64,7 +64,7 @@

* Lighthouse: `--supernode`
* Teku: `--p2p-subscribe-all-custody-subnets-enabled`
* Grandine: `--subscribe-all-data-column-subnets`

Check warning on line 67 in notices/fusaka-notice.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/fusaka-notice.mdx#L67 

Did you really mean 'Grandine'?
* Lodestar: `--supernode`
* Nimbus: `--debug-peerdas-supernode`

Expand All @@ -76,15 +76,15 @@
| --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio` ensure this is also updated to the latest release. |
| `op-batcher` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.2) | The `op-batcher` must be restarted at least once after updating `op-node` to the latest release. The batcher loads the rollup config once at startup and this will need to happen to update the activation timestamps for Jovian. We've opened this [issue](https://github.com/ethereum-optimism/optimism/issues/18178) to improve this experience in the future. |
| `op-node` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. |

Check warning on line 79 in notices/fusaka-notice.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/fusaka-notice.mdx#L79 

Did you really mean 'Hoodi'?
| `op-geth` | [v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) | |
| `op-challenger` | [v1.7.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.7.0) | If deriving from a chain other than Ethereum Mainnet, Sepolia or Hoodi then L1 chain config must be supplied via a new flag. |

Check warning on line 81 in notices/fusaka-notice.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/fusaka-notice.mdx#L81 

Did you really mean 'Hoodi'?
| `kona-node` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.2) | |
| `kona-host` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.2) | |
| `kona-client` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-client%2Fv1.2.2) | |
| `op-reth` | [v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1) | |
| `op-rbuilder` | [v0.2.9](https://github.com/flashbots/op-rbuilder/releases/tag/op-rbuilder%2Fv0.2.9) | |
| `rollup-boost` | [v0.7.8](https://github.com/flashbots/rollup-boost/releases/tag/rollup-boost%2Fv0.7.8) | |
| `kona-node` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.4) | |
| `kona-host` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.4) | |
| `kona-client` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-client%2Fv1.2.4) | |
| `op-reth` | [v1.9.2](https://github.com/paradigmxyz/reth/releases/tag/v1.9.2) | |
| `op-rbuilder` | | Releases will be available November 17th |
| `rollup-boost` | | Releases will be available November 17th |

<Info>
**Note:** `op-node` uses the new `/eth/v1/beacon/blobs/` API for fetching blob data from L1 beacon nodes. If you run a proxy/load balancer in front of your beacon API, ensure it correctly forwards all query parameters.
Expand Down
14 changes: 7 additions & 7 deletions notices/upgrade-17.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@

* [op-node/v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2)
* [op-geth/v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5)
* [op-reth/v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1)
* [op-reth/v1.9.2](https://github.com/paradigmxyz/reth/releases/tag/v1.9.2)
</Step>

<Step title="Configure the Jovian activation date">
Expand Down Expand Up @@ -90,15 +90,15 @@
| --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio` ensure this is also updated to the latest release. |
| `op-batcher` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.2) | The `op-batcher` must be restarted at least once after updating `op-node` to the latest release. The batcher loads the rollup config once at startup and this will need to happen to update the activation timestamps for Jovian. We've opened this [issue](https://github.com/ethereum-optimism/optimism/issues/18178) to improve this experience in the future. |
| `op-node` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. |

Check warning on line 93 in notices/upgrade-17.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/upgrade-17.mdx#L93 

Did you really mean 'Hoodi'?
| `op-geth` | [v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) | |
| `op-challenger` | [v1.7.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.7.0) | If deriving from a chain other than Ethereum Mainnet, Sepolia or Hoodi then L1 chain config must be supplied via a new flag. |

Check warning on line 95 in notices/upgrade-17.mdx

View check run for this annotation

Mintlify / Mintlify Validation (optimism-373f39ad) - vale-spellcheck

notices/upgrade-17.mdx#L95 

Did you really mean 'Hoodi'?
| `kona-node` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.2) | |
| `kona-host` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.2) | |
| `kona-client` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-client%2Fv1.2.2) | |
| `op-reth` | [v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1) | |
| `op-rbuilder` | [v0.2.9](https://github.com/flashbots/op-rbuilder/releases/tag/op-rbuilder%2Fv0.2.9) | |
| `rollup-boost` | [v0.7.8](https://github.com/flashbots/rollup-boost/releases/tag/rollup-boost%2Fv0.7.8) | |
| `kona-node` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.4) | |
| `kona-host` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.4) | |
| `kona-client` | [v1.2.4](https://github.com/op-rs/kona/releases/tag/kona-client%2Fv1.2.4) | |
| `op-reth` | [v1.9.2](https://github.com/paradigmxyz/reth/releases/tag/v1.9.2) | |
| `op-rbuilder` | | Releases will be available November 17th |
| `rollup-boost` | | Releases will be available November 17th |

### For permissionless fault proof enabled chains

Expand Down