Alpenglow Heads to Solana Testnet as Frankendancer Era Ends; Anza Publishes Agave v4.4 Schedule

Anza said Monday that Alpenglow is coming to Solana testnet this week, triggering an immediate action requirement for any operator still running Firedancer or Frankendancer on the test network, and closing the testnet chapter of Frankendancer's history for good.

Testnet activation will also be the first time validators and developers can observe the new commitment behavior on a formal Solana cluster, after more than four months on the Alpenglow community cluster: under Alpenglow's Votor consensus, the "confirmed" and "finalized" designations collapse into one. A block that reaches the confirmed threshold is immediately finalized, with no separate second round. Agave v4.3, the release carrying Alpenglow, reached general adoption on September 21, and Anza issued the v4.3 upgrade call the same day. Anza says testnet comes first, devnet follows, and mainnet-beta comes after an observation period.

Firedancer and Frankendancer Cannot Cross the Migration Gate

The constraint is architectural. Alpenglow replaces Tower BFT's voting and finality logic with Votor, a protocol whose architecture differs fundamentally from Tower BFT. Validator clients that have not implemented Votor cannot participate in the new consensus rounds. Neither Firedancer nor Frankendancer has that implementation.

Anza issued the warning in plain terms: "Firedancer and Frankendancer do not support the Alpenglow migration. Testnet nodes running either need to switch to Agave v4.3.0 before the gate activates."

The urgency is about stake weight. Alpenglow's feature gate requires sufficient stake to vote for activation before it opens. Validators that have not migrated off incompatible clients before the gate window will have their stake excluded from that count.

The Alpenglow operator documentation covers what the migration entails: vote account BLS key registration, validator admission ticket funding, and vote history file handling. Admitted validators (those in the top 2,000 by stake weight per epoch) are charged a validator admission ticket each epoch; the documentation recommends confirming that funding before the gate opens.

Jump Crypto's hybrid client ran on Solana testnet through the full Alpenglow development period, contributing to network operations while Firedancer's complete implementation matured. Once testnet activation completes, that run is over on the test network. Alessandro Decina, an engineer at Anza, added his own note alongside Tim Garcia's post: "kudos to anza for the milestone too."

Whether a Votor-capable Firedancer build is in development for mainnet has not been announced.

Agave v4.4 Schedule: Mainnet Feature Activation Resumes November 9

Anza published the Agave v4.4 release schedule on September 22, the same day the v4.4 branch was created. All dates are described as tentative, and Anza asks operators to wait for Discord announcements before acting.

The v4.4 schedule runs on a separate track from Alpenglow's activation. Testnet operators are asked to adopt v4.4 on September 28, and testnet feature activation resumes October 5. The mainnet-beta volunteer rollout begins October 19, general adoption is recommended November 2, and mainnet-beta feature activation resumes November 9.

Anza's announcement carried a single line: "The Agave v4.4 release schedule is published."

The specific features subject to the November 9 gate have not been detailed; that list will become clear as the v4.4 branch stabilizes.

What Comes After Testnet

Anza has not announced a mainnet-beta date for Alpenglow. Testnet exercises the exact migration devnet and mainnet-beta will run, and mainnet follows an observation period after devnet. For mainnet operators, the Alpenglow operator guide covers the specific pre-activation configuration steps. For testnet operators still on Firedancer or Frankendancer, the migration to Agave v4.3.0 is immediate.