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

Energy Web X is energy blockchain ecosystem powered by Polkadot Relay chain.

website

twitter

github

etherscan

Blockchains (L2)

Energy Web X

# Energy Web X Revenue Methodology

## 1. Overview

The Energy Web revenue metric measures the net protocol revenue generated by the Energy Web Chain, a substrate-based blockchain focused on energy sector applications. Revenue is calculated as the total transaction fees collected by the network minus any fees distributed to supply-side participants. Since Energy Web operates as a proof-of-authority network without supply-side fee sharing, the revenue equals the total transaction fees collected from users who pay for executing transactions and smart contract interactions on the network.

## 2. Data sources

- **Energy Web Chain blockchain events**: Raw blockchain events from the Energy Web Chain substrate blockchain, specifically `transactionPayment` pallet events
- **Transaction payment data**: `TransactionFeePaid` events containing fee and tip amounts paid by users for transaction execution
- **External price data**: End-of-day CoinGecko price feeds for Energy Web Token (EWT) for USD conversion
- **Extrinsic metadata**: Transaction identifiers and execution context from Energy Web Chain substrate blockchain

## 3. Step-by-step calculation

### Component A: Raw event extraction
- **Purpose**: Extract and filter relevant blockchain events from Energy Web Chain
- **Logic**: The calculation begins by collecting all blockchain events from Energy Web Chain, then filtering specifically for events from the `transactionPayment` pallet with the `TransactionFeePaid` method. These events are generated whenever a user pays fees to execute a transaction on the network. Events are aggregated daily using timestamp truncation and include metadata such as block numbers, event indices, and extrinsic identifiers.
- **Key fields**: `timestamp`, `event_pallet`, `event_method`, `event_data`, `extrinsic_id`

### Component B: Fee data parsing and processing
- **Purpose**: Extract and process transaction fee amounts from blockchain event data
- **Logic**: For each `TransactionFeePaid` event, the system parses the `event_data` JSON array to extract two fee components: the base `transaction_fee` from position 1 and the optional `transaction_tip` from position 2. These amounts are combined to calculate the total fee paid per transaction. The fee amounts are then converted from the native 18-decimal format (wei-equivalent) to standard token units by dividing by 10^18. All fees are aggregated daily and associated with the Energy Web chain identifier.
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `chain_id`

### Component C: USD conversion and fee aggregation
- **Purpose**: Convert EWT fee amounts to USD and aggregate into the standard fees metric format
- **Logic**: The processed fee data is joined with end-of-day CoinGecko price feeds for Energy Web Token using the `coingecko_id` of 'energy-web-token'. Daily fee totals are converted to USD amounts using the conversion macro. The data is structured with standard metric dimensions including timestamp grain (daily), market sector ('blockchains_l1'), and business segment ('blockchain'). Missing product IDs are set to null since Energy Web operates as a single blockchain product.
- **Key fields**: `fees`, `coingecko_id`, `timestamp_grain`, `market_sector_id`

### Component D: Supply-side fee calculation
- **Purpose**: Calculate fees distributed to supply-side participants (validators, stakers)
- **Logic**: For Energy Web Chain, supply-side fees are set to zero since the network operates as a proof-of-authority consensus mechanism without fee sharing to validators or stakers. All transaction fees are retained by the protocol as revenue. The supply-side fees are structured with the same dimensional metadata as the total fees for consistency in the final revenue calculation.
- **Key fields**: `fees_supply_side`, `timestamp`, `chain_id`

### Final aggregation
- **Combining components**: The revenue calculation combines total fees (positive) with supply-side fees (negative) using a UNION ALL operation. Total fees from the fees metric are added as positive revenue, while supply-side fees are subtracted by adding them as negative values using the `-fees_supply_side` expression.
- **Currency conversion**: All amounts are converted to USD using end-of-day CoinGecko price feeds for Energy Web Token, ensuring consistent currency reporting across the metric timeline.
- **Time aggregation**: Data is aggregated daily with timestamps truncated to day boundaries, creating daily revenue totals for the Energy Web Chain.
- **Final calculation**: Net revenue equals total transaction fees minus supply-side fees. Since Energy Web has zero supply-side fees, the final revenue metric equals the total USD value of transaction fees collected daily on the Energy Web Chain.

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

Energy Web XEWT

Revenue

Revenue

Competitive landscape

Chain breakdown