Anza Warns Solana Validators Face a Fork Without Agave 4.4.1

Anza urged Solana mainnet-beta validators to install Agave 4.4.1 before epoch 1079, warning that nodes still running without the patch were scheduled to be forked out of the network.

The Solana development team tied the urgent release to a minimum loaded-data-size limit for loader-v3 ProgramData accounts. The requirement applies to those accounts under Agave 4.4.1, the version named in the notice.

Epoch 1079 was expected around 8:30 a.m. ET (13:30 UTC) Friday, Nov. 6, roughly 9:30 p.m. in Beijing. Validators that had not installed the update by that point faced the risk of being separated from the network through a fork.

The alert concerns validator software on Solana's mainnet-beta environment. For operators, it links a software change to a fixed network deadline: the required update is Agave 4.4.1, and the cutoff is epoch 1079. The notice describes a network fork as the consequence for unpatched nodes, putting software version and timing at the center of the warning.