website

twitter

Blockchains (L1)

Plasma

# Plasma Revenue Methodology

## 1. Overview

Plasma revenue represents the total protocol revenue generated from transaction fees on the Plasma blockchain. The metric captures revenue from Plasma's EIP-1559 implementation, where base fees are burned (protocol revenue) and priority fees go to validators. Since Plasma validators are currently internal to the protocol team, all transaction fees count as protocol revenue rather than supply-side revenue. The calculation aggregates daily transaction fees and converts them to USD.

## 2. Data sources

- **Plasma transaction records**: Individual transaction data including gas usage, effective gas prices, sender and recipient addresses, and transaction hashes
- **Plasma block data**: Block-level information containing base fee per gas values required for EIP-1559 fee calculations
- **End-of-day price feeds**: Daily closing prices for XPL token used for USD conversion
- **Token metadata**: XPL token information including contract address and symbol for the native Plasma token

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Collect and standardize raw transaction and block data from Plasma blockchain
- **Logic**: Extract transaction records with `gas_used`, `effective_gas_price`, sender and recipient addresses, and transaction timestamps. Join with block data to obtain `base_fee_per_gas` for each transaction. All transactions are associated with the XPL token address and labeled with 'plasma' chain identifier.
- **Key fields**: `gas_used` (gas consumed by transaction), `effective_gas_price` (total gas price paid), `base_fee_per_gas` (EIP-1559 base fee component), `block_timestamp` (transaction timing)

### Component B: Gas fee calculation
- **Purpose**: Calculate base fees and priority fees following EIP-1559 model
- **Logic**: For each transaction, compute base fees by multiplying `gas_used` by `base_fee_per_gas` and dividing by 10^18 for decimal normalization. Calculate priority fees by multiplying `gas_used` by the difference between `effective_gas_price` and `base_fee_per_gas`, then dividing by 10^18. Aggregate both fee components daily by summing across all transactions per day.
- **Key fields**: `base_fee` (fees burned by protocol), `priority_fee` (fees paid to validators), daily aggregation timestamp

### Component C: USD conversion and standardization
- **Purpose**: Convert XPL-denominated fees to USD and format according to Token Terminal metric standards
- **Logic**: Convert total daily fees (base fees plus priority fees) from XPL to USD using end-of-day price feeds. Apply standard Token Terminal metric formatting including business line classification as 'blockchain', market sector as 'blockchains_l1', and chain identifier as 'plasma'. Include timestamp grain specification as 'day'.
- **Key fields**: `fees` (USD-denominated daily fee total), `timestamp_grain`, `chain_id`, business classification fields

### Final aggregation
- **Combining components**: Total daily fees (base fees + priority fees) are calculated and converted to USD to represent total fee revenue
- **Currency conversion**: XPL token amounts converted to USD using end-of-day price feeds with decimal correction applied
- **Time aggregation**: Data aggregated to daily boundaries using day-truncated timestamps
- **Final calculation**: Revenue equals total fees since all Plasma validators are internal to the protocol (base fees + priority fees = protocol revenue, with zero supply-side revenue). When external validators launch, the methodology notes that only base fees should count as protocol revenue.

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

PlasmaXPL

Revenue

Revenue

Competitive landscape