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 Token holders Methodology

## 1. Overview

The Flow native tokenholders metric measures the total number of unique addresses holding native FLOW tokens across both Flow execution environments: Flow Cadence (the original Flow blockchain) and Flow EVM (Ethereum Virtual Machine compatibility layer). This metric provides a comprehensive view of FLOW token distribution by combining holders from both execution environments into a single daily aggregate count. The calculation aggregates daily snapshots of tokenholder counts from both networks to show the total ecosystem adoption.

## 2. Data sources

- **Flow Cadence balance data**: Daily snapshots of native FLOW token balances for all accounts on the Flow Cadence blockchain
- **Flow EVM balance data**: Daily snapshots of native FLOW token balances for all accounts on the Flow EVM execution environment  
- **Account state data**: Current and historical account balance states across both Flow execution environments
- **Flow transaction data**: Transaction records from both Flow Cadence and Flow EVM that affect native token balances
- **Native token metadata**: Information about the native FLOW token properties and decimal precision across both environments

## 3. Step-by-step calculation

### Component A: Flow cadence tokenholder extraction
- **Purpose**: Counts unique addresses holding native FLOW tokens on the Flow Cadence blockchain
- **Logic**: Extracts daily tokenholder counts from Flow Cadence balance snapshots. The data includes timestamp information, granularity level, chain identifier, and the count of unique addresses with non-zero native FLOW balances. Tokenholder counts are cast to high-precision numeric format to ensure accurate aggregation.
- **Key fields**: `timestamp` for the snapshot date, `timestamp_grain` for aggregation level, `chain` identifier for Flow Cadence, and `tokenholders` count of unique holding addresses

### Component B: Flow EVM tokenholder extraction  
- **Purpose**: Counts unique addresses holding native FLOW tokens on the Flow EVM execution environment
- **Logic**: Extracts daily tokenholder counts from Flow EVM balance snapshots using the same structure as Flow Cadence data. This captures addresses holding native FLOW tokens within the EVM-compatible execution environment. The data follows identical formatting with timestamp, granularity, chain identifier, and precise tokenholder counts.
- **Key fields**: `timestamp` for the snapshot date, `timestamp_grain` for aggregation level, `chain` identifier for Flow EVM, and `tokenholders` count of unique holding addresses

### Component C: Data combination
- **Purpose**: Merges tokenholder data from both Flow execution environments into a unified dataset
- **Logic**: Uses union operation to combine Flow Cadence and Flow EVM tokenholder data into a single dataset. This preserves all records from both sources while maintaining the same data structure across timestamp, granularity, chain identifier, and tokenholder count fields.
- **Key fields**: Combined `timestamp`, `timestamp_grain`, `chain_id`, and `tokenholders` from both execution environments

### Final aggregation
- **Combining components**: The combined dataset is aggregated by timestamp, timestamp grain, and chain identifier, summing tokenholder counts across both execution environments for each time period
- **Currency conversion**: Not applicable - this metric counts addresses rather than token values
- **Time aggregation**: Daily boundary logic groups data by timestamp and timestamp grain to ensure consistent daily snapshots
- **Final calculation**: The final metric represents the sum of unique tokenholders from both Flow Cadence and Flow EVM execution environments for each day, providing a comprehensive count of native FLOW token distribution across the entire Flow ecosystem. The result undergoes standardization through metric finalization processes and quality filtering to ensure data completeness and accuracy.

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

Unique addresses holding a non-zero balance of the project's native token.

FlowFLOW

Token holders

Token holders

Competitive landscape

Chain breakdown