c5f83b52-1

ConfirmedInfrastructure592 words3 min decode

Anza Slates Solana Direct Mapping for Mainnet, With No Activation Date

Anza says Solana's direct mapping memory change reaches mainnet this cycle with no date set. The virtual_address_space_adjustments gate is queued for November 19, epoch 1092.

Anza readies Solana direct mapping for mainnet but sets no activation date
WitnessAnza readies Solana direct mapping for mainnet but sets no activation dateAkela999 / pixabay

Outputs

  1. The virtual_address_space_adjustments memory-checks gate is queued for mainnet activation on November 19, in epoch 1092.

  2. Both direct-mapping gates have been live on devnet and testnet since May 2026.

  3. Anchor programs older than 1.2.2 are exposed to instruction errors when reassigning typed accounts across program calls.

  4. Direct mapping cuts up to four account-data copies per instruction to zero, per the Solana Foundation.

  5. SIMD-0268 would raise cross-program call nesting depth from four to eight after activation.

Anza, the firm behind Solana's primary validator client, confirmed Thursday that direct mapping — a memory-model change that eliminates account-data copying — is queued for mainnet activation this cycle, without setting a calendar date. The Solana Foundation's upgrade page still lists the expected mainnet date as unset.

"Solana devs, direct mapping is a breaking change heading for mainnet activation this cycle," Anza wrote on X, adding that feature gate activations had resumed following the Breakpoint conference. A feature gate is the switch that rolls a protocol change out network-wide at the start of a new epoch.

What is actually being activated?

On-chain data shows the first gate, virtual_address_space_adjustments, which enforces new memory checks, is queued for mainnet activation on November 19. The Foundation's status table places it in epoch 1092, the next epoch.

The second gate, account_data_direct_mapping, removes the need to duplicate account data. It has not been switched on for mainnet yet. Both gates have run on devnet and testnet since May 2026, where the new rules already apply to developer-deployed programs.

The operational consequence is significant. Today, a validator copies each account's data into a program's virtual machine before execution and copies it back afterward. Cross-program invocations repeat that round trip. Direct mapping lets the VM read and write account data where it already sits, cutting up to four copies per instruction to zero, per the Foundation.

What breaks, and for whom?

Under current rules, a program can read past the end of an account, write to a read-only account provided it restores the old value, and span two memory regions in a single access. None of the three triggers an error today. Once the checks gate activates, all three fail with an instruction error.

A quieter hazard sits in the stack layout. The Foundation warns that a program's functionality can change under the new stack layout without producing any error — meaning a successful transaction does not prove that stack-dependent code is safe.

Code is exposed if it:

  • reads raw account bytes instead of the SDK's account types;
  • modifies account sizes;
  • uses unsafe Rust blocks or raw pointers;
  • calls another program and reassigns a typed account — the failure mode for Anchor programs older than version 1.2.2.

What does this change for practitioners?

Anza replayed historical mainnet transactions and contacted teams whose programs would break under the new rules. The replay, however, covered only traffic Anza had already observed, so the Foundation advises developers to test their own code rather than wait for outreach. Most application developers, validator operators and users need take no action — unless a program they depend on violates the new memory rules.

The change sits inside a broader performance agenda. A follow-on proposal, SIMD-0268, would extend the permitted nesting depth of cross-program calls from four to eight once the new rules take effect. A related pointer gate, syscall_parameter_address_restrictions, already went live on mainnet on June 30, 2026, making existing cross-program calls compliant.

Direct mapping also follows the Alpenglow protocol redesign scheduled for October 21, which retires the TowerBFT voting mechanism in use since 2020 and targets sub-150-millisecond finality. Solana processed a record 169.9 million non-vote transactions in a single day on August 4, after the per-block compute limit rose by 66%.

For teams with legacy Anchor deployments, the working deadline is practical rather than announced: the memory checks are queued for November 19 in epoch 1092, and stack-layout breakage will arrive silently.

via cryptonews.net (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,651 articles