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 ckETH total supply Methodology

## 1. Overview

The ckETH total supply metric tracks the aggregate amount of ckETH (Chain-Key Ethereum) tokens in circulation on the Internet Computer Protocol. ckETH is a wrapped version of Ethereum that allows ETH to be used within the Internet Computer ecosystem. This metric measures the total outstanding supply of ckETH tokens at the end of each day, providing insight into the adoption and usage of cross-chain ETH on Internet Computer. The calculation uses external API data from Internet Computer Protocol statistics rather than parsing individual blockchain transactions.

## 2. Data sources

The metric relies on the following data sources:

- **Internet Computer Protocol API data**: Daily statistics collected via external scrapers from Internet Computer Protocol endpoints
- **ckETH canister state data**: Total supply information from the ckETH canister smart contracts on Internet Computer
- **External scraper feeds**: JSON-formatted daily statistics feeds containing ckETH supply metrics and timestamps

The data is collected and stored as JSON objects containing nested daily statistics arrays, with each entry representing a day's worth of ckETH supply data.

## 3. Step-by-step calculation

### Component A: Raw data extraction and parsing
- **Purpose**: Extract daily ckETH total supply amounts from JSON-formatted scraper data
- **Logic**: The system parses JSON data structures to extract daily statistics arrays. Each array element contains a `day` timestamp and `cketh_total_supply` value. The process uses JSON parsing functions to extract the timestamp (converted to proper timestamp format) and the raw supply amount (as a high-precision numeric value). The chain is identified as 'internetcomputer' and the timestamp grain is set to 'day' for all records.
- **Key fields**: `day` timestamp from JSON, `cketh_total_supply` amount, `inserted_at` timestamp for versioning

### Component B: Data deduplication and versioning
- **Purpose**: Handle multiple data insertions and select the most recent data for each day
- **Logic**: Since the scraper may insert multiple records for the same day (due to updates or re-runs), the system applies row numbering based on the `inserted_at` timestamp. For each unique day, records are ranked by their insertion time in descending order, and only the most recently inserted record (row number 1) is selected. This ensures that if corrected or updated data is received, the latest version takes precedence.
- **Key fields**: `timestamp` for grouping, `inserted_at` for ranking, row numbering for selection

### Component C: Gap filling and data continuity
- **Purpose**: Handle missing data points by applying forward fill logic
- **Logic**: The system addresses potential gaps in the daily data by implementing a forward fill strategy. Using window functions, each record includes both the current day's `amount` and the previous day's amount (using LAG function). When the current amount is null or missing, the system uses the previous day's value via COALESCE function. Only records where a previous amount exists are included, ensuring the forward fill has a baseline to work from.
- **Key fields**: Current `amount`, `previous_amount` from LAG function, final `amount` after COALESCE

### Final aggregation
- **Combining components**: The processed daily amounts flow through the intermediate model to the final metric model where they are combined with standard metadata fields
- **Currency conversion**: No currency conversion is applied as ckETH supply is measured in token units, not USD values
- **Time aggregation**: Data is already aggregated to daily granularity from the source, with each record representing end-of-day total supply
- **Final calculation**: The raw amount (stored with 18 decimal precision) is converted to human-readable format by dividing by 10^18. The final metric applies the `finalize_metric_cketh_total_supply` macro which adds standard schema fields (`chain_id`, `business_line`, `market_sector_id`, etc.), validates data integrity, applies forward fill for any remaining gaps, and ensures consistent formatting across the time series

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

Internet ComputerICP

ckETH total supply

ckETH total supply

Competitive landscape