Solana Changelog: October 16, 2026

Solana Changelog – October 16 2026

Solana’s weekly engineering roundup is packed with new releases, protocol tweaks, and community‑driven tooling updates. This edition spotlights the Web3.js v3.1 launch, several client‑side performance enhancements, and a handful of ecosystem projects that are moving the platform toward higher throughput and richer developer experiences.

---

1. Core Library Updates

• Web3.js v3.1.0 – The flagship JavaScript SDK now ships with tighter integration to Solana Kit, the Wallet Adapter, and the Surfpool testing framework. The update also aligns the SDK with the latest SPL interfaces, making it a drop‑in replacement for projects still on the 2.x line. Developers can upgrade with a single command:

```bash npm install @solana/web3.js@3 ```

• Solana Kit v8.5.0 – Brings a unified connection layer that Web3.js now leverages, simplifying endpoint management across RPC providers.
• Solana Go (FluxRPC) v0.1.11 – Introduces a `getMultipleAccountsImmutable` method that adds a lightweight cache for read‑only account batches, reducing RPC load for high‑frequency queries.

These releases collectively tighten the JavaScript‑to‑Rust bridge, lower latency for wallet interactions, and set the stage for upcoming protocol features.

---

2. Validator Client Enhancements

Agave

• Events System (WTM) – A new, protocol‑agnostic events feed is in development, extending beyond the current Geyser model. This will let validators emit custom metrics and give developers richer insight into on‑chain activity.
• Transaction Execution Time Limit (WTM) – A draft proposal aims to bound transaction runtime, enabling the runtime to abort long‑running transactions early and improve overall block finality. Implementation may rely on SIMD instructions for efficient timing checks.
• Sigverify Batch Reduction (WTM) – Shrinking shred batches from 1,024 to 128 reduces memory pressure and speeds up signature verification, a win for low‑resource validators.

Firedancer

• Votor Memory Optimizations (WTM) – Off‑chain vote messaging now consumes fewer allocations, easing the memory footprint of vote traffic during high‑load periods.

Mithril

• No specific updates this week, but the client continues to align with the broader Agave and Firedancer performance roadmap.

---

3. Protocol‑Level Tweaks

• Compute Unit (CU) Re‑pricing for Secp256r1 – A proposal details CU costs for operations on the Secp256r1 curve, moving the model from arbitrary values toward a more data‑driven approach. This will help validators better account for cryptographic workload.
• CU Limit Restoration – Slot times have settled at 200 ms on Mainnet, prompting a request to raise CU limits back to pre‑reduction levels. The change would restore throughput without altering the overall CU‑per‑second budget.
• Post‑Alpenglow Consensus Improvements – With Alpenglow activation imminent, developers are discussing a minCP multiple‑proposer algorithm and other refinements to the consensus engine.

---

4. Ecosystem Tooling & Frameworks

Anchor

• AVM CLI Update – Anchor now forces the use of the latest `cargo-build-sbf` on the developer’s machine, ensuring all programs compile to sBPFv3. This prevents older binaries from being deployed on Mainnet.
• sbpf‑linker Exploration – Early work on adopting upstream BPF compilers could simplify the toolchain and reduce maintenance overhead.

Testing Suites

• Surfpool – Adding a snapshot capability to its scenarios feature, allowing developers to capture account state at any point in a test run. This aids debugging and scenario planning.
• Mollusk & LiteSVM – Continue to receive incremental updates, keeping them aligned with the latest runtime changes.

Other Highlights

• Superbank v0.8.0, Shipstern v0.12.0, LiteSVM v0.18.0, and Mollusk v0.16.2 were all released, each bringing minor bug fixes and performance tweaks.
• Community contributions include a new primitive for pull‑payments, post‑quantum signing via Falcon‑512, and operational security improvements to the Umbra privacy protocol.
• The Durable Nonce deprecation announcement is now live, signaling a shift toward newer nonce handling patterns.

---

5. Looking Ahead

The roadmap points toward a more modular, observable, and performant Solana stack. With the Web3.js v3 ecosystem now stable, developers can expect smoother onboarding for new projects and tighter integration with wallet and RPC layers. Validator clients are converging on shared performance goals—lower memory footprints, clearer execution limits, and richer event streams—while protocol‑level proposals aim to make compute accounting more transparent.

For teams building on Solana, the immediate action items are:

1. Upgrade to Web3.js v3.1 and align your RPC handling with Solana Kit.
2. Review the upcoming CU re‑pricing and limit restoration proposals to anticipate any changes to transaction costing.
3. Explore the new Surfpool snapshot feature for more deterministic testing.
4. Keep an eye on Anchor’s AVM CLI changes to avoid deployment hiccups.

Staying current with these releases will help you leverage Solana’s evolving performance envelope and maintain compatibility as the network moves toward the Alpenglow consensus upgrade.

---

Stay tuned for next week’s Changelog, where we’ll dive deeper into the minCP proposer algorithm and community validator tooling.