Skip to content

Commit 8c9cf3c

Browse files
Merge pull request #2895 from OffchainLabs/f-notice-update
docs: fusaka-notice-update
2 parents 96f299c + 17859a8 commit 8c9cf3c

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

docs/notices/fusaka-upgrade-notice.mdx

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ The following dates are relevant for Arbitrum chain operators.
2323

2424
| Date | Network upgrade | Affected audience |
2525
| ---------------------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
26-
| `Nov 20th 2025, 17:00:00 UTC` | Arbitrum Sepolia upgrade to [ArbOS 51](docs/run-arbitrum-node/arbos-releases/arbos51.mdx) | Node operators for Arbitrum Sepolia |
26+
| `Nov 20th 2025, 17:00:00 UTC` | Arbitrum Sepolia upgrade to ArbOS 50 | Node operators for Arbitrum Sepolia |
27+
| `Dec 1st 2025, 17:00:00 UTC` | Arbitrum Sepolia upgrade to [ArbOS 51](docs/run-arbitrum-node/arbos-releases/arbos51.mdx) | Node operators for Arbitrum Sepolia |
2728
| `Jan 8th, 2026, 17:00:00 UTC (proposed)` | Arbitrum One/Nova upgrade to [ArbOS 51](docs/run-arbitrum-node/arbos-releases/arbos51.mdx) | Node operators for Arbitrum One/Nova |
2829
| `Oct 14th 2025, 07:36:00 UTC` | Ethereum Sepolia Fusaka hard fork | Node operators for Arbitrum chains settling on Ethereum Sepolia (Orbit L2s, Arbitrum Sepolia) |
2930
| `Dec 3rd 2025, 21:49:11 UTC` | Ethereum Mainnet Fusaka hard fork | Node operators for Arbitrum chains settling on Ethereum Mainnet (Orbit L2s, Arbitrum One/Nova) |
@@ -40,6 +41,12 @@ Outlined below are different types of Arbitrum chains, along with node software
4041
| **L3** | **Rollup** | N/A | No nitro update required | Doesn't require historical blob data |
4142
| **L3** | **AnyTrust / AltDA** | Enabled or Disabled | No nitro update required | Doesn't require historical blob data |
4243

44+
:::warning Exceptions
45+
46+
For batch posters settling to mainnet Ethereum, Nitro >=3.8.0 is required.
47+
48+
:::
49+
4350
### How to ensure your node has access to all historical blob data and blob data from all subnets
4451

4552
#### If you run a Nitro node and use an external L1 Ethereum beacon chain RPC:

0 commit comments

Comments
 (0)