DevelopersJuly 9, 2026bySolana FoundationSolana Foundation

Solana Changelog: July 9, 2026

Solana Changelog: July 9, 2026

Agave, Firedancer, Superbank, Solana Go, and LiteSVM all published new versions this week. Engineering work also continued across validator clients, RPC 2.0 coverage, language clients, and testing frameworks.

Releases

Several Solana engineering projects shipped new release tags, including beta and release-candidate versions for core infrastructure and developer tooling.

SIMD discussion

A new Solana Improvement Documents (SIMDs) discussion proposes adding optional fees for successful transaction execution. The proposal comes from @cavemanloverboy and focuses on validator incentives.

Validator client work

Validator client work continued across Agave and Firedancer, with changes focused on snapshotting, signature verification, packet handling, and compilation speed.

  • Agave added Wincode serialization for banking stage snapshots. Solana’s current consensus algorithm keeps copies of several chain histories called forks; when one reaches the right height, validators restart with the new root and purge the other histories. Agave snapshots the state of all accounts, called the Banking Stage, when forks reset the root, and this change makes mapping the bank snapshot to system memory more predictable and faster.
  • Agave continued work to optimize SigVerify, the stage that deduplicates transactions and verifies transaction signatures. Performance improvements here can help transactions get into blocks faster.
  • Agave is working to drop packets faster in XDP. Services using XDP will receive packets through QUIC datagrams rather than QUIC streams, which can arrive out of order and require more deduplication; dropping invalid packets from the networking receive queue faster leaves more time for validator logic.
  • Firedancer is working to speed up service compilation. Faster compilation affects developer experience, CI builds and tests, and how quickly a service can be redeployed after a downtime fix.

RPC 2.0 coverage

RPC 2.0 work expanded coverage of the Solana HTTP RPC spec across Superbank and Cloudbreak. These changes target methods RPC providers need to support.

Language clients and testing tools

Developer-facing libraries and test frameworks also saw new work, including React hooks in Kit and program account testing support in LiteSVM.

  • Kit added transaction planning and sending hooks in @solana/react. The hooks let web developers bundle transaction planning and sending into React hooks instead of writing raw Kit functions, enabling more dynamic component behavior based on transaction planning and sending state.
  • LiteSVM is implementing an interface to the getProgramAccounts method. The feature would let programs test whether a program-derived account was successfully created in the test harness, helping developers catch wrong seeds or unexpected addresses.

Community notes

Several builders and community contributors shared new proposals, tools, podcasts, and profiling work.

  • @sns proposed adding .sol as a top-level domain to ICANN in an SNS post on X.
  • @soundsonacid added a new profiling feature for the seashell test harness in a post on X.
  • @catmcgee is hosting a new podcast called The Privacy Show, shared by Solana on X.
  • @ChainflowSol created a tracker for the lowest validator version qualifying for SFDP in a post on X.
  • @jkdotsol created a new disk profiler powered by eBPF in a post on X.
  • @OkohEbina and @a_ix_d posted a new Devs at a Bar podcast with @shek_dev in a post on X.
  • @inspiration_gx created an eBPF program that tracks uprobe events in Solana’s proof-of-history service in a post on X.

Follow Solana developer updates

For weekly Solana engineering updates, follow @solana_devs on X.

Share this article