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 Fees Methodology

## 1. Overview

The Cronos fees metric measures the total transaction fees collected by the Cronos blockchain on a daily basis, expressed in USD. This represents the daily revenue earned by Cronos network validators from processing transactions. The calculation aggregates all transaction fees paid in CRO token and converts them to USD using end-of-day exchange rates.

## 2. Data sources

- **Scraped blockchain data**: Daily fee amounts collected from the Cronos blockchain via automated scraping processes that extract fee totals from blockchain state
- **External price feeds**: End-of-day price feeds for CRO token to enable USD conversion
- **Chain availability data**: Configuration data that determines when Cronos chain metrics are considered reliable and should be included in calculations

## 3. Step-by-step calculation

### Component A: Raw fee data extraction
- **Purpose**: Extract and process daily fee amounts from scraped Cronos blockchain data
- **Logic**: The calculation begins with raw fee data stored in JSON format containing arrays of daily fee measurements. Each record includes a timestamp and corresponding fee amount in CRO token. The JSON data arrays are unnested to create individual records for each date-amount pair. Metadata is added including chain identifier, token symbol, and timestamp granularity set to daily intervals.
- **Key fields**: `timestamp` (date), `amount` (fee total in CRO), `inserted_at` (data ingestion timestamp)

### Component B: Data deduplication and quality control  
- **Purpose**: Handle multiple data ingestions for the same date and select the most recent reliable data
- **Logic**: Since the scraper may collect data multiple times for the same date, duplicate records are handled by ranking all records for each timestamp based on their insertion time. The most recently inserted data is selected using a row number window function partitioned by timestamp and ordered by insertion timestamp in descending order. Only records with row number 1 (most recent) are retained.
- **Key fields**: `row_number` (ranking for deduplication), `inserted_at` (used for ordering)

### Final aggregation
- **Combining components**: The deduplicated daily fee amounts serve as the base dataset for final processing through standardization macros
- **Currency conversion**: CRO token amounts are converted to USD using end-of-day price feeds, with decimal corrections applied to ensure proper token unit representation
- **Time aggregation**: Data is maintained at daily granularity with timestamps representing specific calendar dates
- **Final calculation**: The final metric value represents total daily fees collected by the Cronos network in USD, with gaps filled using zero values for dates where no fee data is available, filtered to exclude periods when the Cronos chain is not considered operationally reliable for metrics calculation

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

Total value users pay to use a protocol (gross fees, user-paid fees).

CronosCRO

Maintenance

Fees

Fees

Competitive landscape