Block Rewards Nomination Eligibility Status

The Block Rewards Nomination Eligibility Status section provides an overview of whether your worker meets the requirements to participate in block rewards. Below are the criteria, with examples as shown in the image for clarity:

Eligibility Requirements

1️⃣ Cluster Creation Test: Passed 

• Explanation: This verifies that the worker has successfully joined the IO.net cluster. A passed test ensures the worker is properly configured and ready to operate within the cluster.
• Action Needed: If this fails, check your worker’s setup and network configuration.

2️⃣ SOL Wallet Address: Associated Intro Statement

• Explanation: The worker must be linked to a valid Solana wallet address to receive block rewards. This ensures the payout system knows where to send earned rewards.
• Action Needed: Associate a wallet address through the profile dashboard if not already linked.
  
  

We do not support Exchange Deposit Addresses (custodial wallets) for recieving Block Rewards.
If your account in Account Settings is linked to an Exchange Deposit Address, you will be unable to claim Block rewards, participate in seasonal events, or receive worker earnings. To ensure uninterrupted access to these benefits, please update your wallet to a Self-Custodial Wallet as soon as possible.

3️⃣ Processor Eligible:  (e.g.GeForce RTX 4090) 

• Explanation:  In this case, the GeForce RTX 3070 is eligible for block rewards.
• Action Needed: If marked ineligible, verify your device compatibility with IO.net’s supported hardware list.

• Explanation: The device’s connectivity tier must be greater than 0 to qualify.
• Action Needed: If this fails, check your internet connection speed and stability. Upgrade your connection if needed.
  
  

5️⃣ Uptime: Device Has Been Up for More Than 5 Hours

• Explanation: The worker must maintain at least 5 hours of continuous uptime to demonstrate reliability. If the worker is restarted, the uptime counter resets, and the device must complete another uninterrupted 5-hour period to meet this requirement. 
• Action Needed: Ensure the device runs continuously.
  
  

6️⃣ PoW (zkTFLOPs Proof): Last Task Valid and Within Current Hour

• Explanation: This ensures that the worker has completed the most recent Proof-of-Work (PoW) task successfully and within the current hour. It confirms the worker's ability to contribute to the network in real-time.
• Action Needed: If this fails, check your worker logs for errors in PoW tasks. Ensure GPU and CPU resources are properly configured. If still failing please check out:
  
  Windows - Why Is My Worker Failing PoW (Proof of Work)
  Linux - Why Is My Worker Failing PoW (Proof of Work)
  
  

7️⃣ Device has <4 VRAM test failures (2) or last failure was over 12 hours ago

• Explanation: Passing the VRAM test is required for Block Reward eligibility. The test ensures the device can join clusters, maintain participation, and successfully complete VRAM-utilizing tasks. Devices are allowed up to 3 failures per calendar month. On the 4th failure, Block Reward eligibility is suspended for 12 hours but reinstates automatically if no additional failures occur.

• Action Needed: Ensure the device has a stable network connection and close all non-essential applications, leaving only Docker/Docker Desktop and the worker containers running.   

8️⃣ Device Has Sufficient $IO Stake: (e.g 400/400)

• Explanation: A minimum amount of $IO tokens must be staked for the worker to qualify for block rewards. In this case, the required stake of 400 $IO is met.
• Action Needed: If the stake is insufficient, deposit the required $IO.