The Solana Foundation published its August 6, 2026 engineering changelog. The key item in Releases is a set of feature gates lowering slot time from 400ms to 350ms on Devnet and Testnet. The source describes this as a test-environment rollout; it does not present the change as an already completed mainnet deployment. For developers and operators, the update marks the current validation stage for shorter slots before broader rollout.
The same changelog lists new versions across validator clients and developer tooling. Agave releases include v4.3.0-alpha.3 and v4.2.0-rc.1, Firedancer Mainnet is at v1.1.3, and Frankendancer ships Mainnet v0.1007.40100 plus Testnet v0.1104.40200. Additional releases include solana-signature v3.5.1, Wallet Standard v1.1.6, Stake Program Rust SDK v4.4.0, Token 2022 Program JS SDK v0.14.1, the ZK Elgamal Proof Program WASM JS SDK v0.5.1, Subscriptions Program SDKs, LiteSVM v0.15.2 and Surfpool v1.5.0. These are separate ecosystem releases rather than one new Solana product.
For validator clients, the changelog highlights more Agave conformance work, a rethink of program reloading during transaction processing, and improvements to leader Turbine broadcasting cache and routing-table rebuilds. Firedancer is implementing snapshot creation and QUIC datagram support for Alpenglow messages. Mithril is keeping pace with Agave's conformance suite so different validator implementations can be fuzz-tested against the same behavior.
Developer-facing ecosystem work includes an accepted proposal to set the correct account-data size when modifying an existing Solana program, a discussion about preventing self-withdrawal from Vote accounts, and new React hooks planned for Solana Kit such as useAirdrop, usePayer, useIdentity and transaction-planning and sending hooks. In testing frameworks, Surfpool added a stop command for its daemon service.
Taken together, the changelog is more useful as a snapshot of where Solana engineering work is happening than as a single headline feature. Shorter 350ms slots are being exercised in Devnet and Testnet while Agave, Firedancer, Frankendancer and the surrounding SDK stack continue to move in parallel. The important distinction is that these are test-environment and client-release milestones; they do not by themselves prove a completed mainnet performance change.