Starting today, a new progress bar in the Nexus web app shows each step your device takes as it contributes compute power to the network. It’s a small update powered by a much bigger set of behind-the-scenes upgrades that improve access, rewards, and how proving works on Nexus.
This post breaks down what the new progress bar shows, what’s changing under the hood, and what it all means for contributors across the network.
Introducing the Progress Bar
Until now, proving mostly happened behind the scenes. After connecting your device, you would wait and see your NEX Testnet Points tick upward without really knowing what was happening.
The new progress bar changes that. It gives a real-time view into each step of the proving process. Whether you’re a first-time contributor or a power user running multiple devices, the progress bar helps you follow the work from start to finish.
The progress bar:
Shows what’s happening behind the scenes with the compute power you’re contributing
Makes pauses or wait times easier to understand
Helps anyone follow the proving process, regardless of technical background
The Proving Process, Visualized
Each time your device runs a proving task, it moves through five stages:
Stage
What it means
Waiting
Your device is ready and waiting to request its next task. (This happens about every 2 minutes.)
Loading
The network is assigning and preparing the proving task.
Computing
Your device is actively generating a zero-knowledge proof.
Submitting
The completed proof is being sent to the network.
Submitted
The network has received and verified your proof. Points will be awarded soon.
This flow repeats automatically as long as your device is connected. And now, you can follow each step live.
0:00
/0:16
What’s New Under the Hood
The new progress bar is powered by a deeper set of infrastructure upgrades to the proving system itself.
Here’s what has changed behind the scenes:
Improving Access Across the Network: There are improvements to how proving tasks are assigned. The system now focuses on reaching more contributors across the network to help more people participate and earn rewards, regardless of how many devices they run.
Higher rewards per task for CLI Users: Each proving task in the CLI now earns significantly more NEX Testnet Points — up to 10x more than before in many cases.
Weekly reward limits: There will be a limit to the amount of times you can claim NEX Testnet Points per week to promote a more balanced distribution of rewards. This may cause a small delay between proof submission and point claims.
These changes are designed to make Nexus more sustainable and scalable, while improving the experience for all contributors.
What This Means for You
If you’re using the web app: You now get real-time feedback on what your device is doing, and a clearer picture of how the network works.
If you’re proving via CLI: You may see fewer tasks overall, but your rewards per task will be much higher.
If your points seem delayed: That's expected. Don't worry, you're still earning rewards. Some NEX Testnet Points may appear after a short wait due to batching and weekly rate limits.
What Does It Mean To “Prove”?
When you click the button to connect to the Nexus web app, you’re not just toggling a switch. You’re contributing compute power to the network by generating a zero-knowledge proof. This type of proof is a cryptographic statement that confirms a computation was done correctly, without exposing any private data.
Here’s what happens step by step:
Your device connects to the Nexus network, and runs its own instance of the zkVM.
The Nexus network sends a program and its input data to your device.
The Nexus zkVM, which is running on your device, executes the program, generating a proof.
Your proof is submitted to the network, along with performance metrics.
Your account will earn rewards such as points and tokens for your contributions.
The process repeats as long as your device remains connected.
Try It Out
The new progress bar is now live atapp.nexus.xyz. It appears automatically whenever your device is running a task.
Stay Involved
We’re always working to make proving more transparent and rewarding. If you have feedback, questions, or ideas:
