Skip to content

updating notice pages for comms #1847

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 8 commits into from
Nov 6, 2025
Merged

updating notice pages for comms #1847

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
762d1b7
updating notice pages for comms
sbvegan Nov 5, 2025
95f67e0
adding callout
sbvegan Nov 5, 2025
7964da3
updating callouts
sbvegan Nov 5, 2025
7771a7a
Merge branch 'mintlify' into sb-u17-fusaka-notice-updates
sbvegan Nov 5, 2025
c70d189
making small updates
sbvegan Nov 5, 2025
f15c97a
Merge branch 'mintlify' into sb-u17-fusaka-notice-updates
sbvegan Nov 6, 2025
aaa71e7
adding release links and removing out of date callouts
sbvegan Nov 6, 2025
3cfa448
adding challenger releases
sbvegan Nov 6, 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
124 changes: 69 additions & 55 deletions notices/fusaka-notice.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@

This page provides external-facing information about the Fusaka readiness upgrade for OP Stack chains. It summarizes scope, timelines, required actions, and resources for chain operators and partners. This upgrade is necessary for all OP Stack chains deriving from an L1 chain which is due to activate Fusaka (including Ethereum Mainnet and Sepolia).

This is NOT Fusaka adoption on L2. It's a readiness upgrade to make the Optimism protocol compatible with L1 that activates the Fusaka fork. L2 adoption will happen in a future upgrade.
This is NOT Fusaka adoption on L2. It's a readiness upgrade to make the OP Stack protocol compatible with L1 that activates the Fusaka fork. L2 adoption will happen in a future upgrade.

<Info>
All of the tasks below must be performed before Fusaka activates on L1.
Expand All @@ -30,29 +30,33 @@

**Important dates:**

Ethereum Sepolia Fusaka hard fork: Tuesday, October 14th, 2025 07:36:00 UTC (affects chains posting data to Sepolia)

Ethereum Mainnet Fusaka hard fork: Wednesday, December 3rd, 2025 21:49:11 UTC, 1764798551
* Ethereum Sepolia Fusaka hard fork: Tuesday, October 14th, 2025 07:36:00 UTC (`1760427360`)
* Sepolia BPO 1: Tuesday, October 21st, 2025 03:26:24 UTC (`1761017184`)
* Sepolia BPO 2: Monday, October 27th, 2025 23:16:48 UTC (`1761607008`)
* Ethereum Mainnet Fusaka hard fork: Wednesday, December 3rd, 2025 21:49:11 UTC (`1764798551`)
* Ethereum Mainnet BPO 1: Tuesday, December 9th, 2025 14:21:11 UTC (`1765290071`)
* Ethereum Mainnet BPO 2: Wednesday, January 7th, 2026 01:01:11 UTC (`1767747671`)

## For node operators

Update your node software as soon as possible after release:

* Update `op-node` to [v1.14.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.14.1). See the release notes for new config flags and env variables (not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi.)
* Update `op-geth` to [v1.101603.1](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.1)
* [op-node/v1.16.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1)
* [op-geth/v1.101603.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4)
* [op-reth/v1.9.0](https://github.com/paradigmxyz/reth/releases/tag/v1.9.0)

### 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:**

**If you operate your own L1 nodes, ensure also both the L1 execution and beacon nodes are upgraded** and configured for the Fusaka fork (see [Fusaka specs here](https://blog.ethereum.org/2025/09/26/fusaka-testnet-announcement)).
**If you operate your own L1 nodes, ensure also both the L1 execution and beacon nodes are upgraded** and configured for the Fusaka fork.

Outdated L1 nodes can cause derivation failures, blob unavailability, or chain divergence after the fork.
Outdated L1 nodes will cause derivation failures, blob unavailability, or chain divergence after the fork.

Configure your Beacon Node with the new flag (detailed below) before the relevant Fusaka hard fork date.

Expand All @@ -60,84 +64,94 @@

* 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`

## For chain operators

<Info>
Be ready to restart your batcher with the new configuration immediately after the Fusaka fork on L1: e.g. for Sepolia this is at Unix timestamp 1760427360 (Tue Oct 14 2025 07:36:00 UTC). For Mainnet this is at Unix timestamp 1764798551 (Wed Dec 03 2025 21:49:11 UTC).
</Info>

<Info>
Although new chains deriving from Holesky are supported, existing chains deriving from Holesky are not supported since Holesky already activated Fusaka on L1.
</Info>

Update the following:
Update the following components:

| Component | Version | Notes |
| --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `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.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.0) | `OP_BATCHER_TXMGR_ENABLE_CELL_PROOFS`: `true` or equivalent CLI flag needs to be set and the batcher restarted just after Fusaka activates on L1. |
| `op-node` | [v1.14.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.14.1) | 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. |
| `op-geth` | [v1.101603.1](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.1) | |
| `op-challenger` | [v1.6.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.6.0) | 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. |
| `kona-node` | [v1.1.6](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.1.6) | |
| `kona-host` | [v1.1.6](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.1.6) | |
| `kona-client` | [v1.1.6](https://github.com/op-rs/kona/releases/tag/kona-client%2Fv1.1.6) | |
| `op-reth` | [v1.8.2](https://github.com/paradigmxyz/reth/releases/tag/v1.8.2) | |
| `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.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1) | 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.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4) | |
| `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` | []() | |
| `kona-host` | []() | |
| `kona-client` | []() | |
| `op-reth` | [v1.9.0](https://github.com/paradigmxyz/reth/releases/tag/v1.9.0) | |

<Info>
**Note:** `op-node` v1.14.1 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.
**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.

Misconfigured proxies may cause blob fetch failures or derivation stalls after the Fusaka fork.
</Info>
### For Permissionless Fault Proof enabled chains

Chains running permissionless fault proofs will need to deploy new dispute game contracts with new absolute prestates. The new 64 bit version of cannon will be utilized moving forward. The Sepolia Superchain, will utilize [op-program/v1.7.0-rc.3](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.7.0-rc.3).
### For permissionless fault proof enabled chains

<Info>
Optimism will complete the on-chain prestate update (including Dispute Game deployment and implementation set) on OP Sepolia, Base Sepolia, Ink Sepolia, and Uni Sepolia. However, off-chain components (op-challenger) must still be configured by operators to use the new prestate.
<Note>
The Superchain will be bundling Fusaka support and the Mainnet [Jovian hard fork](/notices/upgrade-17) support into a single absolute prestate.
</Note>

If you are a Permissionless FP–enabled chain not included in the list above, you must perform all steps below yourself.
<Info>
Optimism will complete the onchain prestate update (including Dispute Game deployment and implementation set) on OP, Ink, and Unichain Mainnet and Sepolia.
However, off chain components (op-challenger) must still be configured by operators to use the new prestate.
If you are a Permissionless FP enabled chain not included in the list above, you must perform all steps below yourself.
</Info>

Chains running permissionless fault proofs will need to deploy new dispute game contracts with new absolute prestates.

<Steps>
<Step title="Verify the new absolute prestate">
<Step title="Verify the new absolute prestate">

<Info>
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.8.0-rc.4](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.8.0-rc.4). You can use this new absolute prestate `0x03caa1871bb9fe7f9b11217c245c16e4ded33367df5b3ccb2c6d0a847a217d1b` for the following chains:

* Mainnet and Sepolia: `OP`, `Base`, `Ink`, and `Unichain`

You can verify this absolute prestate by running the following command in the root of the monorepo on the `op-program/v1.8.0-rc.4` tag:

```shell
make reproducible-prestate
```

This will output the calculated prestates, the tail end of the output should look like this:

The absolute prestate is generated with the [op-program/v1.7.0-rc.3](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.7.0-rc.3). You can use this new absolute prestate (`0x0339db503776757491b9f3038bf6f1d37b7988a2f75e823fe2656c1352ef2f91`) for chains in the superchain registry.
```shell
-------------------- Production Prestates --------------------

You can verify this absolute prestate by running the following [command](https://github.com/ethereum-optimism/optimism/blob/op-program/v1.7.0-rc.3/Makefile#L130-L132) in the root of the monorepo on the `op-program/v1.7.0-rc.3` tag:
Cannon64 Absolute prestate hash:
0x03caa1871bb9fe7f9b11217c245c16e4ded33367df5b3ccb2c6d0a847a217d1b

```shell
make reproducible-prestate
```
</Step>
-------------------- Experimental Prestates --------------------

<Step title="Upload your new preimage file">
Cannon64Next Absolute prestate hash:
0x03caa1871bb9fe7f9b11217c245c16e4ded33367df5b3ccb2c6d0a847a217d1b

During the previous step, you also generated the preimage of the absolute prestate, which is basically 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 `0x0339db503776757491b9f3038bf6f1d37b7988a2f75e823fe2656c1352ef2f91.bin.gz`.
CannonInterop Absolute prestate hash:
0x03455f7f2179327853a989648c3ac9f2d58be45137bae603271660519b4d5245

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>
CannonInteropNext Absolute prestate hash:
0x03455f7f2179327853a989648c3ac9f2d58be45137bae603271660519b4d5245
```

<Step title="Deploy new dispute game contracts">
* The "Cannon64" hash is the 64-bit prestate.

You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value.
</Step>
Verify that your target prestate was calculated as expected and matches the corresponding entry in
[standard-prestates.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/validation/standard/standard-prestates.toml).
</Step>

<Step title="Update the DisputeGameFactory">
<Step title="Upload your new preimage file">
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`.

You will then need to update the `DisputeGameFactory` to point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`.
</Step>
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>

<Step title="Execute the upgrade">
<Step title="Execute the upgrade">
Once your `op-challenger` is ready with the new preimage, you can execute the upgrade transaction. This should be done by making a delegatecall to the `upgrade()` function of the OP Contract Manager at the address listed in [the registry](https://github.com/ethereum-optimism/superchain-registry/blob/main/validation/standard/standard-versions-mainnet.toml).

Once your `op-challenger` is ready with the new preimage, you can execute the "Set Dispute Game Implementation" transaction. Please simulate and validate that the expected output prior to executing the transaction.
</Step>
Please simulate and validate the expected output prior to executing the transaction.
</Step>
</Steps>
Loading