The Nexus Network is a distributed proving infrastructure that makes zero-knowledge proofs practical at scale. It operates as a verifiable supercomputer.

​
Network Architecture

The Nexus Network operates through two main components:

Nexus Orchestrator

A service that:

• Coordinates the network

• Distributes proving tasks

• Verifies completed work

• Manages reward points

Network Nodes

A global network of computers that:

• Run the Nexus zkVM

• Supply compute to the network

• Submit completed work

• Earn rewards for contributions

The Nexus Orchestrator is currently a centralized service managed by Nexus during testnet phases, Anyone can become a node by running either the web interface or CLI tool.

​
How Nodes Participate

To help understand how the pieces fit together, let’s look at the flow of a node connecting to the system and getting rewarded.

1

Node Setup

A user installs the CLI tool or joins via the web interface to become a network node

2

Network Connection

Node connects to the Nexus Orchestrator and requests work to do

3

Proof Creation

Node receives a proving task and performs the required computations

4

Work Submission

Node submits the completed proof back to the Orchestrator

5

Verification & Points

Orchestrator verifies the work and allocates points in real-time

6

Token Distribution

Every hour, the Orchestrator converts accumulated points into Nexus Chain tokens

​
Current Implementation

This is the current testnet implementation which is based on learnings from previous testnets, which saw over 1.5 million nodes and 100,000 concurrent contributors.

Future versions will continue to focus on:

  • Enhanced scalability

  • Increased security

  • Greater decentralization

Was this page helpful?

OverviewArchitecture