Liquidity providers deposit funds into Mummy Finance and receive trading fees from traders (supply-side fees).

Mummy Finance is a non-custodial exchange for spot and perpetual contracts built on Fantom, Optimism, and Arbitrum. Mummy Finance was founded by an anonymous team and was launched in December 2022.

MMY tokenholders own and govern the protocol. They currently take a cut of the total trading fees paid by traders (revenue).

github

twitter

discord

etherscan

website

Derivative exchanges

Mummy Finance

# Mummy Finance Fees Methodology

## 1. Overview

The Mummy fees metric measures the total trading fees collected by the Mummy protocol across its perpetual and spot trading services. This metric quantifies the protocol's revenue from user trading activities on Arbitrum, Fantom, and Optimism networks. The calculation combines margin fees from leveraged perpetual trading with swap fees from spot trading, providing a comprehensive view of Mummy's fee generation across all supported trading types.

## 2. Data sources

- **Perpetual trading fees**: Parsed `Vault_CollectMarginFees` events from Mummy v1 Vault contracts on Arbitrum, Fantom, and Optimism, containing margin fee collections from leveraged perpetual trading activities
- **Spot trading fees**: Parsed `Vault_CollectSwapFees` events from Mummy v1 Vault contracts on the same three chains, containing swap fee collections from spot trading activities
- **Token metadata**: Token configuration data including symbols and decimal specifications for fee tokens
- **Price feeds**: End-of-day token price feeds for converting fee amounts to USD values

## 3. Step-by-step calculation

### Component A: Perpetual trading fees
- **Purpose**: Captures all margin fees collected from leveraged perpetual trading activities
- **Logic**: Extracts data from `Vault_CollectMarginFees` events across Arbitrum, Fantom, and Optimism chains. Each event represents a margin fee collection during perpetual trading. The component extracts the token address from the `token` field and the fee amount from the `feeTokens` field. Records are classified with 'Perpetual trading' as the business line, 'derivatives' as market sector, and 'perpetual' as business segment
- **Key fields**: `block_timestamp` for timing, `token` for the fee token address, `feeTokens` for the raw fee amount, `transaction_hash` and `log_index` for event identification

### Component B: Spot trading fees
- **Purpose**: Captures all swap fees collected from spot trading activities
- **Logic**: Extracts data from `Vault_CollectSwapFees` events across the same three chains. Each event represents a swap fee collection during spot trading. Uses identical field structure to perpetual fees, extracting token address and fee amounts. Records are classified with 'Spot trading' as the business line while maintaining the same market sector and business segment classifications
- **Key fields**: `block_timestamp` for timing, `token` for the fee token address, `feeTokens` for the raw fee amount, transaction and event identifiers

### Component C: Token metadata enrichment
- **Purpose**: Resolves token addresses to human-readable symbols and provides decimal configuration
- **Logic**: Joins both fee components with token metadata using chain and token address as join keys. This enrichment populates `account_name`, `contract_name`, and `token_symbol` fields with uppercase token symbols, enabling proper fee categorization and reporting
- **Key fields**: Token `symbol` from metadata, `chain` and token address as join keys

### Final aggregation
- **Combining components**: Both perpetual and spot fees are combined using a union operation, maintaining separate business line classifications while sharing the same overall structure and field definitions
- **Currency conversion**: Fee amounts are converted to USD using end-of-day token prices through the `convert_to_usd_and_correct_decimals` function, which also adjusts for token decimal places to ensure accurate monetary values
- **Time aggregation**: All timestamps are truncated to daily boundaries using `timestamp_trunc` with day granularity, enabling daily fee aggregation and reporting
- **Final calculation**: The metric applies zero-filling strategy to ensure continuous time series data and includes chain availability filtering to exclude data from chains that are not currently supported or active

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

Total value users pay to use a protocol (gross fees, user-paid fees).

Mummy Finance

Fees

Fees

Competitive landscape

Chain breakdown