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.
Top Risks
1
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.
2
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.
3
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.
4
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.
Risk Breakdown
Frequently Asked Questions
Is io.net safe to use?
io.net receives a C+ risk grade (42/100) from Hindenrank, where lower scores indicate lower risk. 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. io.net is a Solana-based decentralized GPU computing platform that aggregates underutilized GPUs worldwide for AI and machine learning workloads. Backed by $30M from Hack VC and Multicoin Capital at a $1B token valuation, the network faced a major credibility crisis in April 2024 when 1.8 million fake GPUs were found attempting to connect, revealing that reported node counts were massively inflated. Its C+ grade reflects this track record incident, the ongoing challenge of verifying decentralized GPU supply, and the early-stage nature of compute demand, partially offset by the team's transparent postmortem response and introduction of new verification mechanisms including the Incentive Dynamic Engine.
What are the main risks of using io.net?
The key risks identified for io.net are: (1) In April 2024, io.net discovered approximately 1.8 million fake GPUs attempting to connect to the network, revealing that initial reported node counts of 500,000+ were inflated. Actual verified nodes numbered approximately 120,000, severely damaging metric credibility. (2) Verifying real GPU hardware on a decentralized network remains fundamentally challenging. Despite a new Proof of Work verification mechanism, the economic incentive to register fake nodes persists as long as token emissions reward supply-side growth. (3) The Incentive Dynamic Engine adjusts token emissions based on compute demand, but if demand metrics can be gamed, the adaptive mechanism could perpetuate inflationary emissions without genuine usage. (4) Investor and team tokens (approximately 34% of total supply) began unlocking in July 2025, creating sustained sell pressure during a critical period when the network needs to demonstrate organic growth.
What is io.net's risk score breakdown?
io.net scores 42/100 across eight risk dimensions: Mechanism Novelty: 3/15, Interaction Severity: 6/20, Oracle Surface: 2/10, Documentation Gaps: 4/10, Track Record: 6/15, Scale Exposure: 7/10, Regulatory Risk: 4/10, Vitality Risk: 10/10. The highest risk area is Vitality Risk at 10/10.
How does io.net compare to other DeFi protocols?
Among 68 rated DeFi protocols on Hindenrank, io.net ranks #57 by safety (lowest risk score = safest). Its 42/100 risk score and C+ grade place it among the riskier DeFi protocols.
Has io.net ever been hacked or exploited?
io.net scores 6/15 on the Track Record risk dimension, indicating some history of security incidents or exploits. Higher scores reflect more severe or frequent incidents. Review the full risk report for details.