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 Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the daily revenue generated per active user on the Cronos blockchain. This metric is calculated by dividing total daily revenue by the number of daily active users (DAU). For Cronos, ARPU is consistently zero because protocol revenue is explicitly set to zero in the calculation, reflecting that Cronos may not generate direct protocol revenue or follows a different revenue model structure.

## 2. Data sources

The calculation relies on two primary data sources from the Cronos blockchain:

- **Active user data**: Daily counts of transaction senders scraped from Cronos blockchain activity, representing unique addresses that initiated transactions each day
- **Fee data**: Daily fee amounts collected in CRO tokens, scraped from Cronos blockchain transaction data
- **Scraped blockchain data**: Both datasets come from automated scraping processes that collect and structure daily blockchain metrics with timestamps and insertion tracking

## 3. Step-by-step calculation

### Component A: Daily active users calculation
- **Purpose**: Count unique transaction senders per day to determine daily active users
- **Logic**: Raw active user data is sourced from scraped blockchain activity containing nested daily records with timestamps and user counts. The system processes this data by unnesting the nested JSON structures to extract individual daily records. Deduplication logic is applied using the most recent insertion timestamp for each date to ensure data quality and handle potential duplicate scraping. Transaction senders are classified as the user type and counted as the daily active user metric.
- **Key fields**: `timestamp` for the daily date, `amount` representing the count of unique transaction senders, `inserted_at` for deduplication, `user_type` set to "Transaction sender"

### Component B: Revenue calculation  
- **Purpose**: Calculate daily protocol revenue (set to zero for Cronos)
- **Logic**: Fee data is sourced from scraped Cronos blockchain records containing daily fee amounts in CRO tokens. The raw fee data goes through processing to extract daily amounts and apply deduplication based on insertion timestamps. However, the final revenue calculation explicitly sets all revenue values to zero, regardless of the actual fee amounts collected. This suggests Cronos follows a model where transaction fees do not constitute protocol revenue or uses a different revenue recognition approach.
- **Key fields**: `timestamp` for the daily date, `amount` representing fee amounts in CRO tokens, `fees` processed from amounts, `revenue` explicitly set to 0

### Component C: Dimensional breakdowns
- **Purpose**: Create multiple analytical dimensions for the DAU metric
- **Logic**: The daily active user data is restructured into three dimensional views: project-level aggregation (project_dbt_tag), chain-level breakdown (chain_id set to "cronos"), and user-type breakdown (user_type set to "Transaction sender"). Each breakdown maintains the same user count but enables analysis across different dimensions.
- **Key fields**: `dimensions` indicating the breakdown type, `chain_id`, `product_id`, `user_type`, `user_dau` containing the count values

### Final aggregation
- **Combining components**: The ARPU calculation uses the `calculate_arpu` macro to divide revenue by daily active users, with both metrics sourced from their respective processing pipelines
- **Currency conversion**: No currency conversion is needed as revenue is set to zero; fee amounts are processed in native CRO tokens
- **Time aggregation**: Daily time boundaries are used with gap-filling applied to ensure continuous daily records, missing dates are filled with zero values
- **Final calculation**: ARPU equals daily revenue divided by daily active users, which results in zero for all dates since revenue is zero (0 ÷ DAU = 0). The final metric includes dimensional breakdowns and applies chain availability filters to ensure data quality and completeness.

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

CronosCRO

Maintenance

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape