Nexus Changelog 6.06.25

Welcome back to the Nexus Changelog — a recurring update on improvements across the Nexus stack, including Layer 1, Nexus OS, and the zkVM. This edition highlights new interface upgrades focused on transparency and contributor visibility, and reliability improvements to the Nexus zkVM.

Nexus OS and Layer 1: Smarter visibility, streamlined rewards

Partner ecosystem interface

We’ve launched an upgraded interface to better showcase the Nexus partner ecosystem. Popular apps — like those used for node rental and delegation — now appear prominently at the top of the interface. Users can also filter by category, making it easier to explore available tools and services across the network.

Transparent rewards: From points to NEX

Provers can now track earned reward points directly from the Nexus OS homepage. Each 1,000 points is redeemable for 1.0 NEX, with real-time updates available in the dashboard. This creates a clearer, more immediate connection between contribution and reward.

Node telemetry and performance tracking

For the first time, provers can now view telemetry data related to their contributions — including points accumulated since their last withdrawal and average operations per second (ops/sec). These stats offer a tangible view into individual performance and uptime.

New rewards page

The updated rewards page provides a historical and current snapshot of contribution activity. Users can view claimed and unclaimed points, as well as past participation in earlier testnets. It’s a step toward making contribution history and recognition more accessible to the community.

zkVM: Bug fixes, soundness improvements, and better error reporting

We’ve rolled out a set of important updates to the Nexus zkVM aimed at improving reliability and safety during proving.

• Improved guest error reporting: Provers will now see clearer and more informative error messages when their guest programs encounter issues inside the zkVM — a major boost to developer experience.
• Soundness patch: A soundness issue reported by an external fuzzing team has been successfully patched. We’re grateful to the broader community for helping harden the system.
• General fixes: A series of minor optimizations and performance improvements have also been included as part of this maintenance cycle.

Looking ahead

These upgrades continue to pave the way for Testnet III — with deeper transparency, smarter infrastructure, and a more robust verifiable compute stack. As always, you can track progress in the Nexus Docs or follow development on GitHub.