Node operators process transactions and receive token incentives. These independently owned high-spec node machines around the world are connected via Internet Computer Protocol (ICP), creating a self-sovereign network not reliant on any cloud services. Advanced cryptography allows any application or service to be run on the network in a decentralized manner via smart contracts.

The Internet Computer is a decentralized cloud blockchain, where apps can be built fully onchain, using AI, or by coding. Try caffeine.ai & icp.ninja.

ICP tokenholders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). ICP Holders can stake their ICP on the Network Nervous System (NNS), an advanced fully on-chain DAO that facilitates liquid democracy. Staking ICP allows users to submit proposals, vote on proposals, and earn rewards for their participation in governance. Internet Computer's investors include Polychain, Scalar Capital, Amino Capital, etc.

github

twitter

discord

website

Blockchains (L1)

Internet Computer

# Internet Computer Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of new smart contracts (called "canisters" on Internet Computer) deployed on the Internet Computer network. This metric tracks protocol adoption by counting gross new canister deployments, providing insight into development activity and ecosystem growth. The calculation uses scraped network statistics from Internet Computer's official metrics to provide daily deployment counts.

## 2. Data sources

The metric relies on a single external data source:
- **Internet Computer network statistics**: Daily aggregated statistics scraped from Internet Computer's network dashboard or API endpoints, containing daily counts of newly deployed canisters across the entire network
- **Scraper service data**: Raw JSON data collected by an automated scraper that periodically fetches network statistics, with each scrape timestamped for data freshness tracking

## 3. Step-by-step calculation

### Component A: Raw data extraction and parsing
- **Purpose**: Extract daily canister deployment counts from scraped Internet Computer network statistics
- **Logic**: The calculation begins by parsing JSON data from the scraper service that contains arrays of daily network statistics. Each daily statistics entry includes a `gross_new_canisters` field representing the total number of new canisters deployed on that specific day. The data is extracted using JSON parsing functions to convert the nested JSON structure into tabular format, with each row representing one day's deployment count.
- **Key fields**: `day` timestamp from JSON converted to timestamp format, `gross_new_canisters` value extracted as the deployment count, `inserted_at` timestamp indicating when the scraper collected this data

### Component B: Data deduplication and standardization  
- **Purpose**: Handle multiple scraper runs per day and standardize the data format
- **Logic**: Since the scraper may collect data multiple times per day with updated values, the process uses a row numbering approach to identify the most recent data for each day. Records are ranked by their insertion timestamp in descending order, and only the most recently inserted record for each day is retained. The data is then transformed into the standard metric format with chain identifier set to 'internetcomputer' and the amount field renamed to `contracts_deployed`.
- **Key fields**: `timestamp` for the day, `chain` identifier, `amount` representing daily deployment count, deduplication based on `inserted_at` ranking

### Final aggregation
- **Combining components**: The standardized daily deployment counts are aggregated by day, chain, and product (though already at daily granularity from the source)
- **Currency conversion**: No currency conversion required as this metric counts contract deployments rather than monetary values
- **Time aggregation**: Data is maintained at daily boundaries as provided by the source, with each day representing a complete 24-hour period of deployment activity
- **Final calculation**: The final metric value represents the total number of new canisters deployed on the Internet Computer network for each day, with a finalization process that validates the data schema, ensures complete date coverage by filling missing days with zero values, and applies chain availability filters to exclude data from before the Internet Computer network became operational

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique smart contracts published onchain.

Internet ComputerICP

Contracts deployed

Contracts deployed

Competitive landscape