# Flow Transaction participants (monthly) Methodology

## 1. Overview

Transaction participants (monthly) measures the number of unique addresses that participate in transactions on the Flow blockchain within a rolling 30-day window. Unique addresses are identified across both Flow and Flow EVM environments. On Flow, this includes transaction signers such as payers, proposers, and authorizers, as well as recipients of non-native fungible assets and NFTs who must actively set up vaults or collections. On Flow EVM, active users are identified as the originating addresses of transactions.

## 2. Data sources

- **Blockchain events**: `Deposited` events from `FungibleToken` and `NonFungibleToken` contracts, transaction signer metadata (payers and proposers), and authorizer lists from transaction collections, covering Flow and Flow EVM
- **External data**: Asset metadata for identifying specific contract addresses

## 3. Step-by-step calculation

### Component A: Flow transaction signer extraction

- **Purpose**: Identify addresses responsible for initiating and authorizing transactions on Flow.
- **Logic**: Transaction payers (who pay transaction fees) and proposers (proposal key addresses) are extracted from transaction metadata. Authorizers are identified by unnesting the repeated authorizer field within the transaction collections. These three signer types are captured to ensure all parties providing cryptographic authorization for a transaction are included.
- **Key fields**: `payer`, `proposal_key_address`, and `authorizer`

### Component B: Flow asset recipient tracking

- **Purpose**: Capture addresses that actively receive non-native assets on Flow.
- **Logic**: `Deposited` events are parsed from `FungibleToken` and `NonFungibleToken` contracts. For fungible assets, transfers involving the native Flow token (contract address `1654653399040a61`) are excluded as they do not require the explicit vault setup that characterizes active participation. For non-fungible assets, deposits to the core NFT contract (address `1d7e57aa55817448`) are monitored to identify recipients who have initialized the required collections.
- **Key fields**: `user_address` (extracted from the `to` field of event payloads), `contract_name`, and `event_name`

### Component C: Flow EVM user identification

- **Purpose**: Capture active users interacting with the Flow EVM environment.
- **Logic**: The originating address for every transaction executed on Flow EVM is extracted. This follows standard EVM account tracking where the sender of the transaction is defined as the active user.
- **Key fields**: `from_address`

### Component D: Monthly rolling aggregation

- **Purpose**: Calculate the unique count of participants over a 30-day window.
- **Logic**: All identified addresses from Flow and Flow EVM are aggregated into daily sets. These daily sets are then combined across a rolling 30-day window. During this aggregation, duplicate addresses are removed to ensure each unique entity is counted only once within the period, regardless of the number of transactions or the specific role (signer vs. Recipient) they performed.
- **Key fields**: `user_address`, `block_timestamp`, and `product_id`

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

Unique addresses participating in transactions over a rolling 30-day window.

Transaction participants (monthly)

Blockchains (L1)

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.

Flow

Transaction participants (monthly)

Transaction participants (monthly)

Chain breakdown