Welcome to the latest edition of the Nexus Changelog — your biweekly dispatch from across our engineering teams. This update highlights major improvements to the Nexus OS interface, a milestone release of the CLI, backend upgrades to support scale and reliability, and meaningful progress in the ongoing development of the Nexus zkVM.
Nexus OS
This cycle, Nexus OS received a series of updates aimed at improving usability and network visibility for both new users and seasoned contributors.
We introduced a new logged-out landing page to guide first-time visitors and provide clearer entry points into the proving experience. Once connected, users will find a redesigned Wallet page where they can monitor their address, linked social accounts, asset balances, and on-chain activity.
To make navigating the app more seamless, a persistent Connect button now lives in the top-right corner of every page — ensuring proving is never more than a click away.
The Nodes dashboard has also been upgraded significantly. Your current in-browser node is now pinned to the top of the list, and you can easily track unclaimed points earned by each of your nodes. More importantly, Nexus OS now supports the creation and monitoring of up to 100 active nodes per user — a key step toward scaling the network’s contributor base.
Nexus CLI
This week marks a major CLI release with the arrival of version 0.9.0. This update includes protocol-level changes that require CLI versions prior to v0.8.12 to upgrade in order to maintain compatibility with the network.
We’ve also simplified how users interact with the CLI. The tool can now be invoked as nexus-cli — a backwards-compatible replacement for the previous nexus-network naming convention.
Beyond nomenclature, this release brings a set of core improvements: task fetching is now more stable and efficient, reducing unnecessary network polling without compromising performance.
Additional updates include a refined text-based interface (TUI), a more robust install script, and improved logging mechanisms — all aimed at making the CLI easier to use, debug, and extend.
Layer 1 and backend
On the backend, the team delivered a wide-ranging set of upgrades focused on performance, reliability, and security. We introduced Redis read replicas and sharded keys to improve data distribution and system throughput.
Task handling and points computation are now more efficient thanks to batched task lookups, improved leaderboard logic, and fine-tuned resource allocation across services like database and orchestrator pods.
Functional enhancements include new support for additional guest programs, real-time and concurrent points processing, and a revamped crash reporting pipeline.
We also rolled out internal utilities such as points distribution, block proof batching, and wallet-native features — all tools that strengthen the proving workflow.
We addressed a number of bugs, including issues in points calculation, transaction handling, and API parameter usage.
These fixes also resolved race conditions and improved graceful shutdown behavior. Lastly, we adjusted rate limits on several endpoints and sanitized background job behavior to protect against system abuse and maintain overall resilience.
Web provers are now submitting 1000% more verified ops per second since the start of the testnet.
zkVM
The zkVM team continues to build toward a faster and more modular proving system. This cycle included a key fix to a completeness bug in the new M extension circuits — an important step in ensuring correctness across expanded instruction sets.
Alongside the bug fix, we made significant strides in redesigning the zkVM’s prover architecture. This ongoing work aims to create a more efficient and composable proving framework, enabling faster runtime performance and improved scalability for the next generation of zero-knowledge workloads.
Looking ahead
Each of these updates reinforces the foundation for a more powerful and globally distributed proving layer.
From improved interfaces and onboarding to deeper backend robustness and a stronger zkVM core, the work this cycle brings us closer to a verifiable, performant, and developer-friendly network.We are currently in Testnet III, connect today.
