Anza, the engineering firm behind the Agave validator client, is urging Solana mainnet-beta operators to upgrade to Agave 4.4.1 immediately, warning that validators running older versions risk being forked off the network when epoch 1079 begins.
The epoch transition is expected at approximately 13:30 UTC on Nov. 6, 2026. Anza issued its advisory on Nov. 5, 2026, leaving operators roughly a day to act.
What the upgrade contains
The centerpiece of Agave 4.4.1 is a patch that standardizes the data size for loader-v3 ProgramData accounts. Anza has flagged the change as a critical fix rather than an optional improvement.
The patch is required for compatibility with an upcoming feature gate activation. Feature gates are Solana's mechanism for switching on protocol changes at a set moment.
Validators running earlier versions face exclusion from consensus and from network rewards once epoch 1079 starts.
A fast follow to v4.4.0
The release follows closely on Agave v4.4.0, which Anza tagged as stable and recommended for general mainnet use on Oct. 30, 2026. That version went through a phased rollout, with the share of stake running it increased gradually from 10% to 20% before Anza issued a broad recommendation.
Operators not running Agave have an alternative: the Firedancer validator client, in version 26.10.6, has been confirmed to meet the new requirements.
Why loader-v3 matters
Loader-v3 handles how upgradeable programs are deployed and stored on Solana. The focus on its ProgramData accounts indicates the protocol is preparing for more advanced changes that could potentially enhance operational efficiency and compatibility with new features, while core economic stability and block production rules are expected to remain intact.
If enough validators miss the upgrade, network liveness and consensus participation could be disrupted.
What it means for operators
For validator operators, the choice is direct: upgrade to Agave 4.4.1 or Firedancer 26.10.6, or risk losing rewards and a place in consensus once epoch 1079 begins. The tight window between the Nov. 5 advisory and the expected epoch boundary is the part worth watching for operators running complex infrastructure.
