Infrastructure

Maestro

# Maestro Revenue Methodology

## 1. Overview

Maestro revenue measures the total USD value of fees collected by the Maestro protocol on Solana. This metric answers the business question: "How much revenue does Maestro generate from user fees?" The calculation tracks all SOL payments made to Maestro's fee collection address, aggregates them daily, converts to USD, and treats the total fees as protocol revenue.

## 2. Data sources

- **Solana native transfers**: Records of all SOL transfers on the Solana blockchain, specifically transfers sent to Maestro's fee collection addresses
- **End-of-day price feeds**: Daily SOL/USD price data used for currency conversion
- **Solana transaction metadata**: Transaction timestamps, signers, and amounts in lamports (Solana's smallest unit)

## 3. Step-by-step calculation

### Component A: Fee extraction
- **Purpose**: Identifies and extracts all SOL payments made to Maestro for fees
- **Logic**: Filters Solana native SOL transfers to identify payments sent to the Maestro fee collection address `MaestroUL88UBnZr3wfoN7hqmNWFi3ZYCGqZoJJHE36`. Excludes transfers where the sender is also the fee collection address to avoid counting internal protocol transfers. Each qualifying transfer includes the transaction timestamp, amount in lamports, and transaction signer information.
- **Key fields**: `block_timestamp` for timing, `amount` in lamports, `transaction_signer` for the fee payer, `to_address` filtered to Maestro's fee address

### Component B: Daily aggregation and conversion
- **Purpose**: Aggregates raw fee payments into daily totals and converts to standard SOL units
- **Logic**: Groups all fee transfers by day using timestamp truncation. Sums the total SOL amounts received each day, converting from lamports to SOL by dividing by 1e9 (since 1 SOL = 1 billion lamports). Creates daily fee totals in SOL for each day that had fee activity.
- **Key fields**: `timestamp` truncated to day granularity, `fees` as the daily sum in SOL units, `token_address` set to SOL's address, `chain_id` as 'solana'

### Component C: USD conversion
- **Purpose**: Converts daily SOL fee amounts to USD values using market prices
- **Logic**: Takes the daily SOL fee totals and converts them to USD using end-of-day price feeds. The conversion uses the `convert_to_usd_and_correct_decimals` macro with USD conversion enabled but decimal correction disabled (since SOL amounts are already properly formatted).
- **Key fields**: `fees` converted from SOL to USD values using daily exchange rates

### Final aggregation
- **Combining components**: The fee data flows directly from extraction through aggregation to USD conversion in a linear pipeline
- **Currency conversion**: Uses end-of-day SOL/USD price feeds to convert daily SOL fee totals to USD
- **Time aggregation**: Daily boundaries based on Solana block timestamps, with gaps filled using zeros for days without fee activity
- **Final calculation**: Daily revenue equals the total USD value of all SOL fees collected by Maestro on that day. The `finalize_metric_revenue` macro applies standard schema formatting, validates chain and product IDs, and ensures complete daily time series with zero-filling for missing days.

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

Maestro

Revenue

Revenue

Competitive landscape

Chain breakdown