You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/docs/bob-chain/full-node.md
+9-14Lines changed: 9 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,37 +5,32 @@ sidebar_label: Run a Full Node
5
5
6
6
# Run a Full Node
7
7
8
-
:::warning Upcoming BOB Fusaka Readiness Upgrade – October 14, 2025 (Sepolia), Early December 2025 (Mainnet)
8
+
:::warning Fusaka Activation on Ethereum Mainnet
9
9
**What's Included in the Upgrade**
10
10
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.
11
11
12
12
**Important Dates**
13
13
14
14
- 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
16
16
17
17
**Required Actions for Node Operators**
18
18
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:
20
20
21
21
-**op-node**: Update to version [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2)
22
22
-**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
24
23
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)
26
25
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.
28
27
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:**
31
29
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
36
31
37
32
**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)
39
34
Feel free to reach out with any questions or concerns.
40
35
:::
41
36
@@ -47,7 +42,7 @@ To stay updated on node upgrades and announcements, join our [Telegram channel](
47
42
48
43
## Requirements
49
44
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:
51
46
52
47
- at least 8 GB RAM
53
48
- an SSD, preferably NVME drive with at least 100 GB free
0 commit comments