From e482ce6bacd85042037df63ce1652a455ffaa5b0 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 12:59:04 -0500 Subject: [PATCH 01/20] Adding partial for fusaka historical blobs --- docs/partials/_fusaka-historical-blobs.mdx | 71 +++++++++++++++++++++ docs/run-arbitrum-node/02-run-full-node.mdx | 4 ++ 2 files changed, 75 insertions(+) create mode 100644 docs/partials/_fusaka-historical-blobs.mdx diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx new file mode 100644 index 000000000..9774fa0e6 --- /dev/null +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -0,0 +1,71 @@ +--- +partial_type: content +title: 'Fusaka Historical Blobs Information' +description: 'Information and instructions for node and chain operators that will be impacted by the Fusaka upgrade for historical blob data.' +author: pete-vielhaber +last_reviewed: 2025-10-07 +--- + +import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; + + + +The Fulu consensus node upgrade in Fusaka will activate Ethereum’s PeerDAS ([EIP-7594](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia’s upgrade on October 14th and Mainnet targeting the week of December 3rd. PeerDAS optimizes data availability by not requiring all nodes to download all blob data, while ensuring network-wide data availability. + +Layer 2 network operators must connect to an Ethereum Beacon Chain node with historical blob data to ensure proper functioning of the Nitro node software, or risk failure in fetching blob data. + +## Impacted audiences + +Required action will be required from: RPC nodes, Arbitrum One / Nova node operators, Arbitrum (Orbit) chain node operators + +#### If you run a Nitro node and use an external L1 Ethereum Beacon chain RPC URL + +- Please confirm that your external L1 Beacon chain RPC provider has configured their L1 Beacon chain node to subscribe to all subnets **before the Ethereum Fusaka hard fork**. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. +- For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. + +#### If your external L1 Beacon chain RPC does not subscribe to all subnets: + +- Switch to a provider that does before the dates above. + +#### If you run a Nitro node and you also operate your own L1 Ethereum beacon chain node: + +- Add the new flag (see [table below](#specific-client-flags)) to your Beacon Node’s configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. +- For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. +- If you have not added the new flag before the above deadlines, please temporarily switch to an external L1 Beacon chain RPC URL while your local L1 Ethereum beacon chain node syncs up. + - **Note**: Ensure that the external L1 Beacon chain RPC provider you’re using subscribes to all subnets. +- Once your Beacon chain node is fully synchronized, you may switch back to your own L1 Beacon chain RPC URL (from an external L1 Beacon chain RPC URL). + +## L1 beacon chain node flags + +### Prysm Consensus Layer clients + +Prysm nodes have a new beacon node flag `--subscribe-all-data-subnets` that needs to be added to P2P options, refer to the [Prysm Docs: Command-line options](https://prysm.offchainlabs.com/docs/configure-prysm/parameters/). + +This flag is available as of Prysm v6.1.0 (and we recommend always upgrading to stay on the [latest stable Prysm releases](https://github.com/OffchainLabs/prysm/releases)). + +### Other Consensus Layer clients + +Other Consensus Layer nodes also have flags to ensure they sync data from across all subnets. + +**Note that the accuracy of the flags below**, including the corresponding versions that these flags support, has not been verified or confirmed by the Offchain Labs team. Please consult the respective release notes and documentation for non-Prysm Consensus Layer clients to ensure you’re adding the correct flags. + +### Specific client flags + +| Client | Flag | +| ---------- | --------------------------------------------- | +| Lighthouse | `--supernode` | +| Teku | `--p2p-subscribe-all-custody-subnets-enabled` | +| Grandine | `--subscribe-all-data-column-subnets` | +| Lodestar | `--supernode` | +| Nimbus | `--debug-peerdas-supernode` | + +## Checklist + +To maintain uninterrupted node operation and blob availability: + +- Add the appropriate flag for your CL client. +- Verify your Sepolia beacon endpoint’s configuration before October 14th. +- Verify your Mainnet beacon endpoint’s configuration before the first week of December. +- We recommend using temporary hosted beacon endpoints if updating the configuration cannot be made in time for release. + + diff --git a/docs/run-arbitrum-node/02-run-full-node.mdx b/docs/run-arbitrum-node/02-run-full-node.mdx index d793fa924..e08a4132a 100644 --- a/docs/run-arbitrum-node/02-run-full-node.mdx +++ b/docs/run-arbitrum-node/02-run-full-node.mdx @@ -61,6 +61,10 @@ We provide a summary of the available parameters here, but we recommend reading - Note that these parameters get ignored if a database already exists - When running more than one node, it's easier to manually download the different parts of the snapshot, join them into a single archive, and host it locally for your nodes. Please see [Downloading the snapshot manually](/run-arbitrum-node/nitro/03-nitro-database-snapshots.mdx#downloading-the-snapshot-manually) for instructions on how to do that. +import FusakaHistoricalBlobs from '../partials/_fusaka-historical-blobs.mdx'; + + + ### Required parameters The following list contains all the parameters needed to configure your node. Select the appropriate option depending on the chain you want to run your node for. From c22f74efe97475792d4e22b4548e69b1c072d6e0 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:17 -0500 Subject: [PATCH 02/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 9774fa0e6..5b3e64472 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -8,7 +8,7 @@ last_reviewed: 2025-10-07 import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; - + The Fulu consensus node upgrade in Fusaka will activate Ethereum’s PeerDAS ([EIP-7594](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia’s upgrade on October 14th and Mainnet targeting the week of December 3rd. PeerDAS optimizes data availability by not requiring all nodes to download all blob data, while ensuring network-wide data availability. From 1de3e6ab2b5ff56ab50a22c174e345193907582d Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:24 -0500 Subject: [PATCH 03/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 5b3e64472..7b1912302 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -10,7 +10,7 @@ import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; -The Fulu consensus node upgrade in Fusaka will activate Ethereum’s PeerDAS ([EIP-7594](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia’s upgrade on October 14th and Mainnet targeting the week of December 3rd. PeerDAS optimizes data availability by not requiring all nodes to download all blob data, while ensuring network-wide data availability. +The Fulu consensus node upgrade in Fusaka will activate Ethereum's PeerDAS ([`EIP-7594`](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia's upgrade on October 14th and Mainnet targeting the week of December 3rd. Layer 2 network operators must connect to an Ethereum Beacon Chain node with historical blob data to ensure proper functioning of the Nitro node software, or risk failure in fetching blob data. From 3634c63700480036d60f19d8f6efa97709548b8f Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:32 -0500 Subject: [PATCH 04/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 7b1912302..61426734b 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -12,7 +12,7 @@ import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; The Fulu consensus node upgrade in Fusaka will activate Ethereum's PeerDAS ([`EIP-7594`](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia's upgrade on October 14th and Mainnet targeting the week of December 3rd. -Layer 2 network operators must connect to an Ethereum Beacon Chain node with historical blob data to ensure proper functioning of the Nitro node software, or risk failure in fetching blob data. +Layer 2 network operators must connect to an Ethereum beacon chain node with historical blob data to ensure proper functioning of the Nitro node software, or risk failure in fetching blob data. ## Impacted audiences From 2e68570db19ba055d2bdee36ae006be31e606f9c Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:39 -0500 Subject: [PATCH 05/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 61426734b..94e163193 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -18,7 +18,7 @@ Layer 2 network operators must connect to an Ethereum beacon chain node with his Required action will be required from: RPC nodes, Arbitrum One / Nova node operators, Arbitrum (Orbit) chain node operators -#### If you run a Nitro node and use an external L1 Ethereum Beacon chain RPC URL +#### If you run a Nitro node and use an external L1 Ethereum beacon chain RPC URL - Please confirm that your external L1 Beacon chain RPC provider has configured their L1 Beacon chain node to subscribe to all subnets **before the Ethereum Fusaka hard fork**. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. From 22d9aa48baea0b3e281b30426f2f9c214e95ff74 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:45 -0500 Subject: [PATCH 06/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 94e163193..33ea1f281 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -20,7 +20,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera #### If you run a Nitro node and use an external L1 Ethereum beacon chain RPC URL -- Please confirm that your external L1 Beacon chain RPC provider has configured their L1 Beacon chain node to subscribe to all subnets **before the Ethereum Fusaka hard fork**. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. +- Confirm that your external L1 beacon chain RPC provider has configured their L1 beacon chain node to subscribe to all subnets **before the Ethereum Fusaka hard fork**. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. #### If your external L1 Beacon chain RPC does not subscribe to all subnets: From 735ecc4fe4803605685b686332abe5a72bbcceaa Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:54:56 -0500 Subject: [PATCH 07/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 33ea1f281..a2291cda8 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -23,7 +23,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera - Confirm that your external L1 beacon chain RPC provider has configured their L1 beacon chain node to subscribe to all subnets **before the Ethereum Fusaka hard fork**. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. -#### If your external L1 Beacon chain RPC does not subscribe to all subnets: +#### If your external L1 beacon chain RPC doesn't subscribe to all subnets: - Switch to a provider that does before the dates above. From fda714e0ea10a89e0f0f5e98ec7a644936d80d05 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:06 -0500 Subject: [PATCH 08/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index a2291cda8..ce9346c21 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -27,7 +27,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera - Switch to a provider that does before the dates above. -#### If you run a Nitro node and you also operate your own L1 Ethereum beacon chain node: +#### If you run a Nitro node and operate your own L1 Ethereum beacon chain node: - Add the new flag (see [table below](#specific-client-flags)) to your Beacon Node’s configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. From f5db2bacc056bee42f32f4ffa55987ff298da5dd Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:14 -0500 Subject: [PATCH 09/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index ce9346c21..5fc7fd3ad 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -29,7 +29,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera #### If you run a Nitro node and operate your own L1 Ethereum beacon chain node: -- Add the new flag (see [table below](#specific-client-flags)) to your Beacon Node’s configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. +- Add the new flag (refer to [specific client flags](#specific-client-flags)) to your beacon node's configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. - If you have not added the new flag before the above deadlines, please temporarily switch to an external L1 Beacon chain RPC URL while your local L1 Ethereum beacon chain node syncs up. - **Note**: Ensure that the external L1 Beacon chain RPC provider you’re using subscribes to all subnets. From 2031200e33223ebe675e257b7e5f09dc7eb88bfb Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:22 -0500 Subject: [PATCH 10/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 5fc7fd3ad..a374209c9 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -31,8 +31,8 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera - Add the new flag (refer to [specific client flags](#specific-client-flags)) to your beacon node's configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. -- If you have not added the new flag before the above deadlines, please temporarily switch to an external L1 Beacon chain RPC URL while your local L1 Ethereum beacon chain node syncs up. - - **Note**: Ensure that the external L1 Beacon chain RPC provider you’re using subscribes to all subnets. +- If you haven't added the new flag before the above deadlines, temporarily switch to an external L1 beacon chain RPC URL while your local Ethereum beacon chain node syncs up. + - **Note**: Ensure that the external L1 beacon chain RPC provider you're using subscribes to all subnets. - Once your Beacon chain node is fully synchronized, you may switch back to your own L1 Beacon chain RPC URL (from an external L1 Beacon chain RPC URL). ## L1 beacon chain node flags From 49dc8242d9a980a2b5712193ffaf317b09bdf3be Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:40 -0500 Subject: [PATCH 11/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index a374209c9..5ef5e5c00 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -33,7 +33,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. - If you haven't added the new flag before the above deadlines, temporarily switch to an external L1 beacon chain RPC URL while your local Ethereum beacon chain node syncs up. - **Note**: Ensure that the external L1 beacon chain RPC provider you're using subscribes to all subnets. -- Once your Beacon chain node is fully synchronized, you may switch back to your own L1 Beacon chain RPC URL (from an external L1 Beacon chain RPC URL). +- Once your beacon chain node is fully synchronized, you can switch back to your own L1 beacon chain RPC URL (from an external L1 beacon chain RPC URL). ## L1 beacon chain node flags From 50cafe04ed1260677fd27a61b5ef634eecd375bc Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:45 -0500 Subject: [PATCH 12/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 5ef5e5c00..11ab2d5dd 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -39,7 +39,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera ### Prysm Consensus Layer clients -Prysm nodes have a new beacon node flag `--subscribe-all-data-subnets` that needs to be added to P2P options, refer to the [Prysm Docs: Command-line options](https://prysm.offchainlabs.com/docs/configure-prysm/parameters/). +Prysm nodes have a new beacon node flag `--subscribe-all-data-subnets` that needs to be added to P2P options. Refer to the [Prysm command-line options documentation](https://prysm.offchainlabs.com/docs/configure-prysm/parameters/) for configuration details. This flag is available as of Prysm v6.1.0 (and we recommend always upgrading to stay on the [latest stable Prysm releases](https://github.com/OffchainLabs/prysm/releases)). From 61a7a5d3ef710f8c7480c0969f8cf936b17500dd Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:55:52 -0500 Subject: [PATCH 13/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 11ab2d5dd..69201296d 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -41,7 +41,7 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera Prysm nodes have a new beacon node flag `--subscribe-all-data-subnets` that needs to be added to P2P options. Refer to the [Prysm command-line options documentation](https://prysm.offchainlabs.com/docs/configure-prysm/parameters/) for configuration details. -This flag is available as of Prysm v6.1.0 (and we recommend always upgrading to stay on the [latest stable Prysm releases](https://github.com/OffchainLabs/prysm/releases)). +This flag is available as of Prysm v6.1.0. We recommend upgrading to the [latest stable Prysm releases](https://github.com/OffchainLabs/prysm/releases) to ensure you have the most recent features and security updates. ### Other Consensus Layer clients From 2548a57400fc368abf4328658295544bb70e1b65 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:56:11 -0500 Subject: [PATCH 14/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index 69201296d..d92c8e913 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -47,7 +47,7 @@ This flag is available as of Prysm v6.1.0. We recommend upgrading to the [latest Other Consensus Layer nodes also have flags to ensure they sync data from across all subnets. -**Note that the accuracy of the flags below**, including the corresponding versions that these flags support, has not been verified or confirmed by the Offchain Labs team. Please consult the respective release notes and documentation for non-Prysm Consensus Layer clients to ensure you’re adding the correct flags. +**Note**: The Offchain Labs team hasn't verified the accuracy of the flags below, including the corresponding versions that support these flags. Consult the respective release notes and documentation for non-Prysm consensus layer clients to ensure you're adding the correct flags. ### Specific client flags From fc51ffecbab8de0da57777e64b338e3d9af082b0 Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:56:20 -0500 Subject: [PATCH 15/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index d92c8e913..e53b74702 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -63,7 +63,7 @@ Other Consensus Layer nodes also have flags to ensure they sync data from across To maintain uninterrupted node operation and blob availability: -- Add the appropriate flag for your CL client. +- Add the appropriate flag for your consensus layer client. - Verify your Sepolia beacon endpoint’s configuration before October 14th. - Verify your Mainnet beacon endpoint’s configuration before the first week of December. - We recommend using temporary hosted beacon endpoints if updating the configuration cannot be made in time for release. From ec579aafa35e90f48e4de30e08ca05c767ead32b Mon Sep 17 00:00:00 2001 From: Pete Date: Tue, 7 Oct 2025 14:56:31 -0500 Subject: [PATCH 16/20] Update docs/partials/_fusaka-historical-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- docs/partials/_fusaka-historical-blobs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/partials/_fusaka-historical-blobs.mdx index e53b74702..ac6733a74 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/partials/_fusaka-historical-blobs.mdx @@ -66,6 +66,6 @@ To maintain uninterrupted node operation and blob availability: - Add the appropriate flag for your consensus layer client. - Verify your Sepolia beacon endpoint’s configuration before October 14th. - Verify your Mainnet beacon endpoint’s configuration before the first week of December. -- We recommend using temporary hosted beacon endpoints if updating the configuration cannot be made in time for release. +- If you can't update your configuration in time, we recommend using temporary hosted beacon endpoints. From 9cc747d51cec002ecec8bc8f026401c4f746ce8f Mon Sep 17 00:00:00 2001 From: Pete Date: Thu, 16 Oct 2025 09:08:49 -0500 Subject: [PATCH 17/20] Adding new page for historical blobs; adding to sidebar --- docs/run-arbitrum-node/02-run-full-node.mdx | 6 +++-- .../beacon-nodes-historical-blobs.mdx} | 23 +++++++++---------- sidebars.js | 5 ++++ 3 files changed, 20 insertions(+), 14 deletions(-) rename docs/{partials/_fusaka-historical-blobs.mdx => run-arbitrum-node/beacon-nodes-historical-blobs.mdx} (82%) diff --git a/docs/run-arbitrum-node/02-run-full-node.mdx b/docs/run-arbitrum-node/02-run-full-node.mdx index e08a4132a..a32242510 100644 --- a/docs/run-arbitrum-node/02-run-full-node.mdx +++ b/docs/run-arbitrum-node/02-run-full-node.mdx @@ -61,9 +61,11 @@ We provide a summary of the available parameters here, but we recommend reading - Note that these parameters get ignored if a database already exists - When running more than one node, it's easier to manually download the different parts of the snapshot, join them into a single archive, and host it locally for your nodes. Please see [Downloading the snapshot manually](/run-arbitrum-node/nitro/03-nitro-database-snapshots.mdx#downloading-the-snapshot-manually) for instructions on how to do that. -import FusakaHistoricalBlobs from '../partials/_fusaka-historical-blobs.mdx'; +:::warning Fusaka upgrade: Historical blobs - +If running a beacon node, historical data will now be in blobs. To make this transition to using historical blobs refer to the [Historical Blobs: Beacon Nodes](/run-arbitrum-node/beacon-nodes-historical-blobs.mdx) guide. + +::: ### Required parameters diff --git a/docs/partials/_fusaka-historical-blobs.mdx b/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx similarity index 82% rename from docs/partials/_fusaka-historical-blobs.mdx rename to docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx index ac6733a74..a0b5f3f8d 100644 --- a/docs/partials/_fusaka-historical-blobs.mdx +++ b/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx @@ -1,15 +1,12 @@ --- -partial_type: content -title: 'Fusaka Historical Blobs Information' -description: 'Information and instructions for node and chain operators that will be impacted by the Fusaka upgrade for historical blob data.' -author: pete-vielhaber -last_reviewed: 2025-10-07 +title: 'Beacon Nodes: Historical Blobs' +description: Learn more about the impacts of the Fusaka upgrade when running a beacon node. +author-objective: Build a how-to to guide users in how to transition to using historical blobs. +reader-audience: Technical readers who are familiar with command lines and familiar with Arbitrum and Ethereum +reader-task: Learn how to upgrade to using historical blobs post the Fusaka upgrade when running a beacon node. +content_type: overview --- -import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; - - - The Fulu consensus node upgrade in Fusaka will activate Ethereum's PeerDAS ([`EIP-7594`](https://eips.ethereum.org/EIPS/eip-7594)), with Sepolia's upgrade on October 14th and Mainnet targeting the week of December 3rd. Layer 2 network operators must connect to an Ethereum beacon chain node with historical blob data to ensure proper functioning of the Nitro node software, or risk failure in fetching blob data. @@ -47,7 +44,11 @@ This flag is available as of Prysm v6.1.0. We recommend upgrading to the [latest Other Consensus Layer nodes also have flags to ensure they sync data from across all subnets. -**Note**: The Offchain Labs team hasn't verified the accuracy of the flags below, including the corresponding versions that support these flags. Consult the respective release notes and documentation for non-Prysm consensus layer clients to ensure you're adding the correct flags. +:::warning Verification + +The Offchain Labs team hasn't verified the accuracy of the flags below, including the corresponding versions that support these flags. Consult the respective release notes and documentation for non-Prysm consensus layer clients to ensure you're adding the correct flags. + +::: ### Specific client flags @@ -67,5 +68,3 @@ To maintain uninterrupted node operation and blob availability: - Verify your Sepolia beacon endpoint’s configuration before October 14th. - Verify your Mainnet beacon endpoint’s configuration before the first week of December. - If you can't update your configuration in time, we recommend using temporary hosted beacon endpoints. - - diff --git a/sidebars.js b/sidebars.js index bfe9aa0da..cd004214e 100644 --- a/sidebars.js +++ b/sidebars.js @@ -521,6 +521,11 @@ const sidebars = { id: 'run-arbitrum-node/run-feed-relay', label: 'Run a feed relay', }, + { + type: 'doc', + id: 'run-arbitrum-node/beacon-nodes-historical-blobs', + label: 'Beacon nodes: Historical blobs', + }, { type: 'html', value: From 3685bdf8787646700d6d4c372b38c46396e0b6c4 Mon Sep 17 00:00:00 2001 From: Pete Date: Thu, 16 Oct 2025 09:09:09 -0500 Subject: [PATCH 18/20] vercel redirect --- vercel.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/vercel.json b/vercel.json index a22c01a13..3392afe3e 100644 --- a/vercel.json +++ b/vercel.json @@ -235,6 +235,11 @@ "destination": "/build-decentralized-apps/reference/mainnet-risks", "permanent": false }, + { + "source": "/(docs/partials/_fusaka-historical-blobs/?)", + "destination": "/(docs/run-arbitrum-node/beacon-nodes-historical-blobs/?)", + "permanent": false + }, { "source": "/(docs/partials/glossary/_fast-exit--liquidity-exit/?)", "destination": "/(docs/partials/glossary/_fast-exit-liquidity-exit/?)", From 0cc8196a197c16b34c6957546161187e9435a883 Mon Sep 17 00:00:00 2001 From: Pete Date: Fri, 17 Oct 2025 08:05:08 -0500 Subject: [PATCH 19/20] Changing note style; sidebar title --- docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx | 8 +++++++- sidebars.js | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx b/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx index a0b5f3f8d..e0fd9e2d4 100644 --- a/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx +++ b/docs/run-arbitrum-node/beacon-nodes-historical-blobs.mdx @@ -29,7 +29,13 @@ Required action will be required from: RPC nodes, Arbitrum One / Nova node opera - Add the new flag (refer to [specific client flags](#specific-client-flags)) to your beacon node's configuration before the Ethereum Fusaka hard fork. For chains that post data to Ethereum Sepolia, the Ethereum Sepolia Fusaka hard fork is expected on October 14th, 2025. - For chains that post data to Ethereum Mainnet, the Ethereum Mainnet Fusaka hard fork is expected around the first week of December 2025. - If you haven't added the new flag before the above deadlines, temporarily switch to an external L1 beacon chain RPC URL while your local Ethereum beacon chain node syncs up. - - **Note**: Ensure that the external L1 beacon chain RPC provider you're using subscribes to all subnets. + +:::info Note + +Ensure that the external L1 beacon chain RPC provider you're using subscribes to all subnets. + +::: + - Once your beacon chain node is fully synchronized, you can switch back to your own L1 beacon chain RPC URL (from an external L1 beacon chain RPC URL). ## L1 beacon chain node flags diff --git a/sidebars.js b/sidebars.js index cd004214e..4c33e9e64 100644 --- a/sidebars.js +++ b/sidebars.js @@ -524,7 +524,7 @@ const sidebars = { { type: 'doc', id: 'run-arbitrum-node/beacon-nodes-historical-blobs', - label: 'Beacon nodes: Historical blobs', + label: 'Historical blobs', }, { type: 'html', From 044eeb37bec2b9db9e4507d05ff67d67b175d265 Mon Sep 17 00:00:00 2001 From: Pete Date: Fri, 17 Oct 2025 08:07:12 -0500 Subject: [PATCH 20/20] Minor verbiage change --- docs/run-arbitrum-node/02-run-full-node.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/run-arbitrum-node/02-run-full-node.mdx b/docs/run-arbitrum-node/02-run-full-node.mdx index a32242510..df6b8b565 100644 --- a/docs/run-arbitrum-node/02-run-full-node.mdx +++ b/docs/run-arbitrum-node/02-run-full-node.mdx @@ -63,7 +63,7 @@ We provide a summary of the available parameters here, but we recommend reading :::warning Fusaka upgrade: Historical blobs -If running a beacon node, historical data will now be in blobs. To make this transition to using historical blobs refer to the [Historical Blobs: Beacon Nodes](/run-arbitrum-node/beacon-nodes-historical-blobs.mdx) guide. +If running a beacon node, historical data will now be in blobs. To make this transition to using historical blobs refer to the [Historical Blobs for Beacon Nodes](/run-arbitrum-node/beacon-nodes-historical-blobs.mdx) guide. :::