Our Approach to Hardware Verification
Since launching NodeOps Network’s incentivized Testnet, we’ve achieved a significant milestone with over 8,000 rotated active machines in our network.
However, as we edge closer to Mainnet, we must address a critical challenge: not all hardware meets our quality standards.
This is to be expected. Not all providers on the Testnet are experts in their field. Some came for the Node Points, and some came out of curiosity.
But, it’s time to provide decentralized compute that consumers can rely on. Read on to learn about the workflows and agents that we have designed to maintain our stringent Quality of Service (QoS) standards.
Verifying hardware quality
Our response to the challenge of filtering out the providers that genuinely offer quality hardware from those adding subpar machines to our compute pool in hopes of earning rewards is a comprehensive verification process powered by a fleet of intelligent agents.
Ready state verification
Before a machine can join our active pool, the Orchestrator must observe that it can achieve a “ready state”. The Orchestrator monitors for 2 key properties:
Uninterrupted network connectivity.
Sufficient resources: disk storage, memory, and CPU.
Network connectivity checks
We perform rigorous network tests to ensure:
Duplex connectivity with NodeOps Network services.
Ability to resolve external DNS.
Stable internet connectivity, verified by pinging a list of public domains and services to check latency.
Staking requirement
To contribute to Mainnet DePIN Compute, providers must stake a set amount to participate, adding the economic security that backs their commitment to providing a stable service.
Uptime monitoring
We demand 99% uptime from all machines. This statistic is displayed transparently on each machine’s detail page for accountability.
Probationary period
New machines undergo a 24 to 48-hour close monitoring period. This allows us to thoroughly assess their performance before adding them to the active machine set.
Suspension mechanism
Machines that fail to meet our standards are added to a “suspend” list and remain suspended for an entire epoch.
Provider communication
We understand the importance of keeping our providers informed. An automated notification system delivers machine status updates (up, down, or suspended) directly to the provider’s email.
Conclusion
At NodeOps Network, we’re committed to maintaining a high-quality, reliable DePIN generalized compute infrastructure. Our comprehensive verification process ensures that only the highest-quality machines make it into our active pool, providing our users with the performance and reliability they expect from a leading DePIN Compute platform.
By embedding automated checks, we’re building a robust, trustworthy network that can support the growing demands of both the Web3 and We2 ecosystems. As we continue to expand, we remain dedicated to refining our processes, always aiming to deliver the best possible service to our users and fair opportunities to our providers.
Have you joined the incentivized Testnet yet? If not:
Check out the campaigns we are running to battle-test the system.
If you have a couple of spare CPUs on a machine that doesn’t run any other workloads and you can open up the ports, then consider becoming a provider on NodeOps Network’s Testnet to earn some Node Points.
Don’t have a machine? Don’t worry, you can also provide cloud compute.