Skip to main content

Register a machine

TL;DR

Run one line of code to register your machine.

🌟 Status: Live

This page details the machine registration process, with video and step-by-step guides.

Prerequisites​

Minimum Hardware and port requirements
  • CPUs or vCPUs: β‰₯2
    • GB RAM: β‰₯4
    • SSD storage: β‰₯80GB NVMe Storage
    • Network bandwidth: β‰₯1Gbps unlimited
    • Uptime: β‰₯ 99%
    • OS: Debian (12+) or Ubuntu (22.04+) installation with Linux kernel 6.1+, updated with the latest security patches
  • All traffic allowed on ports:
    • UDP 8472
    • TCP 10250
    • UDP 51820
    • UDP 51821
info

For the incentivized NodeOps Network Testnet, we have dialed down the compute demands as low as possible to enable more of our community to join the Proof of Concept round.

Register a new machine​

Step 1. Create a secret identifier​

Add a machine from our provider dashboard to get a secret identifier for the high-availability Machine you will make available to NodeOps Network Testnet.

tip

Use the "Show me" tab or video if you need assistance.

Step 2. Make the compute available​

info

Your machine will remain in "PENDING" status until the command you generated in Step 2 is executed on that machine.

Run the command provided in Step 2 on the Machine you wish to add, this secret identifies it, and then stake to secure the machine.

To view your machines, click on ACTIVE Machine. New machines can take several minutes to display these details.

tip

Use the "Show me" tab or video if you need assistance.

Gotchas​

Copy error​

An error such as cannot create regular file '/usr/local/bin/atlasnetwork-provider': Permission denied means you didn't create a user account at root for NodeOps Cloud with the correct permissions to run the code.

You can get around this on Ubuntu with sudo. That means:

curl -L https://get.atlasnetwork.dev | sh -s - 9zvmdvJ****Secret*****w9PHZwP

becomes

sudo curl -L https://get.atlasnetwork.dev | sudo sh -s - 9zvmdvJ****Secret*****w9PHZwP

Rejected machines​

Your machine will be rejected if:

  • It runs workloads in addition to the NodeOps Network assigned loads
  • If SWAP is enabled

Next steps​

Congratulations! You are providing decentralized compute via the NodeOps Network's Protocol on Arbitrum Testnet.

Consider: