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

Mythos is a specialized gaming blockchain powered by Polkadot Relay chain.

MYTH holders own and govern the protocol.

website

github

twitter

etherscan

Blockchains (L2)

Mythos

# Mythos Revenue Methodology

## 1. Overview

Mythos revenue measures the daily USD value of transaction fees collected by the Mythos DAO from network operations. The metric focuses exclusively on core blockchain transaction fees that generate actual revenue for the DAO, while explicitly excluding marketplace trading fees and dmarket fees which are considered "mythical revenue" that doesn't accrue to the DAO. This metric answers the question: "How much revenue does the Mythos DAO generate from network transaction fees?"

## 2. Data sources

- **Mythos blockchain events**: Parsed event logs from the Mythos blockchain containing transaction fee payments, marketplace orders, and dmarket trades
- **Transaction fee events**: `TransactionFeePaid` events from the Mythos chain that record network transaction fees and tips
- **Marketplace trading events**: `OrderExecuted` events from the marketplace pallet that record NFT trading activity and associated fees
- **Dmarket trading events**: `Trade` events from the dmarket pallet that record item trading activity and fees
- **External price data**: End-of-day MYTH token price feeds from CoinGecko API for USD conversion

## 3. Step-by-step calculation

### Component A: Mythos Substrate transaction fees
- **Purpose**: Calculates revenue from core blockchain transaction fees that accrue to the Mythos DAO
- **Logic**: Extracts `TransactionFeePaid` events from Mythos blockchain event logs, parsing JSON event data arrays to extract fee `amount` and `tip` values from positions 1 and 2. Converts amounts from 18-decimal precision native MYTH tokens to standard units by dividing by 1e18. Aggregates daily totals by summing `amount` plus `tip` for each day, then converts to USD using end-of-day MYTH token prices from CoinGecko
- **Key fields**: `amount` (base transaction fee), `tip` (additional tip paid), `block_timestamp` (transaction timing)

### Component B: Marketplace trading fees
- **Purpose**: Tracks marketplace trading activity but explicitly excludes fees from revenue calculation
- **Logic**: Extracts `OrderExecuted` events from the marketplace pallet, parsing JSON event data to extract `buyer_fee` and `seller_fee` from positions 5 and 6. Converts from 18-decimal precision and sums both fees daily, then converts to USD using MYTH token prices. However, sets final `revenue` value to 0 as these fees are considered "mythical revenue" that don't apply to the Mythos DAO
- **Key fields**: `buyer_fee` (fee paid by buyer), `seller_fee` (fee paid by seller), but `revenue` is hardcoded to 0

### Component C: Dmarket trading fees  
- **Purpose**: Tracks dmarket trading activity but explicitly excludes fees from revenue calculation
- **Logic**: Extracts `Trade` events from the dmarket pallet, parsing JSON event data to extract `fee` amounts from position 4. Converts from 18-decimal precision and aggregates daily totals, then converts to USD using MYTH token prices. However, sets final `revenue` value to 0 as these fees are considered "mythical revenue" that don't apply to the Mythos DAO
- **Key fields**: `fee` (trading fee amount), but `revenue` is hardcoded to 0

### Final aggregation
- **Combining components**: Uses UNION ALL to combine all three revenue components (Mythos Substrate, marketplace, dmarket) into a single dataset, maintaining separate `product_id` identifiers for each component
- **Currency conversion**: Applies end-of-day MYTH token prices from CoinGecko API to convert all native token amounts to USD values using the `convert_usd_cg` macro with coingecko ID 'mythos'
- **Time aggregation**: Groups all data by daily boundaries using `timestamp_trunc` to day level, with `timestamp_grain` set to 'day'
- **Final calculation**: Sums revenue across all components, though in practice only Mythos Substrate contributes non-zero revenue. Applies `finalize_metric_revenue` macro with 'fill_zeros' strategy to ensure complete daily coverage and chain availability filtering to maintain data quality

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

MythosMYTH

Archived

Revenue

Revenue

Competitive landscape

Chain breakdown