Agave 4.2 Ships 90% Rent Reduction, 3.3x Larger Transactions, 200ms Slots, and a 50,000 SOL Bug Bounty

Anza shipped Agave 4.2 on July 31, delivering three independent feature-gated upgrades to Solana mainnet alongside the first public release of the complete Alpenglow consensus codebase. The same day, the team published full rules for an Alpenglow security competition offering up to 50,000 SOL in bounties, with submissions opening August 5.

Feature activation for all three upgrades is scheduled for the week of August 17, 2026. No breaking changes accompany the release.

90% Rent Reduction

SIMD-0437 cuts the lamports_per_byte constant from 6,960 to 696, a tenfold reduction in on-chain storage cost. For a standard SPL token account, that moves the required rent-exempt deposit from roughly $0.16 to approximately $0.016. Anza has phased the cut across five independent feature gates so network participants can monitor state growth at each step before the next decrement activates.

The practical effect extends beyond absolute cost. When per-account rent drops to a fraction of a cent, it becomes feasible for applications to cover deposit costs on behalf of users rather than requiring wallet funding as a prerequisite. Consumer-facing applications built on Solana have historically had to work around rent requirements through token extensions or app-side subsidy programs; the new floor makes blanket coverage economically tractable.

3.3x Larger Transactions via Transaction v1

SIMD-0296 raises the maximum transaction size from 1,232 to 4,096 bytes through a new v1 transaction format. Existing v0 and legacy transactions continue to function without modification.

The extra payload headroom addresses a concrete constraint: ZK proof systems, large multisignature schemes, and BLS signature structures have routinely exceeded the 1,232-byte cap, forcing developers to split atomic operations across multiple transactions or stitch them together using address lookup tables. At 4,096 bytes, ZK proofs can land in a single transaction alongside the instruction they verify. BLS aggregate signatures, relevant to both Alpenglow's own cryptographic architecture and to zero-knowledge identity applications, fit inside a v1 transaction without external coordination. What previously required bundles can now settle as a single atomic unit.

SIMD-0525 Cuts Slot Times to 200ms

SIMD-0525 targets a reduction from 400ms to 200ms per slot, applied in four successive 50ms decrements. The protocol includes a safeguard: if block skip rates rise past a defined threshold at any decrement, the network will not advance to the next step until stability is restored.

The change has direct market-structure implications. At 200ms, confirmation cadence doubles, tightening the window between a trade's submission and its settlement. Market makers operating on Solana can quote narrower spreads at higher confidence when the clearing cycle shortens; the expected improvement in latency also reduces the gap between on-chain and centralized exchange settlement times.

Alpenglow Code Ships in 4.2; Mainnet Targeting 4.3

Agave 4.2 includes the complete Alpenglow codebase, but mainnet activation is withheld pending the Agave 4.3 release, currently targeting October 2026. The version in 4.2 is intended for community test cluster use and security review.

Alpenglow replaces Solana's existing TowerBFT and PBFT-based finality mechanism with Votor, a purpose-built voting protocol designed for real-time block confirmation. Current TowerBFT finality runs at roughly 12.8 seconds; Votor targets approximately 150ms, an improvement of around 85x. The protocol eliminates on-chain vote transactions entirely, removing the current overhead where validators submit vote transactions in every slot, adding latency and compute overhead at scale.

Alpenglow tolerates up to 20% of stake being offline simultaneously plus an additional 20% acting adversarially, thresholds that match or exceed TowerBFT's security guarantees in the common case.

Anza shipped Alpenglow readiness components in Agave 4.1 in June, including BLS public key infrastructure and validator account tables. The 4.2 release completes the codebase integration, setting up 4.3 as the mainnet activation release.

50,000 SOL Bug Bounty: August 5–19

On July 31, Anza published full rules for an Alpenglow security competition with a prize pool of up to 50,000 SOL. Submissions open August 5 at 16:00 UTC and close August 19 at 16:00 UTC. Findings submitted outside that window are handled under Agave's standard standing security policy rather than the competition terms.

Four crates are in primary scope: votor (the voting engine), votor-messages (vote and certificate types), bls-sigverify (BLS signature verification), and bls-cert-verify (certificate verification and stake-threshold checks). The scope extends to the broader Alpenglow integration surface across the validator, with previously documented known issues excluded from eligibility.

Submissions are made through GitHub Security Advisories, one finding per advisory. Public disclosure before Anza has reviewed and remediated a submission disqualifies that finding. A prior announcement in July had signaled the competition; the July 31 publication sets the formal rules and timeline.

The competition runs concurrently with the test cluster availability introduced in Agave 4.2, giving researchers direct access to running Alpenglow code while the bounty window is open.