Solana mainnet feature‑gate activations resumed on Nov 19 after a pause, with developers warned that the upcoming direct‑mapping upgrade will introduce breaking changes.

Solana mainnet feature‑gate activations resumed on Nov 19 after a pause, with developers warned that the upcoming direct‑mapping upgrade will introduce breaking changes.

Solana’s mainnet feature‑gate activations picked up again on Nov. 19 after a pause imposed by the Breakpoint upgrade, and the network’s developers have cautioned that a runtime change called “direct mapping” – which introduces breaking changes – is slated for activation sometime during the current release cycle.

The feature‑gate tracker maintained by Anza still lists Account Data Direct Mapping as awaiting mainnet activation, without a specific epoch or date. The Solana Foundation’s developer guide likewise shows the mapping gate as not yet live.

Direct mapping alters the way programs interact with account data. At present, validators copy account data into a program’s virtual machine and back again; when one program calls another, the data is copied a second time. The upcoming upgrade will allow programs to read and write the data directly in place, eliminating those copies and the associated comparison steps, according to the Foundation.

Because the data will no longer be duplicated, stricter memory‑access rules are required. The Foundation says most programs will be unaffected, but those that have relied on previously tolerated shortcuts may see instructions fail. In addition, changes to stack memory – the temporary workspace used during function calls – can modify program behavior without necessarily triggering an error.

The upgrade is divided into two separate feature gates. The first, called virtual_address_space_adjustments, introduces the tighter checks and modifies the stack layout; the second, account_data_direct_mapping, removes the copying step. It is the virtual‑address‑space adjustment gate that is responsible for the breaking behavior, not the copy‑removal gate itself.

The two sources do not completely agree on the status of these gates. The Foundation’s guide indicates that the access‑check gate went live on mainnet in epoch 1092, while Anza’s tracker still lists it as pending. Both sources agree that the separate mapping gate has not yet been activated.

The Foundation has highlighted specific risk areas for developers. Anchor‑based programs are particularly vulnerable when they reassign a typed account to another program via a cross‑program invocation (CPI). Legacy account‑exit code may still attempt to write to the account afterward, which under the new stricter rules triggers an ownership error. A merged fix in Anchor addresses this pattern; developers are advised to upgrade to Anchor v1.2.2 and rebuild their programs.

Both feature gates are already active on devnet and testnet. The Foundation recommends that developers test every instruction path—including close, resize and CPI calls—rather than relying on a single successful workflow. Wallets, front‑ends and indexers do not need any changes to formats or RPC calls, but transactions could fail if they invoke a program that has not been updated for the new rules.

Anza’s v4.5 release schedule notes that mainnet activations resumed on Nov. 19 after a pause that lasted through Nov. 18. The schedule also earmarks Dec. 14 as the start of v4.5 feature activations, though all dates remain tentative. This is not a confirmed deadline for direct mapping: the tracker records that the feature shipped in v4.0.0‑beta.0 but does not specify a mainnet activation epoch.

Source: CryptoNews.net

Post a Comment

Previous Post Zeniflix Post