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 Expenses 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

Expenses measures the operational costs incurred by Moonbeam through token incentive distributions. The total value of block rewards paid to validators and delegators on Moonbeam is captured, representing the protocol's primary operational expense. Daily block reward distributions are aggregated, converted from native GLMR assets to USD, and classified as protocol expenses.

## 2. Data sources

- **Blockchain events**: `Rewarded` events from `parachainStaking` pallets, covering Moonbeam
- **External data**: End-of-day price feeds for the GLMR asset

## 3. Step-by-step calculation

### Component A: Raw event processing

- **Purpose**: Extract and structure Moonbeam events for downstream processing
- **Logic**: Raw Moonbeam blockchain events are processed by truncating block timestamps to daily granularity and preserving essential event metadata, including block numbers, event indices, event data, event methods, pallets, and success status.
- **Key fields**: `timestamp` (daily truncated), `event_data`, `event_method`, `event_pallet`, `block_number`

### Component B: Block reward extraction

- **Purpose**: Identify and extract block reward amounts from staking events
- **Logic**: Moonbeam events are filtered for the `parachainStaking` pallet and `Rewarded` method. Reward amounts are extracted by parsing the event data array and casting the second element as a numeric value representing the reward amount in native units.
- **Key fields**: `amount` (extracted from event data), `timestamp`, `block_number`, `event_index`

### Component C: Token incentives aggregation

- **Purpose**: Calculate daily token incentive totals and convert to standard units and USD
- **Logic**: Block rewards are grouped by day and daily totals are summed. Amounts are normalized by decimal precision to handle asset formatting. USD conversion is applied using end-of-day price feeds for the GLMR asset, and protocol metadata, including chain identification and reward type classification, is appended.
- **Key fields**: `token_incentives` (converted amounts), `timestamp` (daily), `chain_id`, `reward_type`

### Component D: Final aggregation

- **Purpose**: Combine components into the final expenses metric
- **Logic**: Token incentive values are mapped directly into the expenses calculation, with the incentive values representing operational costs. USD conversion is performed using end-of-day price feeds for GLMR assets. Daily boundaries are established through timestamp truncation at the raw event processing stage, with all subsequent calculations maintaining daily granularity. The final expenses value is calculated as the sum of all daily block rewards distributed to validators and delegators. Amounts are normalized by decimal precision and converted to USD using end-of-day GLMR price feeds. Missing days are filled with zero values to maintain time series continuity.

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

Total project operating and incentive expenses.

MoonbeamGLMR

Archived

Expenses

Expenses

Competitive landscape

Chain breakdown