5f5a87d8-c

ConfirmedInfrastructure525 words3 min decode

Solana Restarts Mainnet Upgrades With Direct-Mapping Break Warning

Solana resumed mainnet upgrades on Nov. 19, with epoch 1092 activating stricter memory-access checks. Anchor programs below v1.2.2 risk ownership errors under the new rules.

Solana Resumes Upgrades With Direct-Mapping Warning
WitnessSolana Resumes Upgrades With Direct-Mapping Warningblickpixel / pixabay

Outputs

  1. Solana resumed mainnet upgrades on Nov. 19 after a pause through Nov. 18, per Anza's v4.5 schedule

  2. The access-check gate virtual_address_space_adjustments went live in epoch 1092, though Anza's tracker still lists it as pending

  3. Anchor programs should upgrade to v1.2.2 and rebuild to avoid ownership errors on cross-program invocations

  4. Both gates are active on devnet and testnet; Dec. 14 is the tentative start of v4.5 feature activations, not a confirmed direct-mapping deadline

Solana resumed mainnet upgrades on Nov. 19 following a pause through Nov. 18, with Anza's v4.5 release schedule targeting Dec. 14 as the start of v4.5 feature activations, according to the release calendar. The immediate operational story for program developers is not the resumption itself but the stricter memory-access rules that arrived with it.

The Solana Foundation confirms that epoch 1092 marks the activation of the first of two feature gates: virtual_address_space_adjustments, which enforces the new access checks and changes the stack layout. The second gate, account_data_direct_mapping, which removes the account-data copying that validators currently perform, remains inactive on mainnet. Anza's tracker, notably, still lists the access-check gate as pending — a discrepancy developers should treat with caution when planning deployment timelines.

What does direct mapping change for programs?

Today, validators copy account data into a program's virtual machine and copy it back out; cross-program calls repeat the process. Direct mapping lets programs read and write account data where it already lives, eliminating those copies and their associated comparisons. The performance logic is straightforward: fewer copies means less work per instruction.

The cost is stricter enforcement. The Foundation states most programs are unaffected, but code that relied on previously tolerated shortcuts can now fail. Some stack-memory changes — the working space used during function calls — can alter behavior without raising an error, which is the harder failure mode to detect in production.

Four risk areas the Foundation identifies

  • Account-memory shortcuts. Reading beyond account data, or writing to read-only or foreign-owned accounts, fails even if the original bytes are restored afterward.
  • Cross-region accesses. A single memory operation spanning separate regions must be split into separate accesses.
  • Account resizing. Deprecated resizing code that leaves new bytes uninitialized needs replacing. The Foundation recommends substituting realloc with resize, which zero-fills added space.
  • Stack assumptions. Hard-coded stack addresses, address calculations across function frames and out-of-bounds stack accesses can break or silently change behavior.

The Anchor-specific exposure

Anchor programs carry a specific risk when they reassign a typed account to another program through a cross-program invocation. Older account-exit code can still attempt to write the account afterward, triggering an ownership error under the stricter rules. A merged Anchor fix addresses the pattern; the Foundation advises upgrading to Anchor v1.2.2 and rebuilding affected programs.

Both gates are already active on devnet and testnet. The Foundation recommends testing every instruction path — including close, resize and CPI paths — rather than validating a single successful workflow and assuming the rest holds. Wallets, frontends and indexers require no format or RPC changes, but transactions can still fail if a program they call is incompatible.

One caveat on timing: Anza's tracker records direct mapping as having shipped in v4.0.0-beta.0 and supplies no mainnet activation epoch, so the Dec. 14 activation window should not be read as a confirmed direct-mapping deadline. All dates remain tentative, and the gap between the Foundation's epoch-1092 status and Anza's pending listing suggests developers should verify gate status on-chain before each deployment.

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