Skip to main content

io.net

io.net (IO) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

io.net — an AI/Compute | Infra project: an “open source AI infrastructure platform” and a marketplace/orchestrator for access to distributed GPU resources and deployment of AI workloads. Token: IO (SPL, Solana).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a platform that provides fast access to a large pool of GPUs/CPUs (“30,000+ GPUs” claimed) and allows running AI workloads (containers/VMs/clusters).
  • Who it’s for: AI teams/startups and GPU providers (data centers/miners/private clusters).
  • Why onchain/token: Tier‑1 docs describe “TNE On Chain” — records of bookings/payments/refunds and $IO repurchase onchain on Solana (escrow via smart contracts). The IO token is also used in the incentive model (VDP), while some of the token mechanics in the VDP are described as not publicly disclosed.
  • What you can actually touch (Tier‑1): the cloud.io.net interface (creating a container deployment), the worker.io.net and explorer.io.net portals.

How it works (very briefly)

  1. The user does: selects the deployment type (container/VM/clusters) and requests resources for an AI task.
  2. The system does: connects compute from many independent GPU/CPU suppliers around the world and deploys the selected workload (as claimed on the website).
  3. The user gets: compute resources for training/inference and infrastructure to run them.
  4. Where the blockchain is: Tier‑1 describes an onchain layer of financial transactions (bookings/payments/refunds/repurchases) on Solana + the IO SPL token.
  5. Token role: Tier‑1 docs describe payment for compute with the $IO token (alongside USDC/fiat), and the Tier‑1 VDP confirms payouts/rewards in IO.

Quick links: AI thesis fit

Project passport

Field Value
Project name io.net
Also known as (aliases) IO Net | IO
Logo (logo) ../assets/49_io-net_logo.png
Token symbol (ticker) IO
Category AI/Compute | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) SPL
Token contract BZLbGTNCSFfoth2GYDtwr7e4imWzpR5jqcUuGEwr646K
Token model (token_type) utility (payments + staking + rewards)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) rewards in IO for reports/vulnerabilities (VDP); $IO and $IOSD are mentioned (VDP)
Governance —
Admins/keys —
Audit —
Bug bounty yes (VDP)
Team (team) —
Funding (investors/funding) —
AI component (ai_component) GPU/compute for AI/ML workloads
Use‑case (use_case) deploy AI workloads on GPUs
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

io.net positions itself as an “open source AI infrastructure platform” — an infrastructure layer that aggregates compute resources (primarily GPUs) from independent providers and makes them available to AI teams “on demand”. Unlike centralized clouds, the claimed idea is: more GPU sources → lower price/faster access/less dependence on a single provider.

In product form, this looks like a set of web interfaces:

  • Cloud UI (containers/VMs/clusters, etc.),
  • Worker portal (connecting a “worker”/device as a resource provider),
  • Explorer (an overview of the network/devices/clusters/inferences — per the UI).

Features/modules

  • GPU catalogs/deployments (Tier‑1): containers, virtual machines, Ray clusters (as items on the landing page).
  • Worker onboarding (Tier‑1): connecting a new worker/device via the portal.
  • Explorer (Tier‑1): an overview of supply/geographic distribution and network entities (per the UI).
  • Open‑source artifacts (Tier‑1): public repositories for installation/demos/metrics/docs in the GitHub organization.

Typical scenarios

  • Scenario 1 (AI team): selects the deployment type → spins up a container/VM/cluster → runs training/inference.
  • Scenario 2 (GPU provider): connects a worker → publishes the resource → receives payouts/incentives (the general model is described in the VDP).
  • Scenario 3 (observer): views the geographic distribution/devices/clusters via the Explorer.

Getting started (wallet/network)

  • What you need: an account/login for Cloud/Worker/Explorer (per the UI); to participate in the onchain part of the token — a Solana wallet.
  • Network/chain: Solana for the IO token.
  • Fees: Solana fees for operations with the token; compute fees/prices depend on the io.net product (not extracted as Tier‑1).

Architecture/tech (non‑AI)

  • Components: web portals (Cloud/Worker/Explorer), the compute orchestration infrastructure, a pool of independent GPU/CPU providers, the IO token (Solana) and offchain services.
  • Participant roles: compute customers (AI teams), resource providers (workers/nodes), product operators.
  • Where logic runs: compute and orchestration — offchain; Tier‑1 also describes onchain accounting of financial transactions (bookings/payments/refunds/repurchases) on Solana.
  • Dependencies: Solana (token), web infrastructure, GitHub repositories/scripts.

Token/economics (expanded, no forecasts)

  • Token utility: Tier‑1 docs describe payment for compute with the $IO token (with zero fees compared to USDC), and the Tier‑1 VDP confirms payouts/rewards in IO.
  • Protocol necessity drivers: the token is used both as a payment option and as an incentive/reward instrument; at the same time, some of the token mechanics ($IO mining) are described as not publicly disclosed in the VDP.
  • Who pays fees: participants of onchain transactions on Solana (IO transfers).
  • Where fees go: — (not established).
  • Issuance/burn: — (not extracted as Tier‑1).
  • Security/incentive mechanisms: the VDP describes IO as the reward currency; incentives for uptime/performance via $IOSD are also claimed (without details).
  • Distribution/vesting: —.
  • Treasury: —.

Governance

  • Who makes decisions: — (not established per Tier‑1).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: there is a vulnerability disclosure policy (Tier‑1).
  • Incidents: — (not established).
  • Threat model: centralization of the web infrastructure/portals, opacity of the token mechanics ($IO “mining not publicly disclosed” in the VDP), risks of compute suppliers and of task execution quality.

Project status and timeline

  • Current status: the product interfaces are available; the IO token is deployed on Solana (Tier‑1).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: Solana (token), the Ray ecosystem (mentioned in the docs as motivation/origins), GitHub repositories and web portals.
  • Partners: the landing page lists “Trusted by …” (Solana and others), but partnership details were not analyzed in this verification.
  • Where it’s actually used: as a compute platform for deploying AI workloads and as a network of workers/devices connected via the portal.

AI component of the project

  • What is real AI here? Tier‑1 positioning: an “AI infrastructure” platform for running AI workloads on GPUs and accessing open‑source models (as a compute layer).
  • What is truly onchain? Tier‑1 confirms the IO SPL token on Solana and describes “TNE On Chain” as onchain accounting of financial transactions (bookings/payments/refunds/repurchases) on Solana.
  • Why is a token needed? Tier‑1 docs describe payment for compute with the $IO token (as an option), and the Tier‑1 VDP confirms payouts/rewards in IO.
  • Red flags (based on the information found): opacity of some of the token mechanics (“$IO token mining not publicly disclosed” in the VDP), centralization of the web services/portals, and the need to separately verify which parts of the protocol (besides financial transactions) are truly onchain.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform provides a compute layer for AI: deployment of AI workloads on GPUs/CPUs (training/inference) and integration with familiar workflows (per the description).
  • Evidence: Tier‑1 — https://io.net/
  • Why sufficient / why not (one line): Tier‑1 describes a specific function — access to GPUs and deployment of AI workloads.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the public product interfaces show that one can create a deployment and connect a worker/view the network.
  • Evidence: Tier‑1 — https://cloud.io.net/cloud/container/create-cluster, https://worker.io.net/worker/devices, https://explorer.io.net/explorer/home
  • Why sufficient / why not (one line): these are reproducible “what you can touch” product artifacts.
  • Conflict note (if any): some features require a login.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://io.net/
  • Why sufficient / why not (one line): Tier‑1 has no quality metrics for the AI component (it is an infra layer, not a model).
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): the extracted Tier‑1 sources do not contain a sufficient technical description of the protocol/market architecture (there is high‑level marketing and the UI).
  • Evidence: Tier‑1 — https://docs.io.net, https://github.com/ionet-official
  • Why sufficient / why not (one line): without clear architectural specifications/an execution model we set 0.
  • Conflict note (if any): there are repositories on GitHub, but the architecture was not fully reconstructed from them in the current verification.

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: token IO (SPL): BZLbGTNCSFfoth2GYDtwr7e4imWzpR5jqcUuGEwr646K
  • Evidence: Tier‑1 — https://solscan.io/token/BZLbGTNCSFfoth2GYDtwr7e4imWzpR5jqcUuGEwr646K
  • Why sufficient / why not (one line): the onchain fact of the token is verifiable via the explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the Tier‑1 documentation describes “TNE On Chain”: records of bookings/payments/refunds and $IO repurchase “on-chain” on Solana (escrow via smart contracts).
  • Evidence: Tier‑1 — https://docs.io.net/docs/tne-on-chain
  • Why sufficient / why not (one line): Tier‑1 directly describes an onchain transaction system for bookings/payments/repurchases (this is more than “just a token”).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core function of the compute platform is described as offchain; without a blockchain the product could be preserved (with different trust trade‑offs).
  • Evidence: Tier‑1 — https://io.net/
  • Why sufficient / why not (one line): onchain criticality is not proven by Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, IO (SPL), on Solana.
  • Evidence: Tier‑1 — https://solscan.io/token/BZLbGTNCSFfoth2GYDtwr7e4imWzpR5jqcUuGEwr646K
  • Why sufficient / why not (one line): we confirm the onchain fact of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): Tier‑1 docs describe payment for compute in IO Cloud with the $IO token (and alternatively USDC/fiat), with zero fees when paying with $IO.
  • Evidence: Tier‑1 — https://docs.io.net/docs/io-cloud-payments
  • Why sufficient / why not (one line): this is a direct Tier‑1 description of the payment rail for compute with the option to pay in $IO.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): the VDP describes a token incentive model ($IO/$IOSD) and reward payouts in IO (including for security reports).
  • Evidence: Tier‑1 — https://io.net/vulnerability-disclosure-policy.pdf
  • Why sufficient / why not (one line): Tier‑1 directly indicates the payment of rewards in IO.
  • Conflict note (if any): “$IO token mining not publicly disclosed”.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the IO token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — https://io.net/
  • Why sufficient / why not (one line): there is no description of a DAO/voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established as a strict statement per Tier‑1.
  • Evidence: Tier‑1 — https://io.net/vulnerability-disclosure-policy.pdf
  • Why sufficient / why not (one line): Tier‑1 describes incentives/rewards but does not compare them with alternatives.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://io.net/ Tier‑1: “AI infrastructure platform” positioning, access to GPUs, deployment types, links to the product interfaces.
Tier‑1 https://cloud.io.net/cloud/container/create-cluster Tier‑1: a reproducible product artifact (the container deployment interface).
Tier‑1 https://worker.io.net/worker/devices Tier‑1: the interface for connecting a worker/resource provider.
Tier‑1 https://explorer.io.net/explorer/home Tier‑1: the network explorer/dashboard (devices/clusters/inferences per the UI).
Tier‑1 https://github.com/ionet-official Tier‑1: open‑source artifacts (scripts/demos/docs) from the verified organization.
Tier‑1 https://io.net/vulnerability-disclosure-policy.pdf Tier‑1: VDP/bug bounty; mention of $IO/$IOSD and payouts in IO; program terms.
Tier‑1 https://solscan.io/token/BZLbGTNCSFfoth2GYDtwr7e4imWzpR5jqcUuGEwr646K Tier‑1: onchain fact of the IO SPL token on Solana.
Tier‑1 https://docs.io.net/docs/tne-on-chain Tier‑1: “TNE On Chain” — records of bookings/payments/refunds and $IO repurchases “on-chain” + escrow via smart contracts.
Tier‑1 https://docs.io.net/docs/io-cloud-payments Tier‑1: IO Cloud Payments — payment for compute with $IO (0 fee) / USDC (2% fee) / fiat and a reservation fee of 0.25%.
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top