Infrastructure

Maestro

# Maestro Supply-side fees Methodology

## 1. Overview

The Maestro supply side fees metric measures the fees paid by the protocol to liquidity providers or other supply-side participants. This metric captures the cost structure for suppliers of liquidity or services within the Maestro protocol on Solana. For Maestro, this metric is consistently zero, reflecting that the protocol operates on a demand-side fee model where users pay fees but liquidity providers do not receive fee sharing.

## 2. Data sources

The calculation uses the following raw data sources:
- **Solana native SOL transfers**: All SOL transfers on the Solana blockchain, specifically transfers to and from the Maestro fee collection address
- **End-of-day token price feeds**: Daily SOL to USD conversion rates for standardizing fee amounts
- **Solana transaction records**: Transaction metadata including signers, timestamps, and transaction identifiers

## 3. Step-by-step calculation

### Component A: Fee collection identification
- **Purpose**: Identify all fees collected by the Maestro protocol
- **Logic**: Extract native SOL transfers where the recipient address is the Maestro fee collection address `MaestroUL88UBnZr3wfoN7hqmNWFi3ZYCGqZoJJHE36`. Filter out any transfers where the sender is also this fee address to exclude internal protocol transfers or redistributions. Include transaction metadata such as the `transaction_signer`, `transaction_id`, and `block_timestamp` for each transfer.
- **Key fields**: `amount` (transfer amount in lamports), `to_address` (recipient), `transaction_signer` (originating user), `block_timestamp` (transaction timing)

### Component B: Fee amount processing
- **Purpose**: Convert raw transfer amounts to standardized SOL units and aggregate by day
- **Logic**: Convert transfer amounts from lamports (Solana's smallest unit) to SOL by dividing by 1 billion (1e9). Truncate timestamps to daily boundaries and group all transfers by day, chain, product ID, and token address. Sum all fee amounts within each daily group to get total daily fees collected.
- **Key fields**: `fees` (daily aggregated SOL amount), `timestamp` (daily boundary), `chain_id` (always 'solana'), `token_address` (always SOL token address)

### Component C: USD conversion
- **Purpose**: Standardize fee amounts in USD for cross-protocol comparison
- **Logic**: Convert daily SOL fee amounts to USD using end-of-day SOL price feeds. Apply the conversion macro that matches daily fee amounts with corresponding daily SOL prices to calculate USD equivalent values.
- **Key fields**: `fees_usd` (USD-denominated fee amounts)

### Final aggregation
- **Combining components**: The supply side fees metric takes the processed fee data and applies a business logic override
- **Supply-side fee allocation**: Set the `fees_supply_side` field to zero for all records, reflecting that Maestro does not distribute fees to liquidity providers or other supply-side participants
- **Currency conversion**: Maintain the same USD conversion methodology as the underlying fees data
- **Time aggregation**: Preserve daily aggregation boundaries from the underlying fee calculation
- **Final calculation**: The final supply side fees value is always zero, regardless of the underlying fee amounts collected by the protocol. This represents Maestro's business model where all collected fees are retained by the protocol rather than shared with liquidity providers.

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

Portion of fees distributed to service providers or supply-side participants.

Maestro

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown