twitter

discord

website

Blockchains (L1)

Movement

# Movement Revenue Methodology

## 1. Overview

Movement revenue represents all transaction fees collected by the Movement blockchain. This metric measures the total gas fees paid by users for transaction execution, converted to USD. Movement follows a standard L2 blockchain model where all gas fees collected constitute protocol revenue, providing a direct measure of network usage and value capture.

## 2. Data sources

The calculation relies on these core data sources:
- **Movement blockchain transaction records**: Raw transaction data from the Movement network containing gas usage, gas prices, timestamps, and transaction metadata
- **End-of-day token price feeds**: USD price data for Movement's native token used for currency conversion
- **Token metadata**: Protocol classification data identifying Movement as an L2 blockchain with native token transactions

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extracts and processes raw transaction data from the Movement blockchain
- **Logic**: Pulls all transactions from Movement blockchain records including `block_timestamp`, `hash`, `sender`, `gas_used`, and `gas_unit_price`. Applies decimal correction by dividing `gas_unit_price` by 10^8 to adjust for proper decimal representation. Implements special handling for genesis transactions - any transactions timestamped before 2000-01-01 are reassigned to 2024-12-05 timestamp, while normal transactions are filtered to include only those after 2000-01-01.
- **Key fields**: `block_timestamp` for timing, `gas_used` for transaction computational cost, corrected `gas_unit_price` for fee rate, `transaction_hash` for identification

### Component B: Daily fee aggregation  
- **Purpose**: Calculates total gas fees paid per day across all Movement transactions
- **Logic**: For each transaction, multiplies `gas_used` by the corrected `gas_unit_price` to get individual transaction fee amounts. Groups transactions by day using timestamp truncation and sums all fee amounts within each day. This creates daily totals representing all gas fees collected by the Movement network.
- **Key fields**: Daily `timestamp` boundaries, aggregated `fee_amount` representing total daily gas fees in native tokens

### Component C: USD conversion and classification
- **Purpose**: Converts native token fees to USD and applies protocol metadata
- **Logic**: Takes daily fee totals and converts them from Movement native tokens to USD using end-of-day price feeds. Applies protocol classification metadata identifying Movement as `chain_id='movement'`, `market_sector_id='blockchains_l2'`, `business_segment_id='blockchain'`, and `token_address='native'` to properly categorize the revenue within Token Terminal's taxonomy.
- **Key fields**: USD-denominated `fees` amounts, protocol classification identifiers

### Final aggregation
- **Revenue mapping**: Maps calculated fees directly to revenue with a 1:1 relationship, where all gas fees collected become protocol revenue
- **Currency conversion**: Uses end-of-day price feeds to convert from Movement native tokens to USD amounts
- **Time aggregation**: Maintains daily granularity with complete time series 
- **Final calculation**: Revenue equals the sum of all daily transaction fees (gas_used × gas_unit_price) converted to USD, representing total value captured by the Movement network through transaction fee collection

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

MovementMOVE

Archived

Revenue

Revenue

Competitive landscape