Live prices are currently unavailable — the exchange feed could not be reached and no recent cached reading is held.

Research · Altcoins

ICP supply and network economics

Two mechanisms connect the Internet Computer's operation to its token: the rewards paid to node providers, and the cycles burned by canisters. Both are documented, both affect supply or demand for the token, and neither is a price signal on its own.

Last reviewed 2026-09-21Source: ICP Developer Docs — node rewards, cycles and the NNS; ICP token documentationMechanisms are described from the project's own documentation; no reward rate, burn rate or price is quoted.

Dataset, period and method

This page is a mechanism description rather than a data series. Its sources are the Internet Computer's own developer documentation and the project's token documentation, and its method is to set out how each mechanism works and then state precisely what it does and does not imply about market data. Where a figure would be needed to make a quantitative claim, the page declines to make the claim rather than sourcing a number that changes.

The period covered is the network's operation to the review date. The mechanisms described have been in place since launch, though their parameters are set by the network's governance system and can change through proposals. That is a reason to describe the mechanism rather than a current setting.

The distinction the page maintains throughout is between a mechanism that affects supply, one that affects demand, and one that affects neither. Conflating them is the most common error in writing about network economics, and it is what produces claims that a burn "supports the price" without any evidence for the link.

The two mechanisms

The two economic mechanisms that connect the Internet Computer's operation to its token, and what each one affects.
MechanismHow it worksWhat it affects
Node-provider rewardsThe network pays the operators of the machines that run its subnets, in ICP, on a schedule set by governance. The reward is compensation for providing hardware and bandwidth.Supply: newly distributed tokens enter circulation. It is a cost of running the network rather than a market event.
Cycles burnCanisters pay for computation and storage in cycles, which are obtained by converting ICP. Converted ICP is burned and cannot be converted back.Demand for the token: running an application requires acquiring and consuming ICP. The burn removes tokens from circulation permanently.
Governance parametersThe Network Nervous System sets reward rates, cycle costs and other economic parameters through proposals.Both, indirectly: a change in a parameter changes the rate at which either mechanism operates.

Last reviewed 2026-09-21Source: ICP Developer Docs — node rewards, cycles and the NNSDescribes mechanisms and their direction of effect; no rate or quantity is stated.

The node-reward mechanism is a supply-side flow. Tokens are distributed to providers as payment for a service, and those tokens then belong to the providers, who may hold or sell them. The mechanism is a cost of production in the ordinary sense: the network must pay for the hardware that runs it, and it pays in its own token.

The cycles burn is a demand-side mechanism. To run a canister, a developer must obtain cycles, and obtaining cycles means converting ICP, which burns it. The burn is therefore a function of how much computation the network is actually doing. It is the closest thing the network has to a usage-linked sink for the token.

The cycles page covers the unit and its peg in detail, and the reverse-gas model page covers who bears the cost. The point to carry forward is that the burn is proportional to usage, so its effect on supply depends on how much the network is used rather than on how the token is trading.

How the mechanisms interact with market data

The honest answer is that the interaction is real but small relative to market-wide flows, and that its size is not something this page can quantify. A burn that removes tokens from circulation reduces supply, and a reward that distributes tokens increases it. Both are flows against a stock that is large by comparison, and both operate on a schedule that is slow relative to the daily price series.

That means a reader should be sceptical of any claim that a change in the burn rate or the reward schedule explains a price move. The mechanisms are documented and their direction of effect is clear, but the magnitude of that effect relative to market-wide demand is not established by the documentation, and this page does not assert it.

What the mechanisms do explain is the structure of the token's supply over time. The reward schedule is one reason circulating supply grows, and the burn is one reason it grows more slowly than it otherwise would. That is the correct level of claim: a description of the supply mechanism, not a forecast of price.

Limitations

The parameters of both mechanisms are set by governance and can change. A description of the mechanism is therefore durable in a way a description of its current setting is not, which is why this page describes the former.

The page makes no quantitative claim about the size of either flow. Doing so would require a figure that changes and a comparison against market-wide volume that this site does not publish for ICP.

Finally, the mechanisms are not independent of the market. A higher token price makes the same reward budget buy less provider service, and a lower price makes running a canister cheaper in fiat terms because the same cycles cost fewer tokens. Those feedback loops are real, and they are a reason to be careful about treating any single mechanism as a one-way influence on price.

Sources and references

The mechanisms are described from the Internet Computer's own documentation. No rate, quantity or price is quoted, because each is set by the network and changes over time.

  • Cycles, the peg and the burn. ICP Developer Docs, Cycles: the unit, the conversion from ICP, and the one-way flow that makes the burn permanent.
  • Node providers and rewards. ICP Developer Docs, Nodes and node providers: how the machines that run subnets are supplied and compensated.
  • Governance of economic parameters. ICP Developer Docs, Governance: the proposal system through which reward rates and cycle costs are set.
  • ICP token distribution. Internet Computer, ICP tokens: the project's own account of the token's distribution and release.