Solana (SOL) Validators Must Upgrade Before Epoch 1079

By Nodora News · 6 November 2026 · Updated 6 November

Anza told Solana (SOL) validators to install Agave 4.4.1 or Firedancer 26.10.6 before epoch 1079 around 13:30 UTC on Nov. 6 or risk forking off.

Anza, the engineering firm behind Solana's Agave validator client, has issued an urgent upgrade call to Solana (SOL) mainnet operators. Nodes that have not installed Agave 4.4.1 — or Firedancer v26.10.6 for operators on Jump Crypto's alternative client — are planned to fork off when epoch 1079 begins, estimated at about 13:30 UTC on Friday, Nov. 6, 2026.

The warning went out on Thursday, Nov. 5, giving operators roughly a day to patch before the epoch boundary. Solana Status backed the same deadline and named the feature gate that is planned to activate at that turn.

Key takeaways

• Anza told Solana (SOL) mainnet validators to upgrade to Agave 4.4.1 immediately or risk being forked off at epoch 1079.
• Epoch 1079 is estimated to start around 13:30 UTC on Nov. 6, 2026.
• Firedancer operators need version 26.10.6 instead of Agave.
• The patch applies a minimum loaded-data size to loader-v3 ProgramData accounts ahead of feature gate activation.
• The requirement covers staked validators and unstaked nodes, including RPC servers that wallets and apps read from.

What Anza told Solana (SOL) validators

In a Nov. 5 post to mainnet-beta validators, Anza wrote that an "URGENT UPGRADE to Agave 4.4.1 is recommended or you will be forked off," and told operators to "Upgrade now and monitor your node." The Agave v4.4.1 release was published the same day as a stable build recommended for mainnet-beta, testnet and devnet.

Solana Status posted shortly afterward that all Solana mainnet staked and unstaked validators must upgrade to Agave v4.4.1 or Firedancer v26.10.6 before epoch 1079 begins. It also identified feature gate `8whkDenELnfwYLirBc4Wb4H2Z1z5K7tiykpdxJS7cWg1` as planned for activation at that epoch boundary.

A feature gate is Solana's switch for turning a protocol rule on for the whole network at a set epoch. Once it flips, patched and unpatched software can evaluate the same transactions differently. That divergence is what "fork off" means here: an unpatched node stops following the chain the rest of the network agrees on.

What Agave 4.4.1 changes for loader-v3 ProgramData

The centerpiece of Agave 4.4.1 is a runtime fix that applies a minimum loaded-data size to loader-v3 ProgramData accounts. Loader-v3 is Solana's upgradeable program loader. It stores each upgradeable program's executable code in a separate ProgramData account, and Solana caps how much account data a single transaction may load.

The change landed fast. Pull request #16769 was merged on Nov. 5, 2026, with a v4.4 backport (#16775) the same day that adds support for a feature named `loaderv3_programdata_size_floor`. The point release also includes build and CI housekeeping, including two dependency-audit ignores; those do not change validator consensus behavior.

Firedancer v26.10.6, described as a mainnet-ready release, adds support for the same size-floor feature, so operators on either client had a patched build available on Nov. 5.

Agave 4.4.1 follows quickly after Anza recommended Agave v4.4.0 for general mainnet adoption on Oct. 30, 2026, after a phased stake rollout. Operators already on 4.4.0 are one patch version away.

Why the Nov. 6 epoch 1079 deadline matters

Epoch timing is approximate but well constrained. Epoch 1078 started at about 11:54 UTC on Nov. 5, and recent epochs have lasted roughly 25.7 hours, which puts the 1079 boundary near 13:30 UTC on Nov. 6 — early Saturday morning in Australia/Melbourne (about 00:30 AEDT on Nov. 7).

If a validator forks off:

• Its votes stop counting toward consensus.
• Delegated SOL on that validator stops earning until the operator upgrades and rejoins the canonical chain.
• Unstaked RPC nodes that diverge can serve stale or incorrect chain state to wallets and apps.

At the start of epoch 1078, Solana Compass network data put roughly 432 million SOL of active stake across about 694 validators. The upgrade call applies to all of them, plus unstaked infrastructure.

This is a compatibility patch tied to a planned feature activation, not a response to an attack or exploit. Network liveness for well-upgraded stake should continue; the risk sits with operators who miss the window and with any apps that rely on unpatched RPC endpoints.

Solana (SOL) market reaction and prices

The upgrade call landed into a weak broader crypto session driven by a U.S. technology-stock sell-off and heavy futures liquidations, rather than by the Agave notice itself. Spot prices on OKX around the time of writing showed:

• Solana (SOL): about $89.38, down roughly 6.7% over 24 hours (24h range about $88.29–$97.09).
• Bitcoin (BTC): about $75,676, down roughly 5.9%.
• Ether (ETH): about $2,225, down roughly 8.1%.

SOL's move tracked the wider risk-off tape more than any single Solana headline. Still, validator-upgrade deadlines matter for network reliability, which is why operators treat Anza and Solana Status advisories as operationally urgent even when spot prices are driven by macro flows. Live Solana pricing is on the Nodora charts page.

What to watch next for Solana (SOL) and epoch 1079

• Gate activation: confirmation from Anza or Solana Status that feature gate `8whkDenELnfwYLirBc4Wb4H2Z1z5K7tiykpdxJS7cWg1` activated at the epoch 1079 boundary.
• Delinquent stake and skipped slots: whether unpatched stake shows up as delinquent after the turn, and whether slot skip rates rise briefly.
• RPC health: whether wallets and apps report stale reads from operators who missed the Firedancer 26.10.6 or Agave 4.4.1 cutover.
• Client mix: how quickly remaining Agave stake moves from 4.4.0 to 4.4.1, and how Firedancer share behaves through the boundary.

The Solana ecosystem has also been busy on the product side this week, including Samsung Wallet's USDC rollout for eligible U.S. Galaxy users and Schroders' tokenized emerging-market bond strategy on Solana. Those are separate from today's client-compatibility deadline, which is about keeping validators and RPC nodes on the same consensus rules when the loader-v3 size floor turns on.

For now, the instruction from Anza and Solana Status is simple: upgrade before epoch 1079, then watch the node through the boundary.

This article is for information only and is not financial advice.

#Solana #Agave #validators #Firedancer #epoch 1079

This article is general information, not financial advice.