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.
- Hardware requirements
- VPS Suggestion
- Guide on How to Buy a VPS from Contabo
- Run Node
- Add More NODE via Screen
- Manage your NODE
- Update your Node
- FIX GLIBC 2.39 ISSUE
- Need Help? Join TG Group
- 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
screensessions
| 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
| 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 | Not reliable if uptime is unstable |
Guide on How to buy VPS: Contabo
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
- Go to: https://app.nexus.xyz/nodes
- Click "Add CLI Node" in the dashboard to generate your
Node ID.
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 availablescreensession number. - Replace
YOUR_NEW_NODE_IDwith your actualNode IDfrom the Nexus dashboard.
🔔 Note:
Avoid using duplicate screen session names to prevent conflicts that could stop or disable other running 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 |
How to Update:
- Delete old
screen:
screen -XS nexus1 quit
- Download and install the latest
CLI:
curl https://cli.nexus.xyz/ | sh
source ~/.bashrc
- Create new
screen:
screen -S nexus1
- 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
- Install required packages:
sudo apt update
sudo apt install -y gawk bison gcc make wget tar
- 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
- Create a build directory:
mkdir glibc-build
cd glibc-build
../configure --prefix=/opt/glibc-2.39
- Compile and install (this will take time depending on CPU):
make -j$(nproc)
sudo make install
cd ~
- Create screen session:
screen -S nexus1
- Run the Nexus Node:
→ Replace
<your-node-id>with your actualnode 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
- More Info's at Official Docs
- Nexus Official Discord
- Nexus Official Twitter



