# Mythos Substrate Revenue Methodology

## 1. Overview

The portion of fees that Mythos Substrate retains is measured by the Revenue metric. For this product, all transaction-related fees collected at the network level are considered protocol revenue. This includes both the base transaction fees and additional tips paid by users to prioritize transaction processing. Revenue is captured as a 100% share of the total fees generated from activity on the Mythos Substrate chain.

## 2. Data sources

- **Blockchain events**: `TransactionFeePaid` events, covering Mythos
- **External data**: End-of-day price feeds for the native MYTH asset

## 3. Step-by-step calculation

### Component A: Network fee extraction

- **Purpose**: Identify and collect all fee-related activity from the Mythos Substrate network.
- **Logic**: `TransactionFeePaid` events are parsed from the chain's event logs. For each event, both the base fee amount and the optional tip amount are extracted from the event data. These values are summed to determine the total cost paid by the user for the transaction.
- **Key fields**: `amount` (base fee) and `tip` (user-added priority fee).

### Component B: Protocol revenue determination

- **Purpose**: Calculate the specific portion of fees that is retained by the project as revenue.
- **Logic**: A 100% take rate is applied to the network fees extracted from Mythos Substrate. Unlike the associated Marketplaces where fees may be directed to external entities or third parties, all transaction fees paid on the base chain are recognized as protocol revenue. The total revenue for the product is equated to the sum of the base fees and tips.
- **Key fields**: `amount`, `tip`.

### Component C: USD conversion and aggregation

- **Purpose**: Standardize the native asset values into USD for reporting and cross-chain comparison.
- **Logic**: Native asset amounts are normalized by decimal precision. These normalized values are then multiplied by the end-of-day price of the MYTH asset. All revenue values are aggregated to a daily granularity using UTC day boundaries.
- **Key fields**: `block_timestamp` (timing) and `amount` (normalized value).

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

Revenue

Blockchains (L1)

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

Mythos Substrate

Archived

Revenue

Revenue

Chain breakdown