Internet Computer (ICP): NNS Neurons and Governance Locks

Voting power follows stake and lock conditions

ICP holders can lock tokens in Network Nervous System neurons. Voting power depends on stake, dissolve delay and age under current rules. Neurons can vote directly or follow other neurons by topic. Rewards and maturity are protocol accounting outcomes, not guaranteed fixed returns.

The NNS governs protocol upgrades, subnets, node providers and economic parameters. A neuron that begins dissolving follows its configured delay before the stake can be disbursed. Users should review custody, dissolve state, following rules and proposal participation before treating staked ICP as liquid.

Replicated application containers

A canister is a WebAssembly smart contract with persistent state, callable methods and one or more controllers. It runs on a subnet whose nodes replicate execution and reach consensus. Different subnets can have different node counts and purposes, and inter-canister messages can cross subnet boundaries through the network protocol.

Controllers can upgrade code, change settings or delete a canister unless control has been removed or assigned to governance. A polished web interface does not reveal its controller policy. Users and developers should verify the canister identifier and understand whether a frontend, asset ledger and backend logic are governed by the same authority.

Reverse gas for applications

ICP can be sent to the Cycles Minting Canister and burned to mint cycles at a rate tied to XDR. Cycles pay for instructions, storage, messages and supported external integrations. They are designed for predictable resource accounting and cannot be converted back into ICP through the protocol.

Canisters pay most execution costs, so an end user can call an application without holding a gas token. This reverse-gas model shifts responsibility to the developer or service operator. A canister approaching its freezing threshold can stop serving updates and may eventually be deleted if it is not funded.

Verify the correct ledger and application

Confirm whether a destination expects an ICP account identifier, an ICRC account or a principal. Exchange formats can differ from application principals. For canister interactions, verify the canister ID and frontend origin, and never expose an identity seed to a page claiming that cycles must be purchased manually for ordinary use.

Developers should monitor cycles, freezing thresholds, controller keys, subnet dependencies and upgrade procedures. Estimate storage and external-call costs before production. Token holders should distinguish an ICP transfer from neuron staking and from conversion to cycles, because those actions have different reversibility and liquidity.

• Match the required account or principal format.
• Monitor canister cycles and freezing thresholds.
• Review controller and upgrade authority.
• Understand neuron dissolve delays before staking.

The ICP result needs context

Developers convert ICP into cycles through the Cycles Minting Canister, fund canisters, and let applications pay their own resource costs. The Network Nervous System coordinates protocol governance, subnet membership, economics and upgrades through ICP-backed neurons.

A Internet Computer transaction can execute successfully while the application state, contract permission or later exit remains wrong for the user's goal. ICP is the market-profiled asset. Canisters consume cycles for compute, storage and messages; end users do not normally attach ICP gas.

What Internet Computer users should verify and why this design differs

Cycle costs and governance parameters can change. The page does not audit canister code or controllers.

For Internet Computer, the practical sequence is Choose network, Fund fee asset, Review action, Execute, Check finality. Confirm the official destination and current network, then inspect the final balance, position, receipt or documented exit state that actually completes the task: Understand how ICP, canisters, cycles and NNS governance interact before transferring tokens or operating an application.