Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Moonbeam is an Ethereum-compatible smart contracts platform built as a Polkadot parachain.

GLMR holders own and govern the protocol. Moonbeam’s investors include IOSG Ventures, Coinbase Ventures, Fenbushi Capital, CoinFund, etc

website

github

twitter

discord

etherscan

Blockchains (L2)

Moonbeam

# Moonbeam Revenue Methodology

> **Archived 2026-07-31.** Token Terminal stopped tracking Moonbeam following the announced migration of GLMR to Base and the launch of the new Moonbeam Protocol. The methodology below describes how this metric was calculated while the chain was tracked; historical values remain accurate and accessible.

## 1. Overview

Revenue measures the total fees collected by the network from user transactions across both the Layer 1 substrate chain and the Moonbeam EVM compatibility layer. Protocol revenue is generated from transaction processing fees, including both base transaction fees and user-provided tips. Daily fee collection is aggregated and converted to USD to provide insight into Moonbeam's fee generation and network usage patterns.

## 2. Data sources

- **Blockchain events**: `TransactionFeePaid` events from `transactionPayment` pallets, `Executed` events from `ethereum` pallets, and `Withdraw` and `Deposit` events from `balances` pallets, covering Moonbeam and Moonbeam EVM
- **External data**: End-of-day price feeds for the native GLMR asset

## 3. Step-by-step calculation

### Component A: Raw event processing

- **Purpose**: Raw blockchain events are extracted and structured from Moonbeam's substrate chain.
- **Logic**: Daily event logs are extracted and partitioned by timestamp. Event metadata including `event_pallet`, `event_method`, `event_data`, and `extrinsic_id` is preserved for downstream processing.
- **Key fields**: `timestamp`, `event_pallet`, `event_method`, `event_data`, `extrinsic_id`

### Component B: Layer 1 substrate fee calculation

- **Purpose**: Fees from native substrate transactions are calculated.
- **Logic**: Events are filtered to `TransactionFeePaid` events from the `transactionPayment` pallet. The `transaction_fee` and `transaction_tip` amounts are extracted from JSON event data and summed per transaction to determine total Layer 1 fees.
- **Key fields**: `transaction_fee`, `transaction_tip` from event data, aggregated as total `transaction_fee`

### Component C: Moonbeam EVM fee calculation

- **Purpose**: Fees from EVM-compatible transactions on Moonbeam EVM are calculated.
- **Logic**: EVM transactions are identified through `Executed` events from the `ethereum` pallet to extract signer addresses. Corresponding `Withdraw` and `Deposit` events from the `balances` pallet are matched where the signer address, extrinsic identifier, and timestamp align. Fee amounts are calculated by netting the positive withdraw and negative deposit amounts per transaction.
- **Key fields**: `signer_address` from `Executed` events, `transaction_fee` amounts from `Withdraw` and `Deposit` events

### Component D: Fee aggregation and standardization

- **Purpose**: Layer 1 substrate fees and Moonbeam EVM fees are combined into total network fees.
- **Logic**: Layer 1 substrate fees and Moonbeam EVM fees are unioned. Amounts are normalized by decimal precision and aggregated daily by chain and timestamp.
- **Key fields**: `timestamp`, `chain_id`, `transaction_fee`

### Component E: USD conversion

- **Purpose**: Native GLMR asset amounts are converted to USD values.
- **Logic**: Daily aggregated fees are joined with end-of-day price feeds for the GLMR asset. Fee amounts are multiplied by corresponding daily USD prices.
- **Key fields**: `fees` in USD

### Component F: Supply-side fee calculation

- **Purpose**: Fees paid to network participants such as validators and stakers are determined.
- **Logic**: For Moonbeam, supply-side fees are set to zero, indicating all transaction fees are retained by the protocol rather than distributed to validators or stakers.
- **Key fields**: `fees_supply_side` (always 0)

### Component G: Final revenue calculation

- **Purpose**: Consolidate fees and determine the final protocol revenue.
- **Logic**: Revenue is calculated as total fees minus fees paid to supply-side participants. Because supply-side fees for Moonbeam are set to zero, the final revenue amount is determined to be equal to the total fees collected. All values are aggregated to daily boundaries using UTC timestamps.

*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.

MoonbeamGLMR

Archived

Revenue

Revenue

Competitive landscape

Chain breakdown