Anza

Anza is the software company that builds the core of the Solana blockchain. Its main product is Agave, the validator client that most of the network runs. A validator client is the program a node runs to process transactions and vote on blocks. Former Solana Labs staff launched Anza on 30 January 2024, and it took over the code that Solana Labs wrote. Anza also designed Alpenglow, a new way for the network to agree on blocks that aims to make them final in about 150 milliseconds. It makes free tools for app builders too, such as Pinocchio and Solana Kit. Anza is a company with no token of its own. It has no link to the other brands and places that share the name.

How Anza ships changes to Solana

Anza writes open-source code, and the people who run Solana's nodes choose to install it. Nothing Anza ships can change Solana on its own. A change takes hold only when enough nodes run the new release and the feature is switched on.

The path has three steps. First, the change is written up as a Solana Improvement Document, or SIMD. This is a public proposal that other teams can read and push back on. Next, Anza builds the change into an Agave release behind a "feature gate", a switch that is off by default. Last, the gate is turned on, first on the test networks and then on mainnet. Every node applies the change at the same moment, at the start of an epoch.

The slot-time cut shows how this plays out. SIMD-0525 halved the time between blocks from 400ms to 200ms in four 50ms steps, each gated separately. Anza confirmed the last step went live on mainnet on 9 October 2026, as covered in our report on the 200ms activation.

Anza publishes release schedules, patch notes and planned cluster restarts on its blog and in its GitHub repositories, so operators can plan upgrades ahead of time.

Agave validator client: releases, requirements and setup

Agave is the original Solana validator software, now kept up by Anza. It is written in Rust and is free to use under the Apache 2.0 licence. Anza calls it "Solana's majority validator client". Anyone can download it and run a node.

Anza forked the Solana Labs code into its own repository on 2 March 2024, and development has happened in anza-xyz/agave since then. The main program is called agave-validator, alongside tools such as agave-ledger-tool and agave-install.

Releases in 2026 have moved quickly:

• Agave 4.0, a mainnet upgrade candidate in May 2026, made XDP networking ready for production. XDP is a Linux feature that lets a validator forward block data without the usual operating-system overhead. Anza's 4.0 patch notes say it cut the retransmit step from about 600ms to under 1ms. The release also removed UDP transaction ingestion in favour of QUIC.
• Agave 4.2, with mainnet feature activations from 17 August 2026, carried the 200ms slot time, a 90% rent cut and larger transactions, according to the Solana Foundation's 4.2 release overview.
• Agave 4.3, recommended for mainnet validators from 21 September 2026, is the release that carries the Alpenglow migration.

If you want to run Agave, the hardware requirements are heavy. Anza's docs ask for a CPU with a 2.8GHz base clock and SHA extensions, separate NVMe drives of 1TB or more for accounts and for the ledger, and a 10 Gbps connection for staked nodes (2 Gbps is the minimum). Ubuntu 24.04 is the main supported system. Install and upgrade guides live at docs.anza.xyz.

Alpenglow consensus upgrade and 150ms finality

Alpenglow is the new set of rules Anza designed for how Solana agrees on blocks. It replaces TowerBFT, the older system it takes over from. The first part, called Votor, aims to make a block final in about 150ms. That is the point after which a payment cannot be undone. Under TowerBFT the same step takes about 12.8 seconds, according to the Solana Foundation's release notes.

Anza's Alpenglow page describes three main changes:

• Votor finalises a block in one round of voting if validators holding 80% of stake respond, or in two rounds at 60%. Whichever path finishes first wins.
• Votes move off-chain. Validators stop sending a vote transaction for every block and instead exchange signed messages that combine into one compact certificate. That frees block space for users and removes the vote fees operators pay.
• The network is designed to keep running with 20% of stake acting maliciously and a further 20% offline at the same moment.

The migration has already run on Solana's public test networks. Alpenglow went live on testnet on 24 September 2026 and on devnet a day later. Mainnet has no announced date as of 10 October 2026. Anza's page says the migration "will be announced" after an observation period, and the company said on 5 October that Alpenglow is "headed to mainnet-beta soon". Anza's January roadmap had targeted the third quarter of 2026, so the mainnet step is running later than first planned.

A second part of the design, Rotor, is planned to replace Turbine, the system that spreads block data across the network. It has not shipped.

Rent reduction, larger transactions and the Anza26 roadmap

Anza sets out its plans for the year in a roadmap called Anza26. The goals are a faster network, more room in each block, and less work for the people who run nodes and build apps. Three items reached mainnet with Agave 4.2:

• Rent, the SOL deposit every account must hold to stay on-chain, is being cut by 90% under SIMD-0437. The cut is split across five feature gates, and the first step went live in early September 2026.
• A new transaction format (SIMD-0296) raises the maximum transaction size from 1,232 bytes to 4,096 bytes, which lets apps fit more instructions and larger proofs into one atomic transaction.
• Slot times fell from 400ms to 200ms under SIMD-0525.

Other items on the roadmap have not shipped yet. The biggest is Multiple Concurrent Proposers, or MCP. On Solana, one validator at a time picks the order of transactions in a block. MCP would let several validators add transactions to the same slot, which Anza says would break that "single leader monopoly". The roadmap also lists bigger blocks, with a limit of 100 million compute units. A third item, Block Revenue Distribution (SIMD-0123), changes how validators track and share the fees they earn.

Anza developer tools: Pinocchio, Solana Kit, Codama and P-Token

Anza maintains open-source libraries that Solana app developers use every day. They are free, and most of them aim to make programs cheaper to run or easier to call from an app.

• Pinocchio is a minimal Rust library for writing on-chain programs that use as little compute as possible.
• P-Token is a rewrite of the SPL Token program built with Pinocchio. Anza's Agave 4.0 notes estimate it frees roughly 12% of block capacity network-wide.
• Solana Kit is the JavaScript and TypeScript SDK for building apps. Version 7, released in July 2026, added React hooks and transaction introspection.
• Codama generates client code and standard interface descriptions from a program.
• Wincode is a fast serializer for Rust that is compatible with bincode. Agave uses it in performance-critical paths.
• SBPF is the virtual machine that runs Solana programs. Anza published a migration guide to the SBPFv3 bytecode format in September 2026.

Anza's GitHub organisation also holds a Mollusk test harness for programs and the compiler toolchain used to build them.

Anza Research, Quantumglow and post-quantum work

Anza has a research group that works next to its engineers. Its recent papers ask what a powerful quantum computer would mean for Solana, and how the network could stay safe from one.

In April 2026 Anza published "Securing Solana Against a Powerful Quantum Adversary". In July 2026 it followed with Quantumglow, which Anza calls "a post-quantum adaptation of Alpenglow". We explain the design in our report on the Quantumglow proposal. Both are research papers. Neither has a date to ship.

For Anza's own summary of its priorities, see our write-up of Anza's State of the Network talk from Breakpoint in December 2025.

Who Anza and Agave are for

Anza's work matters most to three groups, and most people who use Solana never deal with Anza directly.

People who run nodes are the direct users. If you run a validator or an RPC node, you most likely run Agave or a client built on it, and Anza's release dates set your upgrade plans. The limits are cost and time. The hardware is costly, new releases come often, and a node left on an old version can fall off the network.

Developers use Anza's libraries whether or not they know the name. If you are writing a program where compute cost matters, Pinocchio is aimed at you. If you are building a web app, Solana Kit is the SDK to start from.

Stakers and token holders are affected indirectly. You cannot stake with Anza or buy into it. What you can do is check which client and version your validator runs, since a validator that upgrades late may miss rewards. You can compare validators by commission, uptime and software version on Solana Compass.

Is Agave safe? Bug bounty, security patches and client concentration risk

The main risk with Anza is that so much depends on one team's code. Most of Solana's stake runs Agave or software built from it. A bad bug in Agave could stall the network or split it in two. Careful work lowers that risk, but it cannot remove it.

Three facts help you weigh it.

First, the clients are less independent than the names suggest. Jito-Solana, the client maintained by Jito JTO$0.470-1.2%, is a fork of Agave. Frankendancer, the hybrid client from Jump Crypto, pairs its own networking with Agave's execution and consensus code. A flaw in that shared code affects all three.

Second, Alpenglow has narrowed client choice for now. Before the testnet migration in September 2026, Anza told operators that "Firedancer and Frankendancer do not support the Alpenglow migration" and that testnet nodes on either client had to switch to Agave. Whether Firedancer will support Alpenglow in time for the mainnet migration had not been announced as of 10 October 2026.

Third, security problems do occur and have so far been fixed before anyone used them. Two flaws were reported privately to Anza in December 2025: one could crash a validator through the gossip network, and the other let an attacker block a validator's votes. Anza's patch summary says they were fixed in v3.0.14 together with the Firedancer and Jito teams and the Solana Foundation, with "no known attack on the cluster".

Agave has a standing bug bounty. Its security policy offers up to 25,000 SOL for a loss-of-funds bug and up to 12,500 SOL for a consensus safety violation, paid by the Solana Foundation in SOL locked for 12 months. A separate Alpenglow competition in August 2026 offered a pool of up to 50,000 SOL, according to Helius's Agave 4.2 review.

There is no custody risk in the usual sense. Anza does not hold user funds, and it has no on-chain program that it alone can upgrade. Protocol changes take effect only when validators adopt a release and a feature gate activates.

Agave vs Firedancer, Jito-Solana and Frankendancer

Agave is the main Solana client, and two of the other three are built from its code. Firedancer is the only one that stands fully apart. Jump Crypto wrote it from scratch in C.

Here is how the four differ:

• Agave is Anza's Rust client, descended from the original Solana Labs code. New protocol features, including Alpenglow, usually arrive here first.
• Jito-Solana is Agave with extra code for MEV, the additional income validators earn from how transactions are ordered. It follows Agave's version numbers closely.
• Frankendancer combines Firedancer's networking and block production with Agave's execution and consensus.
• Firedancer shares no code with Agave. That independence is the point: a bug in one client is unlikely to exist in the other.

If you run a node, the choice comes down to a trade-off. Agave gets each new feature first. A second codebase makes the whole network safer, because one bug cannot take down every node. Alpenglow shows the tension: the test networks moved to the new consensus on Agave alone.

Does Anza have a token? ANZA price searches explained

Anza has no token. Its website and docs list no token, no airdrop and no points scheme. Anza is a private company, and Fortune reported that a Solana Foundation grant paid for its launch.

A search for an "Anza price" leads to tokens that borrow the name. One "ANZA" token shown in the Phantom wallet copies the text Anza uses to describe itself, but Phantom flags that token as unverified. No token with the Anza name has been announced by Anza.

Anza founders, funding and history

Anza was founded by a group that left Solana Labs together. Its launch announcement of 30 January 2024 names Jeff Washington, Stephen Akridge, Jed Halfon, Amber Christiansen, Pankaj Garg and Jon Cinque among the founding team. Jeff Washington is chief executive, and Stephen Akridge was a co-founder of Solana Labs.

Fortune reported at launch that about half of Solana Labs' roughly 100 staff moved to Anza. It described Anza as an "employee-owned, for-profit" business funded by a grant from the Solana Foundation, with Solana Labs keeping a 13% stake. The same article quoted critics who called the split "decentralization theater", since the same engineers kept working on the same code under a new name.

Key dates since then:

• 30 January 2024: Anza is announced.
• 2 March 2024: Anza forks the Solana Labs validator into the Agave repository.
• May 2025: Anza researchers present Alpenglow.
• January 2026: Anza publishes the Anza26 roadmap and says the network had "zero downtime" in the previous year.
• 24 and 25 September 2026: Alpenglow goes live on testnet and devnet.
• 9 October 2026: 200ms slots go live on mainnet.