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 Contracts deployed Methodology

## 1. Overview

The Flow contracts deployed metric measures the daily number of smart contracts deployed across both execution environments on the Flow blockchain: Flow EVM (Ethereum-compatible contracts) and Flow (Flow's native smart contract language). This metric provides insight into developer activity and platform adoption by tracking contract creation events from both the native Flow execution environment and the Ethereum Virtual Machine compatibility layer.

## 2. Data sources

- **Flow system events**: Parsed `AccountContractAdded` events from Flow system contracts that track native Cadence contract deployments
- **Flow EVM contract records**: Processed contract creation data from Flow's Ethereum Virtual Machine environment containing deployment traces and metadata
- **Flow blockchain data**: Block timestamps and transaction identifiers from the Flow blockchain for temporal context

## 3. Step-by-step calculation

### Component A: Flow contract tracking
- **Purpose**: Counts daily deployments of native Cadence smart contracts on Flow
- **Logic**: Extracts contract deployment events from Flow's system contract that emits `AccountContractAdded` events when new Cadence contracts are deployed to accounts. Captures the deployer `address`, `contract` name, `codeHash`, and deployment `block_timestamp`. Each event represents a unique contract deployment. Data is aggregated daily by truncating timestamps to day boundaries and counting distinct deployments.
- **Key fields**: `block_timestamp` for daily aggregation, `address` for deployer identification, `contract` for contract name, `codeHash` for contract identification

### Component B: Flow EVM contract tracking  
- **Purpose**: Counts daily deployments of Ethereum-compatible smart contracts on Flow's EVM
- **Logic**: Uses pre-processed contract creation records from Flow's EVM environment. Captures `creation_timestamp`, `contract_address`, `deployer_address`, and `contract_bytecode` for each deployed contract. The data includes creation trace addresses and creator information. Daily aggregation counts distinct contract addresses deployed each day.
- **Key fields**: `creation_timestamp` for daily aggregation, `contract_address` for unique contract identification, `deployer_address` and `creator_address` for deployment attribution

### Final aggregation
- **Combining components**: Both Flow and Flow EVM daily counts are unioned together, with Flow contracts tagged as `chain_id='flow'` and `product_id='Flow'`, while Flow EVM contracts are tagged as `chain_id='Flow EVM'` and `product_id='Flow EVM'`
- **Currency conversion**: Not applicable - this metric counts contract deployments rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent daily reporting across both execution environments
- **Final calculation**: The final metric represents the sum of distinct contract deployments per day across both Flow and Flow EVM environments, with standardized formatting applied through the finalize metric macro and zero-filling for days without deployments

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

Unique smart contracts published onchain.

FlowFLOW

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown