Infrastructure

Agave v4.5: tentative schedule, pause through 18 November

On 10 November 2026 Anza posted the Agave v4.5 schedule. Feature activations are paused until after Breakpoint, Anza writes. The dates are tentative and the gates are planned.

On 10 November 2026 Anza published the schedule for Agave v4.5 on X and in the wiki. Feature activations are paused until after Breakpoint, Anza writes. In the wiki, the pause in release work runs through 18 November.

Activations on testnet, devnet, and mainnet are set to resume on 19 November. Every date in the wiki can change. Operators should wait for announcements on Discord before an upgrade or a downgrade.

Two stages on mainnet

Anza plans two stages for the mainnet-beta version. Volunteers are to take 20 percent of stake to v4.5, and the general recommendation follows. Anza writes that this cuts a week from the release cycle.

The v4.4 schedule had three stages: 10 percent of stake, then 20 percent, then the general recommendation. That rollout is in the v4.4 report.

The wiki sets the mainnet-beta upgrade candidate at 27 November. The call for 20 percent of stake is dated 30 November. The general recommendation is 7 December.

Feature activation for v4.5 on mainnet is planned to begin on 14 December. The wiki marks the devnet upgrade as delivered on 10 November and the testnet recommendation on 6 November. The testnet target had been 9 November.

Planned gates

Anza names three gates for this cycle and lists them as planned.

Rent reduction under SIMD-0437 is set to continue in steps 3 through 5. Anza takes the rate from 5,080 lamports per byte to 2,575, then to 1,322. Step 5 ends at 696 lamports per byte.

Existing accounts keep working. The excess can be claimed after each step. Claiming inside Solflare is covered in the Solflare report.

On 11 November 2026 the mainnet rate was 5,080 lamports per byte. Steps 3 through 5 are not active. The measurement is at the end of this report.

The Solana Foundation page Reduced Rent, updated September 2026, still lists step 2 as testnet in its table. The query shows 5,080 lamports per byte on mainnet.

That page still expects steps 3 through 5 with Agave 4.4. Anza’s schedule of 10 November places those steps in the v4.5 cycle. Earlier steps are in the Agave 4.2 report.

Under direct mapping, SIMD-0460, the runtime is supposed to stop copying account data into the virtual machine and back. The same applies to a call into another program. Programs would read and write the data in place.

On the page Account Data Direct Mapping, the change has been active on devnet and testnet since May 2026. The page lists both gates as pending and gives no mainnet date.

Programs that break the new memory rules can fail, the page says. On 10 November Jonas Hahn wrote on X that programs should be tested locally or against devnet.

His profile lists him as DevRel at the Solana Foundation. He names the feature virtual_address_space_adjustments.

Automatic resizing under SIMD-0433 covers loader-v3 upgrades. The ProgramData account is supposed to resize to the new binary.

A smaller file returns surplus rent to the spill account. A larger file needs no separate ExtendProgram call. That change is planned as well.

What to watch

  • Whether the wiki target dates hold
  • Whether rent steps 3 through 5 activate in this cycle
  • Which mainnet date direct mapping gets

How we measured. On 11 November 2026 the public mainnet API returned a minimum balance of 650,240 lamports for an account with no data.

The minimum is 128 bytes of overhead plus the data bytes, times lamports per byte. 650,240 divided by 128 is 5,080.

Sources

Background and guides

#agave #anza #rent #validator #simd