SOLANA·HUB
DE
Infrastructure

Agave v4.1 Recommended for Mainnet Validators — Setting the Stage for Alpenglow

Anza recommends Agave v4.1 for mainnet validators: lower RAM, XDP out of experimental, Pinocchio rewrites and several SIMD activations. The release prepares for Alpenglow; 200ms slots and larger blocks only arrive with v4.2.

SOLANA·HUB Editorial ·
Source: Helius

What happened

Agave v4.1 (specifically v4.1.0-rc.1) is now recommended for general use on mainnet, according to Anza. The release brings performance and efficiency gains and lays the groundwork for Solana’s next scaling step around the new Alpenglow consensus. It follows Agave 4.0.

What v4.1 brings now

  • Lower RAM: validators on v4.1 use less memory than on v4.0 and v3.1.
  • XDP goes standard: the “experimental” label for XDP is gone, with standardized flags (--xdp-interface, --xdp-cpu-cores, --xdp-zero-copy). More than two-thirds of the network has already activated XDP.
  • Pinocchio rewrites: the rewritten p-memo program is live and now needs only 287 instead of 2,022 compute units (about 14% of the previous cost). The p-ATA program is in development and is expected to cut weighted CU usage by roughly 80.9% — freeing more than 2.78 million CUs per block.
  • Several SIMD activations: including BLS pubkey management (SIMD-0387), Validator Admission Tickets (SIMD-0357, 1.6 SOL per epoch), Fast Leader Handover (SIMD-0337), commission in basis points (SIMD-0291), and a SHA-512 syscall (SIMD-0512).

What is not in it yet (v4.2 and beyond)

Important context — these widely cited features are not in v4.1:

  • 200ms slot times are expected to arrive only with Agave v4.2.
  • Larger blocks (4096-byte transactions) are likewise planned for v4.2.
  • Alpenglow activation on mainnet has no fixed date yet; community testing is ongoing, and the preparation work sits in v4.1.

What validators should do

  • XDP migration: operators not yet on XDP should prepare the switch (Anza/Solana Foundation provide checklists).
  • BLS key registration: vote accounts without a registered BLS public key cannot participate in the new Alpenglow voting — registration must happen before activation.
  • Vote account funding: with Validator Admission Tickets, the fee is deducted from the vote account rather than the identity account, so funds must be placed accordingly.

How the consensus change works: Alpenglow explained. What matters when choosing a validator: Solana validator selection.

Note: This is reporting, not investment advice.

What to watch

  • When Alpenglow is activated on mainnet
  • When v4.2 ships with 200ms slots and larger blocks
  • How quickly validators move to v4.1

Sources

#agave #anza #alpenglow #validator #infrastructure

Related Articles