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

## 1. Overview

Active addresses daily measures the number of unique addresses that were active on the Flow blockchain ecosystem in a given day. For Flow, an "active address" is defined as any address that participated in a transaction in one of three roles: as a transaction payer, proposal key holder, or transaction authorizer. This metric combines activity from both Flow's native Cadence environment and its EVM-compatible environment (Flow EVM), providing a comprehensive view of daily user engagement across the entire Flow ecosystem.

## 2. Data sources

The calculation uses three primary blockchain data sources:
- **Flow Cadence transaction records**: Contains transaction payers and proposal key addresses from Flow's native Cadence environment
- **Flow EVM transaction records**: Contains transaction sender addresses from Flow's EVM-compatible environment  
- **Flow collections data**: Contains transaction authorizer information extracted from nested transaction structures

## 3. Step-by-step calculation

### Component A: Flow EVM user extraction
- **Purpose**: Identifies active addresses from Flow EVM transactions
- **Logic**: Extracts distinct sender addresses (`from_address`) from Flow EVM transaction records. Each sender address represents a user who initiated a transaction on the EVM-compatible Flow environment. Records are truncated to daily boundaries and tagged with chain identifier 'Flow EVM', market sector 'blockchains_l1', business segment 'blockchain', and product 'Flow EVM'.
- **Key fields**: `block_timestamp` truncated to day, `from_address` as user address, transaction hash for record linkage

### Component B: Flow user extraction  
- **Purpose**: Identifies active addresses from Flow's native Cadence environment across three user roles
- **Logic**: Extracts users in three distinct categories: 1) Payers - addresses that pay transaction fees (`payer` field from transactions), 2) Proposers - addresses that hold proposal keys (`proposal_key_address` from transactions), 3) Authorizers - addresses that authorize transactions (extracted by unnesting the `authorizers` array from the collections data structure). All three types are combined as they represent different ways users can actively participate in Cadence transactions.
- **Key fields**: `block_timestamp` truncated to day, `payer`/`proposal_key_address`/`authorizer` as user addresses, transaction identifiers for linkage

### Component C: User data combination
- **Purpose**: Combines Flow EVM and Flow users into unified daily user dataset
- **Logic**: Unions all user records from both Flow EVM and Flow components, maintaining distinct daily records per user address per chain. This creates a comprehensive view of all active addresses across the Flow ecosystem while preserving the source chain information.
- **Key fields**: Standardized `timestamp` at day level, `user_address` as the active address, `chain` identifier distinguishing Flow EVM vs flow

### Component D: HyperLogLog aggregation
- **Purpose**: Calculates approximate distinct user counts across multiple dimensions while handling potential cross-chain duplicates
- **Logic**: Applies HyperLogLog sketching with precision 15 to enable approximate distinct counting of user addresses. Creates sketches for each day and user combination, then merges these sketches across different dimensional breakdowns: project-level aggregation (project_dbt_tag), chain-level breakdown (Flow EVM vs flow), user type breakdown, and product breakdown. The HyperLogLog approach allows efficient handling of large datasets while maintaining accuracy for distinct counting.
- **Key fields**: HLL sketches created from `user_address`, dimension identifiers for breakdowns

### Final aggregation
- **Combining components**: Selects the chain-level and project-level dimensional breakdowns from the HyperLogLog aggregated data
- **Currency conversion**: Not applicable - this is a count metric
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day
- **Final calculation**: Renames the `user_dau` field to `active_addresses_daily` to reflect that for blockchain metrics, unique users are considered equivalent to active addresses. Applies zero-filling strategy through the finalization macro to ensure complete daily time series with zeros for days with no activity.

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

Unique active addresses over a fixed 24-hour window.

FlowFLOW

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown