Solana’s engineering teams used the week of July 23 to push new builds across both major validator clients and refresh nearly the entire JavaScript SDK surface at once, according to the Solana Foundation’s July 23 changelog. Anza shipped Agave v4.3.0-alpha.2 alongside a v4.2.0-beta.2, Firedancer landed v1.1.2, and fifteen separate program SDKs and tools published new versions in a single week — the kind of coordinated release wave that usually signals housekeeping ahead of bigger protocol changes.
The bigger change is the one that already cleared governance: the Resource and Inclusion Fees SIMD moved to accepted status, restructuring how base fees are split and burned. We covered the fee-burn proposal and the Agave 4.3 alpha in depth when the SIMD landed; this week’s changelog confirms the accepted split — 2,500 lamports of each base fee to the validator, the remainder computed from requested compute units and burned, a protocol-level buy-and-burn tied directly to network usage.
For builders, though, the fee headline overshadows a week with unusually concrete tooling news. Here’s what actually changed under the hood.
Fifteen SDK releases in one sweep
The JS SDK wave touched almost every program a typical Solana app links against: Address Lookup Table v0.13.0, Stake v0.8.0, System v0.13.0, Memo v0.12.0, Compute Budget v0.17.0, Token v0.15.0, Token-2022 v0.13.0, Loader V3 v0.5.0, Record v0.3.0, Program Metadata v0.8.0, ZK ElGamal Proof v0.3.2, Token Wrap v2.6.0, plus Single Pool Program v6.0.1.
When this many SDKs version-bump together, the practical takeaway is dependency alignment: if you upgrade one, plan to upgrade the set, and read the linked release notes before touching a production lockfile. The Foundation’s changelog makes the same point explicitly — review version-specific changes before upgrading.
LiteSVM re-embraces Web3.js
The most interesting single line for app developers: LiteSVM v0.15.0 will support Web3.js once again, alongside Kit. LiteSVM is the lightweight test harness many teams use instead of spinning up a full validator, and its renewed support for the revived @solana/web3.js framework matters because the ecosystem never fully migrated: a large share of legacy projects still sit on Web3.js while newer codebases adopted Kit. A test tool that speaks both means those legacy projects get modern testing without a forced rewrite of their client layer first.
In the same program-tooling bucket, the Subscription Program is adding immediate cancellation support — a user can stop subsequent payments at once, which closes the gap between on-chain subscriptions and how SaaS billing actually behaves — and Caravel is adding associated token account helper CPI invocations, smoothing over one of the most repetitive pieces of Solana program boilerplate.
Validator internals: PoH memory, epoch boundaries, Parquet archives
The client work this week is unglamorous and load-bearing. Agave changed how proof-of-history records are grouped, simplifying the types that store them so memory allocation is more efficient — PoH runs continuously as the chain’s clock, so freed memory there goes straight to higher-priority work like processing user transactions. Agave is also improving its program deployment CLI, which the changelog candidly calls one of the main pain points of Solana development: getting a program onto mainnet.
On the Firedancer side, v1.1.2 shipped while the team works on the epoch boundary procedure — the moment each epoch where validator rewards are prepared and the next leader schedule is set. And Superbank, part of the RPC 2.0 effort, is adding archival via Parquet files, meaning historical chain data lands in the same columnar format the rest of the data-engineering world already queries. Triton One published companion articles on indexing the entire blockchain with Superbank, one of its RPC 2.0 services.
The quiet tell: a bug bounty before Alpenglow
Tucked into the developer-resources section is the item with the largest forward significance: Anza started a bug bounty program ahead of the switch to Alpenglow on mainnet. Alpenglow is the consensus overhaul Solana has been building toward all year, and opening a bounty now is the standard hardening move you make when a mainnet date is close enough to be real. Paired with Firedancer’s epoch-boundary work and Agave’s steady 4.2-beta/4.3-alpha cadence, the release train looks like it’s being cleared for that transition.
Rounding out the week: Helius released an RPC benchmarking tool, OtterSec published guidance on doing Anchor releases safely, and community write-ups covered Groth16 internals and observing proof of history with eBPF — the sort of ecosystem material that tends to cluster when core infrastructure is about to shift.
What to do with this week
If you run a validator, track the Agave 4.2 beta and 4.3 alpha notes now rather than at release, because the fee-split change rides in with that line. If you build apps, the SDK wave plus LiteSVM’s dual-framework support makes this a reasonable week to schedule the dependency-alignment pass you’ve been deferring. And if you’re watching Solana strategically, the Alpenglow bug bounty is the calendar signal: consensus changes of that size don’t open bounties until the endgame.
The weekly engineering updates continue at @solana_devs on X, and the Foundation links every release note in the full changelog.
