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 Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Cronos measures the number of unique addresses that send at least one transaction on the Cronos blockchain each day. This metric provides insight into network activity and user engagement on the Cronos ecosystem. The calculation relies on pre-processed transaction sender data from external scraping services that analyze Cronos blockchain activity to count unique daily active addresses.

## 2. Data sources

- **Cronos blockchain data**: Pre-processed daily active user counts sourced from external blockchain analytics scrapers that monitor Cronos network activity
- **Transaction sender analysis**: Aggregated counts of unique addresses that initiated transactions on Cronos blockchain, processed daily by external scraping services
- **Data quality metadata**: Insertion timestamps and versioning information to ensure data freshness and handle multiple data updates

## 3. Step-by-step calculation

### Component A: Raw transaction sender extraction
- **Purpose**: Extract and process daily active user counts from scraped Cronos data
- **Logic**: The system retrieves nested JSON data containing daily timestamps and corresponding active user amounts from external scraper sources. Each record includes an `inserted_at` timestamp for data quality tracking. The JSON data structure is unnested to extract individual date-amount pairs, where `timestamp` represents the day and `amount` represents the count of unique transaction senders for that day.
- **Key fields**: `timestamp` (daily date), `amount` (count of unique transaction senders), `inserted_at` (data insertion timestamp)

### Component B: Data quality and deduplication
- **Purpose**: Ensure data freshness by selecting the most recent data when multiple entries exist
- **Logic**: When multiple data entries exist for the same date (due to data reprocessing or updates), the system applies row numbering based on the `inserted_at` timestamp in descending order. Only the record with row number 1 (most recently inserted) is selected for each date. The `amount` field is renamed to `transaction_senders` for clarity.
- **Key fields**: `row_number` (ranking based on insertion time), `transaction_senders` (renamed from amount)

### Component C: Dimensional breakdown creation
- **Purpose**: Create multiple analytical perspectives of the DAU data
- **Logic**: The system creates three separate dimensional breakdowns from the same transaction sender data. The project-level breakdown sets `dimensions` to 'project_dbt_tag' with null values for chain, product, and user type identifiers. The chain-level breakdown sets `dimensions` to 'chain' and populates `chain_id` with 'cronos' while nulling other dimension fields. The user-type breakdown sets `dimensions` to 'user_type' and populates `user_type` with 'Transaction sender' while nulling other fields.
- **Key fields**: `dimensions` (breakdown type), `chain_id` (cronos), `user_type` (Transaction sender), `product_id` (null)

### Final aggregation
- **Combining components**: All three dimensional breakdowns are combined using union operations to create a comprehensive dataset with different analytical perspectives of the same underlying DAU data
- **Schema standardization**: The `finalize_metric_user_dau` macro is applied to ensure consistent schema structure and fill missing dates with zero values using a 'fill_zeros' strategy, maintaining continuity in time series data
- **Data quality filtering**: Chain availability filters are applied to ensure only valid and available chain data is included in the final metric
- **Final calculation**: The final DAU value represents the count of unique addresses that sent transactions on Cronos blockchain for each day, available across multiple dimensional breakdowns for flexible analysis

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

Unique revenue-generating users over a fixed 24-hour window.

CronosCRO

Maintenance

Active users (daily)

Active users (daily)

Competitive landscape