What is Agave
Agave serves as the main validator client for Solana, meaning it's the software that validators utilize to vote on consensus, produce blocks and validate transactions. The Agave codebase is written in Rust and is maintained by Anza, a Solana Labs spin-off from early 2024. Agave was the original Solana Labs client, renamed in 2024 following the spin-off and rebranding of the software.
To visualize it, think of a familiar diner your community frequented for years. One day, the sign changes, the management team rotates, and suddenly, there's a new sign above the door. The regulars hardly notice because the burgers still taste the same. That's Agave: Solana Labs' client renamed, with most of the network not even bothering to update their preferred menu.
What Agave Is Doing Throughout 2026
The most recent major release, Agave v3.0, was deployed at the end of 2025, and the biggest upgrade to the client since Agave replaced the original Solana Labs client. The update added support for XDP networking, which refers to the eXpress Data Path networking feature of the Linux kernel. This allows validators to process Turbine (the block- and transaction- data distribution technology for Solana) directly on the network interface card, resulting in higher throughput and latency improvements required for SIMD-0286, a Solana Improvement Proposal increasing the total number of compute units (CU) per block from 60 to 100 million. In other words, each 400ms block of processing is now ~66% bigger.
Agave 4.x releases will continue through 2026, and Anza is currently preparing releases to halve the current slot time (400ms) from 200ms, and increase the maximum size of transactions in future Agave releases. All Agave upgrades follow the same process: Anza releases the software version, validators test on the devnet testnet, then a majority of stake upgrades over the next few days.
Here's the thing most new Solana users don't realize: only a relatively small amount of stake is using the base Agave client as of mid-2026. In fact, more than 70% of all stake is being run on Jito Solana, an offshoot of Agave that adds an auction mechanism to optimize MEV (profit taken when optimizing transaction ordering) distribution to validators and stakers. Agave itself is the low single digits, while the remainder of the client diversity comes from the newly released Firedancer client with the target to reach 20% as of mid-2026. This is not an issue because Jito runs off an Agave fork so, in effect, Agave runs 75% of the network.
How Agave Stacks Up Against Geth for Ethereum
Geth is the nearest comparison to Solana's Agave as it's the original Ethereum consensus client that most of the rest of the infrastructure around the blockchain is built off. Geth has been pushed down for years as one client running >66% of the entire network is dangerous due to the potential for a smart contract or bug causing it to lock up a chain and validate it as final. Agave had its close call to this as several outages that Solana experienced in 2022 can be traced back to a bug in the only client being used, and the precursor to Agave as mentioned above.
The key distinction between Solana's Agave and Ethereum's Geth is in the diversity of consensus client implementation. While Ethereum has six main consensus clients maintained by different teams, for Solana, Agave was the only consensus client for many years until Firedancer was able to make significant improvements. While there has been some discussion that Jito should be counted as its own client, it's more appropriate to consider it as Agave because the only major difference is in how blocks are created. The client diversity is what counts for the purpose of consensus. As of mid-2026, Jito + Agave make up roughly 75% of stake on the Solana mainnet. It isn't until the Firedancer release can reach it's target of 50% by the end of 2026 will Solana have any major issues, the same issues Ethereum is currently working to resolve for the network.
Why Agave is Important to Solana
This means that every swap through Jupiter, NFT transaction through Phantom, or stake delegation through Marinade is validated, ordered, and voted on by an Agave client on the majority of nodes in the Solana Network. If you were to buy the hottest new memecoin at the time of launch right now, the chances of your transaction being validated by the current leader of Solana, and the probability of the Solana transaction being included in a 100M CU block (something Agave v3.0 made possible), means the validator is running Jito's Agave fork. The release cycle is, in effect, the roadmap for the entire network, which is why Solana Compass tracks every Agave release by which validator is on what version.
The downside is clear: One entity, Anza, controls the underlying code of Agave (which 95%+ of validators are running), meaning the majority of the network would be down immediately should any significant bugs be introduced into the codebase. Client diversity via Firedancer is the solution, not a done deal.
Is Agave the new Solana Labs client?
Agave does not replace the Solana Labs client in code base, it was only the name that was changed and the client was renamed following a spin-off. The client was simply updated to the new version when the upgrade to Agave was implemented.
