Question 1

What is IO?

Accepted Answer

IO is the native token of io.net's decentralized GPU computing network. The network supplies distributed GPU computing power for computing needs such as AI and machine learning, and uses Solana as its on-chain settlement layer; IO therefore serves payments for computing services, supply-side participation, and incentive arrangements within the network, rather than representing a particular GPU or a single AI application. To understand IO, it is important to distinguish between “computing services” and “token mechanics”: users need available GPU computing, providers supply hardware resources, and IO is used to connect payments, collateral, incentives, and related functions. Whether the network generates actual demand for computing will directly affect subsequent revenue-based incentive mechanisms.

Question 2

What is IO used for in the network?

Accepted Answer

IO can be used to pay for io.net GPU computing and fine-grained inference services; node operators can also stake IO as performance collateral. In other words, users obtain computing services through payment, providers participate in the network by supplying resources, and staking makes operators bear token-locking responsibilities related to service performance while providing services. Staking does not simply mean holding tokens for rewards. Here, it is first a collateral arrangement within the conditions for node participation, intended to give nodes greater incentive to maintain stable, reliable service; actual obtainable compensation still depends on the network's service and incentive rules.

Question 3

Which blockchain is IO based on?

Accepted Answer

io.net conducts on-chain settlement on Solana, and IO is the native token of the io.net network. For a network that needs to frequently coordinate distributed devices and computing services, the settlement layer records and completes on-chain token operations related to services; Solana is the settlement infrastructure adopted by the network, which does not mean all GPU computation itself is performed on-chain. Therefore, “on-chain settlement” and “off-chain provision of computing power” should be understood separately: GPU nodes actually provide computing resources, while Solana supports the settlements and token interactions that io.net chooses to place on-chain.

Question 4

How does IDE change IO's economic mechanism?

Accepted Answer

IDE stands for Incentive Dynamic Engine, io.net's demand-driven incentive mechanism. It replaces the former inflationary, fixed-emission approach by linking provider compensation and token economics more closely to actual GPU use and network revenue. Its logic is to first assess whether the network has genuine demand for computing and revenue, then coordinate supply-side compensation and supply-reduction arrangements accordingly; the official materials identify metrics such as utilization as a basis for the system's dynamic balance. Thus, IDE does not pre-commit to a fixed quantity of ongoing emissions, but instead seeks to reduce the disconnect between incentives and actual demand for services.

Question 5

How does IO supply decrease under IDE?

Accepted Answer

Under io.net's published IDE design, providers are paid what they are due first; after that, at least 50% of remaining network revenue is used to reduce IO supply, an arrangement the official page describes as burning. This order is important: it does not first take a fixed share from all revenue, but instead uses the revenue remaining after providers have been paid as the calculation basis. This mechanism links supply reduction to network revenue: without corresponding residual revenue, “at least 50%” cannot be understood as a fixed quantity of IO; even if a supply reduction occurs, it indicates only a mechanism on the token-quantity side and does not by itself establish conclusions about price, earnings, or returns.

Question 6

What changes have occurred in IO's issuance and incentive mechanism?

Accepted Answer

IO's issuance and incentive mechanism has indeed changed directionally: the early model primarily used fixed emissions to incentivize GPU supply, while the subsequent IDE became demand-driven and aims to reduce reliance on token supply created by the old incentive model. This does not treat historical issuance under the old mechanism as having disappeared; rather, it is an economic-model transition: the old model emphasized scheduled emissions, whereas IDE brings provider compensation, actual usage, and residual-revenue supply-reduction arrangements into the same relationship. When reviewing historical data or token narratives, users should avoid treating old fixed-emission parameters as the current incentive rules under IDE.

io.net (IO) Price

io.net (IO) Price Performance

Fear & Greed Index

Why Did io.net (IO) Fall in the Last 24 Hours?

About io.net (IO)

Use Cases and Features

Supply and Issuance Mechanism

How to Buy and Use io.net (IO)

How to Buy

Related Markets

Simple Earn

io.net (IO) Basics & Market Insights

Fundamentals

Market Analysis

Frequently Asked Questions About io.net (IO)