Anza Advances Solana Agave Client with Series of V4 Pre-Releases
The development team pushed v4.4.0-beta.0 and two v4.5.0 alpha builds to GitHub between Sept. 28 and Oct. 8.
At a glance
- What happened
- Anza published three pre-release versions of the Agave client on GitHub between Sept. 28 and Oct. 8.
- Why it matters
- The concurrent progression of the v4.4.0 beta and v4.5.0 alpha tracks signals continuous technical updates to the Solana network's validator software.
- Who is affected
- Solana developers and node operators using the Agave client.
- What's next
- No next step announced.
- Primary source
- Agave (Solana) releases: Release v4.5.0-alpha.2
Key points
- Anza published Agave Release v4.5.0-alpha.2 on Oct. 8, containing eight assets and tied to commit 9365a53.
- The v4.5.0-alpha.1 build was released on Oct. 3 with two assets.
- Release v4.4.0-beta.0 was published on Sept. 28, after which 65 commits were made to the master branch.
Anza is accelerating the development cycle of the Agave client for Solana, issuing three separate pre-releases across two major version tracks in an 11-day window [1, 2, 3]. The successive updates, spanning the v4.4.0 and v4.5.0 series, highlight continuous active iteration on the core validator software originally forked from Solana Labs [2, 3].
The v4.5.0 Alpha Progression
Development on the v4.5.0 track has entered the alpha testing phase. Anza published Release v4.5.0-alpha.1 on Oct. 3 2. The release was tied to commit ffa314a and included two repository assets 2.
Five days later, on Oct. 8, the team followed up with Release v4.5.0-alpha.2 1. This second alpha build was linked to commit 9365a53 and contained eight assets 1. The repository recorded one additional commit to the master branch subsequent to the alpha.2 release 1.
The v4.4.0 Beta Track
Concurrent with the alpha builds for v4.5.0, Anza is advancing the v4.4.0 series through its beta phase. The team released v4.4.0-beta.0 on Sept. 28 3. This build, bound to commit 98535e5, also featured eight associated assets 3. Following the beta.0 release, the master branch logged 65 further commits 3.
Implications
The dual-track pre-release strategy indicates that Anza is simultaneously finalizing the v4.4.0 series for potential mainnet deployment while already laying the groundwork for the subsequent v4.5.0 architecture [1, 3]. All three releases were verified on GitHub via the same GPG key ID (B5690EEEBB952194), maintaining cryptographic continuity across the software updates [1, 2, 3].
What to Watch
Market participants and node operators should monitor the Anza repository for the transition of the v4.4.0 track from beta to a stable release candidate. Additionally, further alpha iterations for v4.5.0 may be published before that branch advances to its own beta phase.
Sources
- [1] Release v4.5.0-alpha.2 — Agave (Solana) releases, October 8, 2026
- [2] Release v4.5.0-alpha.1 — Agave (Solana) releases, October 3, 2026
- [3] Release v4.4.0-beta.0 — Agave (Solana) releases, September 28, 2026
Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.