Technologie & IA
Anza releases the first Agave 5.0 alpha for testing only
Solana’s validator client switches its default account storage to SplitFile in the November 19 prerelease. Anza excludes mainnet, the public testnet, and production hosts from its intended use.

A prerelease for use outside public networks
Anza published Agave 5.0.0-alpha.1 on November 19, 2026. The version number denotes the first alpha in the 5.0 series of the Solana validator client. The accompanying notice limits this version to testing. The team asks users to keep it off mainnet, the public testnet, and production hosts. The release provides a version to examine and test, without announcing a date for a stable release.
The changelog accompanying the code distinguishes three channels. It places series 5.0 in the development channel, series 4.5 in beta, and series 4.4 in stable. The same file still lists version 5.0.0 in the section for releases that are not final. That information places the alpha in the development cycle. It does not change the software run by validators on public networks.
SplitFile becomes the default account storage format
The most visible configuration change in the 5.0 changelog concerns account storage. SplitFile becomes the default file format. The release notes also say writes to SplitFile account files are buffered. They separately list a change that splits account reads into metadata reads and data reads. These changes affect how the client stores and retrieves local state.
The changelog also removes several account database configuration options, including ones related to storage access, cache limits, and thread counts. The team gives no estimate in this notice of disk space, memory use, or throughput on a production host. An isolated test can show startup configuration and read and write behavior within the limits Anza sets for the release.
Preparations for the format of block fragments
The release also brings together work on SIMD 504, a proposal concerning the format of fragments used to transmit blocks. The notes cite the addition of the transmission format to the code and a check for duplicate fragments when they are inserted in the local ledger. They also describe tests associated with the activation mechanism. Including these changes in an alpha gives no date for activation on a public network.
Other changes concern the encoding of certain instructions. The notes cite the use of wincode in the cost model to read system instructions and in the program loader to encode and decode instructions. These are specific parts of the code identified in the notice. For now, the release documents Anza’s work on the 5.0 series and the changes to test in an isolated environment.
