Skip to content

SKaaalper/Nexus-Testnet-III

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 

Repository files navigation

Nexus Incentivized Testnet III — Prover-Node Setup

image

Testnet III will be live until the Nexus Mainnet launch later in Q3 2025. This means that, unlike past Nexus testnets, participants in every country will have weeks, not days, to contribute to the Nexus supercomputer and earn rewards.

Table Of Contents:

Features:

  • Installs all required dependencies
  • Supports 1 to 10 simultaneous nodes (recommended 1 Node ID : 1 VPS Server, if your server is low RAM)
  • Automatically installs Rust, Nexus CLI, and nexus-network
  • Launches multiple nodes in screen sessions

💻 Nexus Prover Node — Recommended Hardware Requirements

Component Minimum Recommended
CPU 6 cores (x86_64) 8 cores or higher
RAM 12 GB 12 GB or more
Disk Space 10 GB SSD 20 GB SSD (NVMe if possible)
Bandwidth 5 Mbps (up/down) 10+ Mbps stable
OS Ubuntu 22.04 Ubuntu 24.04 LTS
Architecture x86_64 x86_64
Other Root access + open ports VPS or Dedicated Server

⚠️ Memory Notice

12 GB of RAM is now the safe minimum for running a Nexus Prover node without crashes.

You can run multiple nodes on one VPS/device, but not recommended unless you have enough RAM.
If memory is too low, it may cause system crashes ❗❗

💡 More RAM = Higher Cycles/sec

💡 VPS Suggestions:

Provider Plan Example Meets 12GB RAM? Notes
Contabo VPS 30 6 vCPU / 12 GB RAM / 300 GB SSD for ~$12/mo ✅ Yes 💯 Recommended
Hetzner CPX41 8 vCPU / 16 GB RAM / 160 GB SSD ✅ Yes Excellent performance
DigitalOcean 2 vCPU / 2–8 GB RAM ❌ No Needs upgrade
Localhost (VM) Ubuntu VM on Home PC ⚠️ Maybe Not reliable if uptime is unstable

Guide on How to buy VPS: Contabo

Run the Auto-Installer

Copy and paste the following one-liner to begin setup:

wget -q https://raw.githubusercontent.com/SKaaalper/Nexus-Testnet-III/main/nexus-prover-setup.sh && chmod +x nexus-prover-setup.sh && sudo ./nexus-prover-setup.sh

image

If you want to add more nodes

cd /root/nexus-prover
  • Create screen:
screen -S nexus2
  • Run Node:
nexus-network start --node-id <your-node-id>
  • Change nexus2, nexus3, nexus4, etc., depending on the next available screen session number.
  • Replace YOUR_NEW_NODE_ID with your actual Node ID from the Nexus dashboard.

🔔 Note: Avoid using duplicate screen session names to prevent conflicts that could stop or disable other running nodes.

Monitor or Manage Nodes:

Action Command
Detach session CTRL+A then D
Reattach session screen -r nexus1
Stop a node screen -XS nexus1 quit
Remove setup files rm -rf /root/nexus-prover

image

Update your node to stay in sync and continue participating.

How to Update:

  1. Delete old screen:
screen -XS nexus1 quit
  1. Download and install the latest CLI:
curl https://cli.nexus.xyz/ | sh
source ~/.bashrc
  1. Create new screen:
screen -S nexus1
  1. Start your node again:
nexus-network start --node-id <your-node-id>

→ Get your Node id HERE: https://app.nexus.xyz/nodes

→ Make sure you replace <your-node-id> with your actual Node ID.

→ Monitor and Manage your node: GO HERE

image

FULL COMMANDS TO FIX GLIBC 2.39 ISSUE.

  1. Install required packages:
sudo apt update
sudo apt install -y gawk bison gcc make wget tar
  1. Download GLIBC 2.39:
cd ~
wget -c https://ftp.gnu.org/gnu/glibc/glibc-2.39.tar.gz
tar -zxvf glibc-2.39.tar.gz
cd glibc-2.39
  1. Create a build directory:
mkdir glibc-build
cd glibc-build
../configure --prefix=/opt/glibc-2.39
  1. Compile and install (this will take time depending on CPU):
make -j$(nproc)
sudo make install
cd ~
  1. Create screen session:
screen -S nexus1
  1. Run the Nexus Node: → Replace <your-node-id> with your actual node ID:
/opt/glibc-2.39/lib/ld-linux-x86-64.so.2 \
--library-path /opt/glibc-2.39/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu \
/root/.nexus/bin/nexus-network start --node-id <your-node-id>

→ Get your Node id HERE: https://app.nexus.xyz/nodes

→ Monitor and Manage your node: GO HERE

Join the Telegram for updates and help:

👉 @KatayanAirdropGnC

Releases

No releases published

Packages

No packages published

Languages