Internet Computer

DFINITY spent years designing a chain that could serve software and web content. The May 10, 2021 genesis opened the production network and activated the NNS. DFINITY did not vanish at that moment: it continued to research the protocol, write releases, and submit proposals. But authored code is not automatically live code. The formal path to network-level adoption runs through NNS proposals and system-canister execution.

That distinction matters because 'community governed' can be heard as a claim about social influence. The protocol makes a narrower, testable claim: neurons vote, adopted proposal types call specified methods, and the registry propagates the resulting topology or version change. Who holds enough coordinated voting power is a separate empirical question, and the public material reviewed here does not completely identify every beneficial owner.

A canister combines WebAssembly code and persistent state, but it does not run on every Internet Computer node. It is assigned to one subnet, whose members replicate and execute it. The NNS registry links those separate chains into one address space by recording membership, software versions, routing ranges, and assignments.

This architecture enables scaling, while making topology governance consequential. NNS proposals can create a subnet, swap its nodes, recover a stalled subnet, change firewall rules, or reroute canister ranges. Node providers supply machines and registered node operators administer their assigned hardware; neither role alone decides the subnet map.

An ICP balance becomes an NNS vote only after it is locked in a neuron. A neuron needs at least six months of dissolve delay to vote, while longer commitments up to eight years receive more weight; stake, age, and activity rules also matter. Adopted proposals can change protocol canisters, economics, node rewards, and network configuration. They do not automatically replace the controller list of every independently deployed app.

Canisters prepay computation with cycles. One trillion cycles follow one SDR/XDR, and the canister spends them on execution, storage, messages, and cryptographic services. A visitor can therefore call an application without holding ICP. ICP's job is upstream: it can be converted one-way into cycles, staked for governance, or transferred.

Supply follows those uses. Node-provider remuneration and spawned voting maturity create ICP; cycle conversion and some fees destroy it. The official API reading on September 4, 2026 was 556,204,661.33388347 ICP. Treating that number as a fixed maximum would erase the mechanism that produced it.

A controller can upgrade, reconfigure, stop, or delete its canister. Some teams retain that key, some use multisig, some hand control to an SNS, and some remove controllers entirely. Hosting on Internet Computer proves where code executes; it does not by itself prove who governs that code. ICP ownership likewise gives no automatic equity in DFINITY, revenue claim on the foundation, or ownership of the apps sharing the network.