On this page
Internet Computer is a blockchain network designed to run applications and store their state across groups of replicated computers. Its native ICP token supports network governance and can be converted into cycles, the computational fuel consumed by applications. Owning ICP and paying for an application's operation are related activities, but they are not the same thing.
The network's public genesis was May 10, 2021, according to the Internet Computer's technical overview. Current developer documentation describes an operating platform with application programs called canisters, subnet infrastructure and on-chain governance. ICP remains its native asset; a token with the same ticker on another network should not be assumed to be the same asset.
What the network actually runs
A canister combines program code with persistent state. Applications can use canisters for backends and other services, while the network replicates their operation across a subnet. A subnet is a group of nodes maintaining its own blockchain and running an independent instance of the consensus protocol.
According to the developer documentation, subnets can operate in parallel and communicate with one another. This design distributes work across the network, although an individual application's performance still depends on its architecture and subnet resources. Describing the network as a computer does not mean that every application has unlimited capacity.
The consensus documentation explains that nodes agree on the order of messages and execute the resulting state transitions consistently. It uses notarization and finalization rather than proof-of-work mining. The stated safety model assumes fewer than one-third of a subnet's nodes are faulty. That assumption is part of the design, not an assurance that every application built on it is secure.
ICP and cycles have different jobs
ICP can be transferred, staked for governance or burned to create cycles. The network-economics documentation describes cycles as computation fuel whose accounting value is tied to the IMF's XDR currency basket. Canisters consume them to pay for resources.
This separates application resource accounting from the token's market price. It does not freeze every application's total costs: resource consumption, pricing rules and software design still matter. Nor does network usage mechanically establish a particular ICP price.
The same documentation identifies sources of new ICP, including node-provider remuneration and realized governance rewards, alongside burns from cycle conversion and transaction fees. Supply therefore changes through both issuance and destruction. An increase in activity should not be presented as proof that burns must exceed all new issuance.
Governance creates rights and withdrawal conditions
The Network Nervous System, or NNS, governs the protocol. Holders stake ICP in neurons, which participate in proposals and voting. The separate Service Nervous System framework lets individual applications establish their own governance; an application's governance token is not automatically ICP.
Staking involves a dissolve delay: a waiting period connected to retrieving locked tokens. Voting power depends on more than the token amount, and following other neurons can delegate decisions on particular topics. The current governance documentation should be checked before making a commitment because parameters can change through governance.
Governance rewards accumulate as maturity rather than immediately appearing as spendable ICP, according to the economics documentation. Realizing rewards and unlocking an existing stake are distinct events. Neither should be confused with a fixed corporate-style dividend or a promise of a particular yield. The staking guide explains why withdrawal terms matter alongside displayed rewards.
Identify the native token before transferring it
The official system-canister registry identifies the native ICP ledger as ryjl3-tyaaa-aaaaa-aaaba-cai. This is an Internet Computer canister identifier, not an Ethereum contract address. A receiving service must support the intended network and account format.
Internet Computer also supports assets representing value from other chains. Its Chain Fusion documentation describes chain-key tokens such as ckBTC and ckETH as representations backed by the corresponding external assets. Those tokens have different identities and mechanisms from ICP itself. The bridge and wrapped-asset guide provides useful context for checking what arrives at a destination.
Wallet and exchange support must be checked for the specific asset and route. A market listing is not proof that every deposit network is open or that a wallet supports every canister-based token. Avoid sending based only on a ticker, and confirm custody and recovery arrangements before committing funds.
The risks sit at several levels
ICP exposes holders to market-price and liquidity risk, changing supply, governance decisions and possible withdrawal delays. Applications add their own code, access-control and operational risks. Network replication cannot repair a flawed application design by itself.
The project's technical overview records roughly 469.2 million ICP at genesis in May 2021. That historical starting supply is not today's total. The original distribution and any remaining holder-specific vesting arrangements are separate from ongoing protocol issuance. This profile does not assert a complete current unlock calendar or a live supply total. Those require dated ledger and allocation evidence, while the mechanisms above explain why supply and available balances can change.
Internet Computer's distinctive proposition is to place more application execution on replicated blockchain infrastructure. Assessing that proposition means examining the application, its governance and its actual resource needs, rather than treating the ICP token as a substitute for that work.