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

Flow is a smart contract platform for decentralized applications (a blockchain). Flow was founded by Roham Gharegozlou, Dieter Shirley and Mikhael Naayem and launched in 2019.

FLOW holders own and govern the protocol. They currently don’t take a cut of the total transaction fees paid by users (revenue). Flow’s investors include a16z, Coatue, Coinfund, Fabric Ventures, etc.

governance

github

twitter

discord

website

Blockchains (L1)

Flow

# Flow Active users (daily) Methodology

## 1. Overview

Flow Daily Active Users (DAU) measures the number of unique addresses that interact with the Flow blockchain on a daily basis. This metric combines users from both Flow blockchain variants: Flow EVM (Ethereum Virtual Machine implementation) and Flow (native Flow implementation). The calculation identifies active users through different transaction roles and interaction patterns across both blockchain variants, providing a comprehensive view of daily user activity on the Flow ecosystem.

## 2. Data sources

- **Flow EVM transaction records**: Transaction data from Flow's Ethereum Virtual Machine implementation containing transaction initiator addresses
- **Flow Cadence transaction records**: Native Flow transaction data including payer addresses, proposal key addresses, gas limits, and fee information  
- **Flow Cadence collection records**: Nested blockchain data structures containing transaction collections with embedded authorizer address arrays

## 3. Step-by-step calculation

### Component A: Flow EVM user identification
- **Purpose**: Identifies daily active users from Flow EVM transactions
- **Logic**: Extracts unique transaction initiator addresses from Flow EVM transaction records. Each `from_address` that initiates at least one transaction on a given day counts as one daily active user. Timestamps are truncated to daily boundaries to ensure proper daily aggregation. Users are classified with chain identifier as `Flow EVM`, market sector as `blockchains_l1`, business segment as `blockchain`, and product as `Flow EVM`.
- **Key fields**: `from_address` as the user identifier, `block_timestamp` for temporal grouping, `transaction_hash` for transaction reference

### Component B: Flow payer identification  
- **Purpose**: Identifies users who pay transaction fees in Flow
- **Logic**: Extracts unique `payer` addresses from Flow Cadence transaction records. Payers are addresses responsible for covering transaction fees. Each unique payer address per day counts as one daily active user. Null payer addresses are excluded from the calculation.
- **Key fields**: `payer` as the user identifier, `block_timestamp` for daily grouping, `fee_amount` for transaction cost reference

### Component C: Flow proposer identification
- **Purpose**: Identifies users who act as transaction proposers in Flow
- **Logic**: Extracts unique `proposal_key_address` values from Flow Cadence transaction records. Proposal key addresses represent users who propose transactions in the Flow consensus mechanism. Each unique proposal key address per day counts as one daily active user. Null proposal key addresses are excluded.
- **Key fields**: `proposal_key_address` as the user identifier, `proposal_key_index` and `proposal_key_sequence_number` for proposal tracking

### Component D: Flow authorizer identification
- **Purpose**: Identifies users who authorize transactions in Flow
- **Logic**: Extracts authorizer addresses from nested Flow collection data structures. Collections contain arrays of transactions, and each transaction contains arrays of authorizer addresses. The data is unnested using cross joins to flatten the nested structure, extracting each individual authorizer address. Each unique authorizer address per day counts as one daily active user. Null authorizer addresses are excluded.
- **Key fields**: `authorizer` addresses from the nested array structure, `blockTimestamp` from collection records, transaction `id` for reference

### Final aggregation
- **Combining components**: All four user identification components (Flow EVM users, Flow payers, Flow proposers, and Flow authorizers) are combined using union operations. Each component maintains its respective chain identifier to distinguish between Flow EVM and Flow users.
- **Time aggregation**: Daily boundaries are established by truncating `block_timestamp` values to day precision using timestamp truncation functions. This ensures all activity within a 24-hour period is grouped together.
- **Deduplication**: Distinct operations are applied at the component level to ensure each unique address is counted only once per day within each user type category. However, the same address could potentially appear across multiple categories (e.g., as both a payer and proposer) and would be counted separately.
- **Final calculation**: The final DAU count represents the total number of user records across all categories per day, where each record represents one unique address-role combination. This provides a comprehensive view of daily user activity across both Flow blockchain variants and all transaction roles.

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

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

FlowFLOW

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown