Skip to main content

Fusaka-enabled Parent Upgrade Notice

Note separate from ArbOS 50 release - learn more **here (coming later)**

Date of required actions

  • L1 Mainnet upgrades to Fusaka: Dec 3rd 2025
    • Applicable to Orbit chains & ArbOne/Nova operators
  • L1 Sepolia upgrades to Fusaka: October 14th 2025
    • Applicable to Orbit chains & ArbOne/Nova operators
  • Arb One/Nova upgrades to ArbOS 50 "Dia"
    • ArbOS 50 release - learn more **here (coming later)**

Required Node/Client Configurations for Orbit chains and ArbOne/Nova operators on Fusaka-enabled parent chain

LayerData AvailabilityFallback to blobs enabledNitro versionConsenus Layer Client
L2RollupN/A3.8.0 or 3.7.6See table below
L2AnyTrust / AltDAYes > Fallback to blobs3.8.0 or 3.7.6See table below
L2AnyTrust / AltDANo > Fallback to Calldata or disabledNo action requiredNo action required
L3RollupNo action neededNo action requiredNo action required
L3AnyTrust / AltDANo action neededNo action requiredNo action required

Required Consensus Client & Nitro Flags for Orbit chains and ArbOne/Nova operators that post blobs to Fusaka-enabled parent chain

ClientCompatible with NitroRequired Nitro FlagRequired Beacon Node Flag
PrysmNone--subscribe-all-data-subnets
LighthouseNone--supernode
Teku--parent-chain.blob-client.dangerous.skip-blob-proof-verification--p2p-subscribe-all-custody-subnets-enabled
LodestarNone--supernode
Erigon Caplin

To read more about PeerDAS changes and why Layer 2 network operators must connect to an Ethereum beacon chain node with historical blob data, see the historical blobs docs.