Skip to content

Commit 460edb4

Browse files
authored
docs: add fusaka mainnet upgrade notice (#889)
* docs: add fusaka mainnet upgrade notice * docs: clean up * docs: remove duplicate
1 parent a581d00 commit 460edb4

File tree

1 file changed

+9
-14
lines changed

1 file changed

+9
-14
lines changed

docs/docs/docs/bob-chain/full-node.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -5,37 +5,32 @@ sidebar_label: Run a Full Node
55

66
# Run a Full Node
77

8-
:::warning Upcoming BOB Fusaka Readiness Upgrade – October 14, 2025 (Sepolia), Early December 2025 (Mainnet)
8+
:::warning Fusaka Activation on Ethereum Mainnet
99
**What's Included in the Upgrade**
1010
This is a **readiness upgrade** to make BOB protocol compatible with Ethereum's Fusaka hardfork on L1. This is NOT Fusaka adoption on L2—that will happen in a future upgrade.
1111

1212
**Important Dates**
1313

1414
- Ethereum Sepolia Fusaka hard fork: Tuesday, October 14th, 2025 07:36:00 UTC (BOB testnet already upgraded)
15-
- Ethereum Mainnet Fusaka hard fork: Expected early December 2025
15+
- Ethereum Mainnet Fusaka hard fork: December 3rd, 2025 21:49:11 UTC
1616

1717
**Required Actions for Node Operators**
1818

19-
If you or your partners are running external nodes, please ensure the following steps are completed:
19+
If you operate a BOB mainnet node, you must upgrade op-node and op-geth to the versions specified in the official notice:
2020

2121
- **op-node**: Update to version [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2)
2222
- **op-geth**: Update to version [v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5)
23-
- **L1 Beacon Node**: Ensure your L1 beacon node endpoint can serve all blobs and is configured with the appropriate Fusaka flags before the fork
2423

25-
**Required Actions for Chain Operators**
24+
Official notice: [https://docs.optimism.io/notices/fusaka-notice#for-node-operators](https://docs.optimism.io/notices/fusaka-notice#for-node-operators)
2625

27-
- **op-batcher**: Update to [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.2) with `OP_BATCHER_TXMGR_ENABLE_CELL_PROOFS: true` and restart just after Fusaka activates on L1
26+
Nodes that are not upgraded correctly will stop syncing after activation.
2827

29-
- **proxyd**: Update to [v4.23.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.23.0) or greater (requires whitelisting `eth_blobBaseFee` RPC)
30-
- **op-challenger**: Update to [v1.7.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.7.0) if using permissionless fault proofs
28+
**NO action required if you:**
3129

32-
**Previous Upgrades**
33-
34-
- **Isthmus**: Active on May 9, 2025, 16:00:01 UTC
35-
- **Granite and Holocene**: Active on BOB mainnet
30+
- Use existing external RPC nodes directly
3631

3732
**More Info**
38-
For full details, please refer to the [Fusaka Upgrade Notice](https://docs.optimism.io/notices/fusaka-notice)
33+
For full details, please refer to the [Fusaka Upgrade Notice](https://docs.optimism.io/notices/fusaka-notice#for-node-operators)
3934
Feel free to reach out with any questions or concerns.
4035
:::
4136

@@ -47,7 +42,7 @@ To stay updated on node upgrades and announcements, join our [Telegram channel](
4742

4843
## Requirements
4944

50-
As of May 2025 we recommend you have at least the following hardware configuration to run a node:
45+
As of December 2025 we recommend you have at least the following hardware configuration to run a node:
5146

5247
- at least 8 GB RAM
5348
- an SSD, preferably NVME drive with at least 100 GB free

0 commit comments

Comments
 (0)