§ Wiki · Wiki entry

Node Provider Self-declaration

The identity declaration and good-faith statement a prospective node provider files before the NNS votes on their onboarding proposal.

·May 4, 2026·3 min read

[!WARNING] No new machines or new node providers are currently being onboarded, as the target topology has been reached.

A self-declaration is the document a prospective node provider files to declare their real-world identity, confirm fit with the published hardware requirements, and commit to honest operation of their machines. The Network Nervous System (NNS) uses it — together with proof of identity — when voting on whether to accept the provider.

In a fully decentralized network, provider onboarding is managed entirely through the NNS. There is no contract with DFINITY; the self-declaration is the artefact the community votes against.

What the declaration covers

The current questionnaire that captures these details is the Node Provider Self-Declaration Form. Work from that form when preparing your declaration.

The document records:

  • Identity. Entity name, representative details, and physical location.
  • Hardware compliance. A guarantee that the machines being onboarded match the published specification.
  • Good-faith statement. An acknowledgement of potential liability for damages, and an explicit acknowledgement that deliberate interference with nodes can constitute criminal activity in some jurisdictions.

Alongside the declaration, the candidate supplies proof that the identity (or identities) listed in the declaration exist in the real world, in a form acceptable to the community.

Public information, private disclosure, and audit

The form separates the public information every entity completes (the greyed fields, which are shared with the ICP community) from material filed only for private disclosure.

After a provider submits the form, an auditor reviews it and requests the additional documents needed to verify the statements. Once the information is verified, the completed form (excluding the supporting documents in the private-disclosure sections), together with the auditor's confirmation, is shared with the ICP community.

[!NOTE] The audit process is still evolving (it has so far been run as a pilot), so the exact steps may change.

Process

  1. Prepare the documents. Draft the self-declaration using the Node Provider Self-Declaration Form, and gather the identity proofs. Compute a SHA-256 hash of each file.
  2. Upload to the wiki. The artefacts go on the public node-provider self-declarations page so they are inspectable.
  3. Submit the NNS proposal. The proposal references the uploaded files and embeds their hashes — see Node Provider Onboarding for the ic-admin command and required summary fields.
  4. Community vote. Token-holders evaluate the declaration and identity proofs and vote on acceptance.

[!NOTE] The required contents of the self-declaration are captured in the Node Provider Self-Declaration Form. Use that form as the canonical template when drafting your declaration.

Related