io.net (IO): tokenomics, risks and score
A GPU aggregation network pooling capacity from data centres, mining operations and individuals into clusters for machine learning workloads.
What io.net is, and what it does
This is an AI or compute network. It coordinates machine learning work, hardware or data across many independent participants instead of one company's data centre.
What the IO token itself does: Fees are used to buy and destroy the token, so usage of the protocol permanently reduces the supply.
Where it runs: Solana. Mechanism: Aggregated GPU compute network on Solana. It has been running since 2024, so roughly 2 years.
The facts
- TICKER
- IO
- SECTOR
- AI and compute
- CHAIN
- Solana
- LAUNCHED
- 2024, so around 2 years of operating history
- MECHANISM
- Aggregated GPU compute network on Solana
- MAXIMUM SUPPLY
- 800 million
- VALUE CAPTURE
- Buyback burn
- UPGRADE CONTROL
- Team controlled
- VESTING
- Heavy overhang
- LIQUIDITY BAND
- Micro cap. Thin, often a single venue or pool. Treat the quoted price as indicative only.
How the score breaks down
Each dimension is explained on the directory page, and the reasoning behind it is taught in the Academy research process.
Supply and value capture
A hard maximum supply that cannot be raised without the agreement of essentially every participant. Fees are used to buy and destroy supply, so usage reduces the number of tokens outstanding.
The founding team retains control over upgrades or parameters. Ownership is heavily concentrated. A small number of wallets hold enough to determine the price on their own.
Where it is strong and where it is not
- Supply is capped, so holders are not diluted indefinitely
- The token captures real protocol revenue rather than relying on speculation alone
- Audited, with published reports
- Heavily concentrated ownership means a few wallets control the outcome
- Significant supply is still scheduled to unlock, which is a structural headwind
- Upgrade control sits with a small group, so the rules can change
- Thin liquidity. Check order book depth before assuming you can exit
Incident history
An API vulnerability was exploited to register large numbers of fake GPU devices, inflating reported network capacity and raising questions about supply verification.
Our read
The main risk
A prior incident involving fabricated capacity, heavy unlocks, and competition with hyperscale providers.
Before you buy anything
Check the contract address against the project's own documentation rather than a search result or a screener link, since impersonation tokens with identical names and logos are listed constantly. Check the order book depth before assuming you can exit at the quoted price. And write down what would make you wrong before you buy, not after. The Academy thesis module covers why that single habit protects more capital than any indicator.