NewsCryptoAnza readies Solana direct mapping for mainnet activation, with no date set

Anza readies Solana direct mapping for mainnet activation, with no date set

Author: Cryptopolitan·

Key Takeaways

  • •Anza confirmed that direct mapping is on track for Solana mainnet activation in the current cycle, but no calendar date has been announced.
  • •The virtual_address_space_adjustments gate, which introduces new memory checks, was queued for November 19 and is listed as live in epoch 1092, while the account_data_direct_mapping gate has not yet been switched on for mainnet.
  • •Direct mapping removes the need to copy account data, cutting up to four copies per instruction down to zero, and a separate proposal, SIMD-0268, would extend cross-program nesting depth from four to eight once the new rules take effect.
  • •Code that reads raw account bytes, modifies account sizes, uses unsafe Rust blocks or raw pointers, or runs Anchor versions older than 1.2.2 is exposed to instruction errors, and new stack layouts can change program behavior without triggering an error.
  • •Both gates have been active on Solana's devnet and testnet since May 2026, and most app developers, validator operators, and users need no action unless they depend on a program that fails to follow the new rules.
Anza readies Solana direct mapping for mainnet activation, with no date set

Anza, the team behind Solana's (SOL) main validator software, said Thursday that direct mapping is on track for activation on the Solana mainnet in the current cycle, although no date has been set for the change to go live. The team also cautioned that the change could break on-chain programs that rely on unsafe memory shortcuts.

Memory checks gate queued for epoch 1092

In a post on X, Anza said feature gate activations had started up again after the Breakpoint conference. A feature gate is a switch that requires the entire network to adopt a protocol change once a new epoch begins, making it Solana's mechanism for coordinating protocol upgrades across validators.

“Solana devs, direct mapping is a breaking change heading for mainnet activation this cycle,” Anza wrote. The post carried no calendar date, and the Solana Foundation's upgrade page states that the expected mainnet date has not yet been set.

On-chain data shows that virtual_address_space_adjustments, the gate that adds the new memory checks, was queued for mainnet activation on November 19. The Foundation's status table lists the checks gate as live in epoch 1092, the next epoch.

The second gate, account_data_direct_mapping, removes the need to duplicate account data. Mainnet has not switched it on yet. Both gates have been live on Solana's devnet and testnet since May 2026, meaning the new rules already apply to programs that developers deploy to those networks ahead of mainnet activation. That sequencing gives developers a staged path — memory checks first, copying removal later — with two checkpoints to watch: the epoch 1092 activation and the eventual scheduling of account_data_direct_mapping.

Anchor programs older than 1.2.2 risk instruction errors

Under the current rules, a program can read past the end of an account, write to a read-only account as long as it restores the old value, and reach across two memory regions in a single access. Today, no error stops any of those three actions. Once the checks gate is turned on, all three fail with an instruction error.

A quieter risk emerges when the stack layout is altered. According to the Foundation, the new stack layout can change a program's functionality without generating an error, which means a successful transaction does not demonstrate that stack-dependent code is safe.

Code is considered exposed if it reads raw account bytes rather than using the SDK's account types, modifies account sizes, or uses unsafe Rust blocks or raw pointers. Anchor programs older than version 1.2.2 are also vulnerable when they call another program and reassign a typed account.

Anza replayed previous mainnet transactions and contacted teams whose programs would break. Because the replay covered only traffic Anza had already seen, the Foundation advises developers to test their own code rather than wait for a call. The Foundation's upgrade guidance describes which programming patterns leave code exposed.

Most app developers, validator operators, and users do not need to take any action ahead of the activation. The exception arises when a program they depend on does not follow the new rules.

What direct mapping changes

Today, the validator pulls data from each account into a program's virtual machine before the program begins, then transfers it back. Cross-program invocations repeat that round-trip. Direct mapping eliminates the copying entirely: the virtual machine reads and writes account data where it already exists, with up to four copies per instruction going to zero, according to the Foundation.

Once the new rules are in effect, a separate proposal, SIMD-0268, extends the depth to which programs can nest such calls from four to eight. Cross-program calls on mainnet are already compliant, because a related pointer gate, syscall_parameter_address_restrictions, went active on mainnet on June 30, 2026.

The update follows Alpenglow, a protocol redesign scheduled for October 21 that removes the TowerBFT voting method in use since 2020 and targets transaction finality under 150 milliseconds, according to Cryptopolitan. After the compute limit per block was raised by 66%, Solana registered a record 169.9 million non-vote transactions in a single day on August 4, per Cryptopolitan's earlier coverage.

At the time of writing, SOL was trading at $72.86, down 1.2% over the past 24 hours.