Internet Computer (ICP)

What Internet Computer is

Internet Computer is a public network that runs full applications, front end included, as smart contracts. ICP is its native asset. Its documentation gives ICP four jobs: it moves value, it converts into the fuel that powers computation, it is staked into voting neurons to govern the network, and it pays the operators who run the hardware (source: internetcomputer.org, ICP tokens page, read September 2026).

The design goal is that a dapp should be served directly from the chain rather than from a company's servers, with no cloud provider in the path. The documentation calls the result a "sovereign cloud."

For where to buy Internet Computer from your country or state, see the availability tables on this page and the venues at Exchanges.

How it works

The network is divided into subnets. The documentation defines a subnet as "a group of nodes that run their own instance of the ICP consensus protocol," and states that "subnets typically range from 13 to 40 nodes," with most application canisters deployed on 13-node subnets for cost efficiency. Canisters are the network's smart contracts: they hold code and state together and can serve web requests directly.

Each subnet reaches consensus independently. The documentation states that "each subnet runs a consensus protocol that produces one finalized block per round, approximately every 1 second," and is precise about what that finality means: "ICP provides cryptographic (not probabilistic) finality: once your update call returns, the state change is committed." That is a different guarantee from a chain where finality accumulates with each additional confirmation.

Chain-key cryptography is how a subnet of many machines behaves like a single signer. The documentation describes it as splitting a key into shares "distributed across the subnet's nodes using threshold cryptography," so an external verifier checks "one signature against one public key" regardless of subnet size. That lets a browser verify a response without tracking the subnet's membership.

Boundary nodes sit at the edge. The documentation describes them as an "HTTP gateway" and "API endpoint" that translate ordinary web requests into canister messages and route them, and notes that they "cannot modify canister state."

The economics run on a reverse gas model, and this is the most consequential design decision for anyone using an application on the network. On most chains a user attaches a fee to every interaction. Here, the documentation explains, "the software that powers each app pays for its own computation from a balance of cycles, maintained like a built-in battery that can be recharged." The reason it matters is stated just as directly: "without reverse gas, every web request would need a wallet signature."

Cycles are bought with ICP at a fixed exchange rate against a unit of account rather than against a dollar amount of the token. The documentation states the conversion as "ICP worth 1 XDR produces 1 trillion cycles," and draws the consequence: "cycles have constant value, so compute prices don't track token volatility." A developer's hosting bill therefore does not move with the market price of ICP, even though the tokens spent to pay it do.

Governance is the Network Nervous System, which the documentation calls "a fully autonomous, onchain governance organization built directly into the Internet Computer protocol" and "the brain of the Internet Computer network." Holders stake ICP into voting neurons under a liquid democracy model, voting themselves or following others. The capability that distinguishes it is upgrade authority: "proposals can update the replica software itself — no hard forks." It also admits node providers, described as being "voted into the network by the governance system (NNS)" after meeting hardware standards, a process it calls "deterministic decentralization."

Applications can adopt the same pattern through a Service Nervous System, after which "control of that application is handed over to a fully decentralized digital governance system — no backdoors, no single operator, no foundation."

Supply and tokenomics

ICP is issued to pay for governance participation and for hardware, and destroyed when computation is paid for. Both sides of that loop are usage-driven rather than fixed by a schedule.

The burn is the interesting half. Every cycle spent on computation came from ICP that was destroyed to create it, so the documentation's claim follows directly: "the more compute the network performs, the more ICP gets burned," and "the balance has already tipped deflationary several times." Net supply change is therefore a function of how much the network is actually used against how much is paid out in governance and node provider rewards. It is not a fixed rate, and a period of deflation is not a guarantee of the next one.

Node provider rewards are quoted "in constant-value terms," meaning the operator is paid a value rather than a token quantity. That protects hardware economics from token price swings and moves the variability onto issuance.

History

The Internet Computer was built around a claim most blockchains do not make: that the chain itself should host the whole application, not just its settlement logic. Serving a web page from a canister, rather than from a server that talks to a chain, is what the architecture is organized around, and the reverse gas model exists because that goal is impossible if every page view needs a wallet signature.

Scaling was approached horizontally from the start. Rather than making one chain faster, the network adds subnets, each running its own consensus instance. Chain-key cryptography keeps that from becoming a verification problem: however many subnets exist, a client checks one signature against one public key.

Governance was designed to remove the fork as a coordination tool. Because proposals can upgrade the replica software that nodes run, protocol changes ship as votes rather than as coordinated client releases. The Service Nervous System later extended the same machinery to applications built on top.

Risks and what to watch

Voting power concentration is therefore the first thing to watch. Liquid democracy means many holders follow the votes of a few, so effective control can be more concentrated than the distribution of staked ICP suggests.

Node provider admission is also a governance decision. The documentation describes providers as being "voted into the network by the governance system," which makes the operator set a function of NNS outcomes rather than of open permissionless entry. The stated aim, "deterministic decentralization," is a design goal; whether the resulting set is diverse across jurisdictions and owners is something to verify rather than assume.

Subnet size sets the security budget for whatever runs on it. Most application canisters sit on 13-node subnets, which have smaller fault tolerance than 40-node ones. If an application matters, the subnet it runs on is part of its threat model.

Staked ICP in a neuron is not immediately spendable. Neurons dissolve over a configured period, and the minimum and maximum dissolve delays are not published on the pages read for this entry, so no figure is given here.

Finally, the reverse gas model shifts a cost from users to developers. An application whose cycle balance runs out stops running, an operational risk that does not exist where the user pays per interaction.

Frequently asked questions

What is the reverse gas model?

The application pays for its own computation instead of the user paying a fee per interaction. The documentation describes each app maintaining a balance of cycles "like a built-in battery that can be recharged," which is what allows a page to be served without a wallet signature.

What are cycles and how do they price compute?

Cycles are the unit computation is billed in. ICP is converted into cycles at a rate fixed against a unit of account: "ICP worth 1 XDR produces 1 trillion cycles." Because the rate is fixed that way, compute prices do not move with the token price.

Does using the network reduce ICP supply?

Converting ICP into cycles destroys it, so more computation means more ICP burned. The documentation states that the balance between burning and issuance "has already tipped deflationary several times." It is usage-dependent, not a fixed schedule.

Where can you buy Internet Computer?

Availability depends on your country or US state. See where to buy Internet Computer for the exchanges serving your jurisdiction, and Exchanges to compare fees and kyc requirements.