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 Fees Methodology

## 1. Overview

Flow fees represent the total transaction costs across the Flow blockchain ecosystem, combining fees from both Flow EVM (the EVM-compatible layer) and Flow (the native Flow execution layer). This metric aggregates L2 gas fees from EVM transactions and L1 transaction fees from Cadence transactions, providing a comprehensive view of network usage costs. The metric answers how much users collectively pay to execute transactions on the Flow blockchain infrastructure.

## 2. Data sources

- **Flow EVM transaction records**: EVM-compatible transaction data including gas usage, gas prices, transaction hashes, and block timestamps
- **Flow Cadence transaction records**: Native Flow blockchain transactions with pre-calculated fee amounts, payer addresses, and transaction metadata
- **End-of-day FLOW token price feeds**: Daily closing prices for FLOW tokens sourced from CoinGecko API integration
- **Token metadata**: Standard token addresses and symbols for both EVM (`0xd3bf53dac106a0290b0483ecbc89d40fcc961f3e`) and Cadence (`A.1654653399040a61.FlowToken`) FLOW token representations

## 3. Step-by-step calculation

### Component A: Flow EVM gas fees
- **Purpose**: Calculate daily gas fees from EVM-compatible transactions on Flow
- **Logic**: Extract gas usage and gas price data from Flow EVM transaction records. Calculate individual transaction fees by multiplying `gas_used` by `gas_price` and dividing by 1e18 to adjust for decimal precision. Aggregate these calculated fees daily by grouping transactions by day, token address, and chain. Apply standard USD conversion using the built-in price conversion macro that handles both decimal correction and currency conversion automatically.
- **Key fields**: `gas_used` (gas consumed by transaction), `gas_price` (price per gas unit), `block_timestamp` (transaction timestamp), `token_address` (FLOW token contract address)

### Component B: Flow transaction fees  
- **Purpose**: Aggregate pre-calculated fees from native Flow Cadence transactions
- **Logic**: Extract fee amounts directly from Flow Cadence transaction records, where fees are already calculated upstream. Aggregate daily by summing all `fee_amount` values, grouping by day while also calculating additional metrics like average fees, median fees, transaction counts, and unique payer counts. Convert to USD manually by joining with FLOW token price data from CoinGecko and multiplying native fee amounts by the corresponding daily price.
- **Key fields**: `fee_amount` (pre-calculated transaction fee), `block_timestamp` (transaction timestamp), `payer` (fee-paying address), `token_address` (Cadence FLOW token identifier)

### Final aggregation
- **Combining components**: Union the USD-converted Flow EVM and Flow fee datasets using a simple concatenation approach, since both components already have matching schema structures with daily timestamps and USD-denominated fee amounts
- **Currency conversion**: Flow EVM fees use the standard automated conversion macro, while Flow fees use manual conversion by joining with end-of-day FLOW prices and direct multiplication
- **Time aggregation**: Both components aggregate to daily boundaries using timestamp truncation to day level, with all transactions within a calendar day grouped together
- **Final calculation**: Apply metric finalization process that validates business classification fields (market sector, business segment, product IDs), ensures schema compliance, fills any gaps in the time series with zero values using the fill-zeros strategy, and applies chain availability filtering based on the `chain_id` field

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

Total value users pay to use a protocol (gross fees, user-paid fees).

FlowFLOW

Fees

Fees

Competitive landscape

Chain breakdown