Anza Readies Solana Direct Mapping for Mainnet Activation This Cycle

21 minute ago 2 sources neutral

Key takeaways:

  • Breaking memory checks may cause short-term Solana program failures, so SOL traders should watch migration.
  • Zero-copy account data and deeper calls could structurally boost Solana throughput, aiding SOL valuation.
  • Record non-vote activity plus Alpenglow finality goals suggest SOL's adoption trend is structural, not speculative.

Anza, the team behind Solana’s main validator software, confirmed on Thursday that direct mapping is preparing for mainnet activation this cycle, although no calendar date has been set. The change is described as a breaking modification that could disrupt on-chain programs using unsafe memory shortcuts.

According to Anza’s post on X, feature gate activations resumed after the Breakpoint conference. A feature gate allows the entire network to adopt a protocol change at the start of a new epoch. Anza wrote: ‘Solana devs, direct mapping is a breaking change heading for mainnet activation this cycle.’ On-chain data shows that the virtual_address_space_adjustments gate, which adds new memory checks, was queued for mainnet activation on November 19 and is live in epoch 1092. The second gate, account_data_direct_mapping, removes the need to duplicate account data but has not yet been turned on for mainnet.

Both gates have been live on Solana’s devnet and testnet since May 2026. Under current rules, programs can read past the end of an account, write to a read-only account if the old value is restored, and reach across two memory regions in one access. Once the checks gate activates, all three actions fail with an instruction error. The Solana Foundation also warned that a changed stack layout could alter program functionality without generating an error. Code is considered exposed if it reads raw account bytes rather than SDK account types, modifies account sizes, or uses unsafe Rust blocks or raw pointers. Anchor programs older than 1.2.2 are vulnerable when calling another program and reassigning a typed account.

Anza replayed previous mainnet transactions and contacted teams whose programs would break, but the Foundation advises developers to test their own code rather than wait for a call. Most app developers, validator operators, and users do not need to act. Direct mapping eliminates copying by letting the virtual machine read and write account data where it already exists, reducing up to four copies per instruction to zero. After the new rules are implemented, the SIMD-0268 proposal extends cross-program call nesting depth from four to eight. A related pointer gate, syscall_parameter_address_restrictions, has been active on mainnet since June 30, 2026.

The update follows Alpenglow, a protocol redesign scheduled for October 21 that removes the TowerBFT voting method used since 2020 and aims for transaction finality under 150 milliseconds. 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. At the time of writing, SOL was trading at $72.86, down 1.2% over the past 24 hours.

Previously on the topic:
Nov 17, 2026, 12:50 p.m.
Solmate and Akash Advance AI GPU Services on Solana
Disclaimer

The content on this website is provided for information purposes only and does not constitute investment advice, an offer, or professional consultation. Crypto assets are high-risk and volatile — you may lose all funds. Some materials may include summaries and links to third-party sources; we are not responsible for their content or accuracy. Any decisions you make are at your own risk. Coinalertnews recommends independently verifying information and consulting with a professional before making any financial decisions based on this content.