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

Polygon is a smart contract platform for decentralized applications & interoperability platform for blockchains. Polygon was founded by Jaynti Kanani, Sandeep Nailwal & Anurag Arjun and launched in 2017.

MATIC holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Polygon’s investors include Coinbase Ventures, ZBS Capital, MiH Ventures, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Polygon

# Polygon Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Polygon measures the number of unique addresses that initiated at least one transaction on the Polygon network within a given day. This metric provides insights into user engagement and network activity by counting distinct transaction senders, serving as a key indicator of blockchain adoption and usage patterns.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Polygon blockchain transactions**: Complete transaction records from the Polygon network including transaction hashes, sender addresses, recipient addresses, timestamps, and gas information
- **Block timestamp data**: Precise timing information for when transactions were included in blocks
- **Transaction metadata**: Additional transaction details like gas usage, effective gas prices, and block numbers

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extracts and processes all Polygon network transactions with relevant metadata
- **Logic**: Sources raw transaction data from Polygon blockchain records, extracting key fields including block timestamps, transaction hashes, sender addresses (`from_address`), recipient addresses, gas usage, and effective gas prices. The component applies standard business categorization by setting `market_sector_id` to "blockchains_l1" and `business_segment_id` to "blockchain". It also includes the wrapped POL token address as a reference token
- **Key fields**: `block_timestamp` for timing, `from_address` for user identification, `transaction_hash` for uniqueness, `gas_used` and `effective_gas_price` for transaction costs

### Component B: Daily user aggregation  
- **Purpose**: Identifies unique users per day by counting distinct transaction senders
- **Logic**: Truncates block timestamps to day-level granularity using daily time boundaries. Selects distinct combinations of the truncated timestamp and sender address (`from_address`) to ensure each user is counted only once per day, regardless of how many transactions they sent. Applies metadata enrichment including chain identification as "polygon", user type classification as "Transaction sender", and timestamp grain specification as "day"
- **Key fields**: `timestamp` (truncated to day), `user_dau` (the sender address), `chain`, `user_type`, and business categorization fields

### Final aggregation
- **Combining components**: The processed transaction data flows directly into the daily aggregation without additional joining, as both components work with the same transaction dataset
- **Currency conversion**: No currency conversion is required for this metric as it counts addresses rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent 24-hour periods for user counting
- **Final calculation**: The metric value represents the count of distinct `from_address` values for each day, where each unique address that sent at least one transaction is counted as one daily active user

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

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

PolygonPOL

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown