Elevated risk — major Sybil attack incident undermining metric credibility and early-stage compute adoption, partially offset by transparent incident response, new verification mechanisms, and strong investor backing.
Risk Breakdown
Top Risks
Major Sybil attack in April 2024: approximately 1.8 million fake GPUs attempted to connect to the network, exploiting vulnerabilities in node verification. The true network size was found to be approximately 120,000 verified nodes, far below the initially reported 500,000+, severely undermining credibility of reported metrics.
GPU supply verification remains a fundamental challenge for decentralized compute networks. Despite security patches and a new Proof of Work verification mechanism introduced after the Sybil attack, the difficulty of remotely verifying physical GPU capacity creates persistent gaming risk.
Early-stage network with limited production AI workload adoption. While the network spans 7,000+ GPUs across 50+ countries, real compute utilization and revenue generation metrics are opaque, creating uncertainty about organic demand.
Significant token price decline: IO has fallen substantially from its launch price, with market cap dropping from approximately $860M FDV to $155M circulating market cap, reflecting market skepticism about the project's metrics and adoption trajectory.
Frequently Asked Questions
Is io.net safe to use?
What are the main risks of using io.net?
What is io.net's risk score breakdown?
How does io.net compare to other DeFi protocols?
Has io.net ever been hacked or exploited?
Get risk alerts before it's too late
Weekly grade changes, downgrade alerts, and new protocol risk findings. Free.