Overview
As part of the Fulu consensus node upgrade in Fusaka, Ethereum’s PeerDAS (EIP-7594) will be activated. ****This change optimizes data availability by removing the requirement for all nodes to download all blob data, while still guaranteeing full data availability network-wide.
However, this means that node operators for Layer 2 networks, such as Arbitrum One and other Arbitrum L2 chains, will need to upgrade to support PeerDAS.
Failure to act on these will result in Arbitrum L2 Nitro nodes →
- failing to fetch blob data properly from Ethereum if the proper L1 Beacon Chain flags are not set (Sepolia or Mainnet).
- failing to post batches to Ethereum if the proper Arbitrum Nitro node version is not used (Sepolia or Mainnet).
- failing to post assertions to Ethereum if Nimbus is used to estimate L1 gas (Sepolia or Mainnet).
Actions Required for Nitro Node Operators
Issue 1: L2 Inbox reader issues syncing from batches posted on Fusaka-enabled parent chains
Issue 2: L2 Batch posting issues when trying to post a batch on a Fusaka enabled parent chain
Issue 3: L2 Arbitrum staked proposers/validators may face issues posting assertions to L1 if Nimbus consensus layer client is used