Providers

Overview

With Atlas Network we aim to create a diverse and decentralized pool of infrastructure Providers, which form one core aspect of our marketplace. This section will provide the details around the architecture, various operational mechanics, and an incentivization model designed to create a reliable Provider pool.

Hardware requirements

The minimum hardware requirements for a provider is:

• Two vCPUs
• 4 GB Memory
• ≥80GB NVMe Storage
• ≥1Gbps unlimited network bandwidth
• 99% Uptime

Provider Capacity

In Atlas Network, the capacity that every provider adds to the pool is measured in a unit called a Compute Unit (CU). One CU is a machine with one CPU, 2GB RAM, and 30 GB storage.

1 CU = 1 CPU | 2GB RAM | 30 GB Storage

Every machine a provider adds gets broken down into the number of CUs; the total of all the minimum CUs is the provider capacity.

Example:
One provider brings three machines to the pool.

Machine1: 1 CPU | 4 GB RAM | 100 GB Storage
Machine2: 2 CPU | 4 GB RAM | 200 GB Storage
Machine3: 4 CPU | 8 GB RAM | 500 GB Storage

CU of Machine1: min(1 | 2 | 3.3) = 1
CU of Machine2: min(2 | 2 | 6.6) = 2
CU of Machine3: min(4 | 4 | 16.6) = 4

The provider capacity = 1+2+4 = 7

Here is another example. Consider a machine with this spec.
4 CPU | 7.57 GB RAM | 150.16 GB Storage

CU: min (4 | 3 | 5) = 3

Staking

In Atlas Network, every provider must stake 2000 $NODE for provider onboarding. For every CU the provider brings to the pool, an additional stake of 20 $NODE for each machine.

In the above example, the provider stakes 2000 $NODE for provider onboarding and stake 20, 40, & 80 $NODE for each machine.

Node Scheduling and Deployment

In Atlas Network, Node operators can choose from several different options for their node deployment. For details refer to Node Operators. Every auto-assign workload deployment happens on a machine best suited for it. The Atlas Network Scheduler is responsible for finding the best machine whenever a new auto-assign workload gets added to the pipeline.

The scheduler logic works in three stages:

1. It searches for all the machines amongst all the providers with free CUs that are more than or equal to the CU requirement for the workload.
2. Next, the scheduler picks the least utilized machine among all these machines.
3. Finally, the machine with the most uptime gets selected from this group for the workload deployment.

The second condition ensures that the workload deployment distribution is fair and does not become concentrated amongst a few providers.

Uptime is a crucial metric for all providers and their machines. It measures the amount(%) of time the machine has been available in the provider pool.

In Atlas Network, we want to put machines with the highest uptime ahead in the workload deployment queue. Since rewards are also dependent on running workloads, providers are incentivized to have machines with the maximum uptime they can.

If more than one machine passes the third condition, the logic will randomly select one machine from this group. Once the final machine is selected, the Atlas Network client receives a deployment request, which triggers the actual deployment process.

Service Level Aggrement(SLA)

Since provider machines will run nodes of various protocols, they must have a high uptime. Providers must ensure that their machines have 99% or more uptime annually. Machines that meet this requirement are chosen for node deployments, which means having a less uptime machine will impact the earning potential.

To maintain a robust network, machines with less than 99% uptime could be kicked out.

Provider Onboarding

The attached video shows the entire provider onboarding process.

Here is a step-by-step guide:

Provider Registration:

1. Go to the Provider dashboard and connect your wallet.

2. Stake the $NODE tokens to start the onboarding process.

3. Continue to create your profile to complete the registration process.

Machine Registration:

NOTE: To add a machine, make sure you are the provider.

1. Start adding your machines (compute infrastructure) using “Add machine.”

2. To add a machine, a call to our MachineRegistry contract gets triggered and completes the machine registry process.

3. Copy the machine setup command and run it on your machine.

4. Your machine will be visible under “All” in the “AWAITING-STAKE” state. Click on “Stake” to start the machine staking process. The machine will change to "CONFIGURING."

5. Wait for the machine to turn to “ACTIVE.”

6. Click on the active machine to pull up its details.

Rewards & Slashing

Coming soon