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 Supply-side fees Methodology

## 1. Overview

Cronos fees supply side measures the total transaction fees collected by the Cronos blockchain network that are distributed to network validators and stakers. This metric represents the revenue generated by the protocol that flows to the supply side participants (validators/stakers) rather than being burned or held by the protocol treasury. The calculation directly uses the total network fees as the supply-side fees since all transaction fees on Cronos are distributed to network participants.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Cronos blockchain fees data**: Daily aggregated transaction fees collected via automated scraper from the Cronos network
- **CRO token metadata**: Token symbol and chain identification data for standardization
- **Temporal data**: Daily timestamps for time-series aggregation and boundary definitions

## 3. Step-by-step calculation

### Component A: Raw fees extraction
- **Purpose**: Extract and standardize daily transaction fees from the Cronos blockchain
- **Logic**: The system retrieves raw fees data from automated scraper that monitors Cronos network activity. The scraper collects nested data arrays containing daily fee amounts. These nested structures are unnested to create individual fee records, each with a `timestamp`, `amount`, and `inserted_at` field. The `amount` values are cast to high-precision numeric format to handle large fee amounts accurately. Each record is tagged with chain identifier 'cronos' and token symbol 'CRO' for standardization.
- **Key fields**: `timestamp` for daily boundaries, `amount` for fee values in CRO tokens, `inserted_at` for data versioning

### Component B: Data deduplication and quality control
- **Purpose**: Ensure data quality by selecting the most recent data when multiple scraper runs exist for the same day
- **Logic**: Since the scraper may run multiple times per day, the system applies deduplication logic using window functions. Records are partitioned by `timestamp` and ordered by `inserted_at` in descending order, with row numbers assigned. Only records with row number 1 (most recently inserted) are retained to avoid double-counting fees from multiple scraper executions on the same day.
- **Key fields**: `row_number` for deduplication ranking, `inserted_at` for temporal ordering

### Component C: Fees metric standardization
- **Purpose**: Transform raw fees into standardized metrics format with proper metadata
- **Logic**: The cleaned fees data is structured into the standard metrics format with required metadata fields. Each record receives `chain_id` set to 'cronos', `market_sector_id` set to 'blockchains_l1', `business_segment_id` set to 'blockchain', and `product_id` set to null since this represents network-level fees rather than product-specific fees. The `timestamp_grain` is set to 'day' for daily aggregation. The finalize fees macro validates the schema, ensures no temporal gaps exist by filling missing days with zero values, and applies data quality checks.
- **Key fields**: `fees` containing daily fee amounts, metadata fields for categorization, `timestamp_grain` for aggregation level

### Final aggregation: Supply-side fees assignment
- **Combining components**: The supply-side fees metric directly references the standardized `fees` field from the fees metrics component
- **Currency conversion**: Fees remain in native CRO tokens without USD conversion at this stage
- **Time aggregation**: Daily boundaries are maintained with `timestamp_grain` set to 'day'
- **Final calculation**: Supply-side fees equals total network fees since all transaction fees on Cronos are distributed to validators and stakers rather than being burned or retained by the protocol. The `fees_supply_side` field is set equal to the `fees` field value, representing the portion of total fees that flows to supply-side participants in the network.

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

Portion of fees distributed to service providers or supply-side participants.

CronosCRO

Maintenance

Supply-side fees

Supply-side fees

Competitive landscape