Validators process transactions and receive fees from users (supply-side fees).

Cronos is a smart contract platform for decentralized applications (a blockchain). Cronos was founded by Crypto.com and launched in 2021.

CRO holders own and govern the protocol. They currently do not take a cut of the total transaction fees paid by users (revenue).

github

twitter

discord

website

Blockchains (L1)

Cronos

# Cronos Revenue Methodology

## 1. Overview

The Cronos revenue metric measures protocol revenue generated by the Cronos blockchain network. Currently, this metric is explicitly set to zero for all time periods, indicating that Cronos does not generate protocol revenue despite collecting transaction fees. This design separates fee collection (which measures network activity costs paid by users) from revenue (which measures income retained by the protocol). The metric maintains the same dimensional structure as fees data to enable consistent reporting and potential future revenue calculations.

## 2. Data sources

The calculation uses the following data sources:
- **External scraper data**: Daily fee collection data scraped from Cronos blockchain operations, containing timestamps and fee amounts
- **Fee amounts**: Transaction fees paid by users, denominated in `CRO` tokens
- **Blockchain metadata**: Chain identifiers, market sector classifications, and business segment categorizations
- **Temporal data**: Daily timestamps for time-series aggregation and gap identification

## 3. Step-by-step calculation

### Component A: Raw fee data extraction
- **Purpose**: Extracts and processes scraped fee data from the Cronos blockchain
- **Logic**: The system retrieves fee data from external scraper sources that collect daily fee amounts from Cronos blockchain operations. The scraped data contains nested structures with timestamps and corresponding fee amounts denominated in `CRO` tokens. Data is unnested to create individual records for each day's fee collection, with amounts cast to high-precision numeric format to handle large values accurately.
- **Key fields**: `timestamp` for daily boundaries, `amount` for fee values in `CRO` tokens, `inserted_at` for data freshness tracking

### Component B: Data deduplication and standardization
- **Purpose**: Ensures data quality by removing duplicates and standardizing metadata
- **Logic**: Since scraper data may contain multiple entries for the same day with different insertion timestamps, the system applies deduplication logic using window functions. Records are partitioned by timestamp and ordered by insertion time in descending order, with only the most recently inserted data retained for each day. Chain metadata is standardized with `cronos` as the chain identifier, `CRO` as both contract name and token symbol, and `day` as the timestamp grain.
- **Key fields**: `row_number` for deduplication ranking, `chain` set to cronos, `token_symbol` set to CRO, `timestamp_grain` set to day

### Component C: Fee metric processing
- **Purpose**: Structures fee data with proper business classifications and schema validation
- **Logic**: The processed fee data is enhanced with business metadata including market sector classification as `blockchains_l1` and business segment as `blockchain`. Product identifier is set to null since fees are measured at the protocol level rather than specific products. The `finalize_metric_fees` macro applies schema validation, ensures consistent field types, and implements a fill-zeros strategy to create records for missing dates with zero fee values.
- **Key fields**: `chain_id` for blockchain identification, `market_sector_id` as blockchains_l1, `business_segment_id` as blockchain, `fees` containing the daily fee amounts

### Final aggregation
- **Combining components**: The revenue calculation uses the fees data structure as a template but explicitly sets all revenue values to zero, indicating that Cronos does not retain any portion of collected fees as protocol revenue
- **Currency conversion**: No currency conversion is applied since revenue is set to zero; fees remain denominated in `CRO` tokens but revenue calculation bypasses this
- **Time aggregation**: Daily time boundaries are maintained from the original fee data, with the same timestamp and timestamp grain structure preserved
- **Final calculation**: Revenue is calculated as zero for all time periods: `revenue = 0`. This explicit zero assignment indicates that while Cronos collects transaction fees from users, none of this fee income is retained as protocol revenue. The metric maintains dimensional consistency with fees data to enable reporting and potential future revenue recognition if the protocol's economic model changes.

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

CronosCRO

Maintenance

Revenue

Revenue

Competitive landscape