Internet Computer Protocol : Program info

For a bug to be considered for a bounty, it must be in the scope outlined in this section. If you found a bug that is not explicitly in scope, we encourage you to still submit it. It may still qualify for a bounty depending on DFINITY’s discretion and the attack’s impact.

Core Internet Computer Protocol Stack

The Internet Computer Protocol is a distributed protocol run by multiple nodes that constitute the Internet Computer blockchain network. It is structured into layers which are peer-to-peer, consensus, message routing, and execution. See our protocol documentation and specs. In order to get a good overview of the Internet Computer and to get started see our documentation.

• The Internet Computer Protocol (ICP) GitHub Repository
• Some important components are the following, but protocol implementation spans across additional crates:
  • execution, system_api, canister_sandbox and embedders: execution layer for wasm smart contracts
  • consensus and orchestrator: consensus protocol implementation
  • message routing and xnet: messaging layer implementation
  • state_manager: state management
  • p2p and http_endpoints: networking layer implementation
  • http_outcalls: HTTP calls from canisters to Web 2.0
  • crypto: implementation of core crypto, including threshold signatures

Governance: Network Nervous System and Service Nervous System

Network Nervous System (NNS)

All aspects of ICP behavior are governed by the community of enthusiasts and users through a democratic governance system called the Network Nervous System (NNS). A high-level introduction can be obtained from this quick video.

• Network Nervous System (NNS) on GitHub
  • Core canisters include NNS Root, NNS Governance, NNS CMC, NNS GTC (Genesis Token Canister), NNS lifeline canister
• Registry on GitHub

Service Nervous System (SNS)

ICP offers a framework to launch decentralized autonomous organizations (DAOs), called the Service Nervous System (SNS):

• Service Nervous System (SNS) on Github
  • Core canisters include SNS Root, SNS-W, SNS Governance, SNS Swap

Frontend applications

The NNS front-end dapp provides a user-friendly way to interact with the Internet Computer’s governance system. It offers features such as logging in using Internet Identity, sending and receiving tokens, staking neurons, and viewing and voting on NNS and SNS proposals. See also the NNS dapp tutorial.

• Network Nervous System dapp on GitHub
• Domain: https://dashboard.hackenproof.com/redirect?url=https://dashboard.hackenproof.com/redirect?url=https://nns.ic0.app/

Financial Integrations

ICP provides ledger implementations for the ICP token according to the ICRC standards:

• Ledgers on GitHub, including archive and index canisters

Rosetta API provides applications that third parties (e.g. exchanges) can run to obtain ICP price data:

• Rosetta API on GitHub

Chain Fusion and Cross-Chain Applications

Chain-Key (ck) Tokens

These are ICRC compliant tokens that bring other assets, such as BTC or ETH to the ICP ecosystem. See also the Chain Fusion page.

• Bitcoin
  • Bitcoin integration, including the adapter, docs
  • ckBTC on GitHub and the related BTC checker, docs
• Ethereum:
  • ckETH and ckERC20 on GitHub, ckETH docs, ckERC20 docs
  • EVM RPC canister including the client

Internet Identity: Self-Sovereign Single Sign-on Solution

Internet Identity is an anonymous blockchain authentication framework on ICP and supports passkey authentication. Check out the quickstart guide to Internet Identity and the following video.

• Internet Identity on GitHub, specification
• Domain: https://dashboard.hackenproof.com/redirect?url=https://identity.ic0.app/

Developer Experience and Tooling: SDK, CDK, Motoko

The documentation for tools and development kits to assist with development in ICP can be found here. Motoko is a custom built, native language for ICP that simplifies the development of smart contract canisters.

Source code & domain:

• Motoko and Motoko base library on GitHub
• IC Software Development Kit on GitHub
• Rust Canister Development Kit
• Agents for clients to interact with ICP:
  • JavaScript Agent on GitHub
  • Rust Agent on GitHub
• Candid IDL on GitHub
• Cycles Ledger on GitHub
• Quill governance toolkit on GitHub

Internet Computer Infrastructure

Node Operating Systems

The node software runs on the virtual machine termed ‘GuestOS’ that in turn runs on ‘HostOS’. In addition to these OSes, the boundary node systems have their own operating system ‘Boundary-guestOS’. Finally, the ‘SetupOS’ is used to install and set up a node.

• Operating Systems on GitHub

Edge Infrastructure: HTTP Gateway and API Boundary Nodes

The HTTP gateways and the API boundary nodes are major ICP infrastructure components. They sit on the perimeter and act as a gateway to the Internet Computer platform. Here is the list of components:

• HTTP gateway on GitHub
• Boundary nodes on GitHub
• Boundary node OS on GitHub
• Domains: boundary.ic0.app, boundary.dfinity.network
  • boundary.dfinity.network: main load balancer
  • ic0.app, icp0.app: used for ICP api calls and as HTTP gateway:
    • With HTTP asset certification <canister-id>.ic0.app
    • Without HTTP asset certification <canister-id>.raw.ic0.app
  • icp-api.io used for ICP api calls (no HTTP gateway)

Other infrastructure

In addition to the boundary nodes there are additional infrastructure assets that support the operations of the Internet Computer. Here is the list of the domains:

• dfinity.network
• dfinity.systems

• Do not use off the shelf dynamic scanners such as DAST tools on production systems.
• Make every effort not to damage or restrict the availability of products, services, and infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities or social engineering attacks
• Don’t break any law

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without explicit consent from the organization.
• Act responsibly and in good faith during the disclosure process.

We are happy to thank everyone who submits valid reports which help us improve security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• Abide by the program rules and disclosure guidelines
• Ensure that the potential security bug you are reporting is in scope as specified in the Scope & Targets section below.
• Any vulnerability found must be reported as soon as possible after discovery and ideally through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, including attachments such as screenshots or proof of concept code as necessary.
• You must not be a current employee of DFINITY or one of its contractors.
• Only use the email address under which you registered your HackenProof account.
• Do not engage in social engineering techniques or spear-phishing campaigns. Do not cause any harm to the data or the system.
• Duplicate reports and closely related submissions will be dealt with on a case-by-case basis. If the submissions are determined to be genuine they may be rewarded based on a lower rewards scale.
• In case that your finding is valid you might be asked for extra KYC verification to proceed with payments