Solana Changelog: October 1, 2026

What happened

Devnet lists Alpenglow as a notable feature gate alongside new Agave, Firedancer, Superbank, Web3.js, Kit, and program SDK (the toolkit a developer builds on a platform with) releases. If you want to stay updated on Solana tech every week, follow Solana Changelog at @solana_devs and @readylayerone and turn on notifications.

The change proposed here removes both the unnecessary transformation step and the duplicated memory allowing for runtime and space allocated to run an instruction. The discussion is about using three reserved places in memory (the registers in the proposal) to store crucial data about the size of the instruction accounts and data and where they are located.

Doing this allows for programs to do lookups instead of copying data from memory region to memory region, which is the much slower way the runtime does this today. A proposal was made to make CPIs on the runtime saner and more performant WTM - Calling other programs on Solana requires a syscall (a specified operation on the runtime with a well-defined behavior and cost) that stores redundant account information in memory and transforms that information only to be transformed back again during processing.