website

twitter

Infrastructure

Trojan

# Trojan Fees Methodology

## 1. Overview

Trojan fees represent the total daily fees collected by the Trojan protocol on Solana. This metric measures protocol revenue by tracking native SOL transfers to designated fee collection addresses. The calculation aggregates all SOL transfers to specific Trojan fee accounts, converts amounts from lamports to SOL, and then converts to USD using end-of-day price feeds.

## 2. Data sources

- **Solana native transfers**: Native SOL transfer events on the Solana blockchain, specifically transfers where the recipient is a designated Trojan fee collection address
- **End-of-day price feeds**: Token price data used to convert SOL amounts to USD values
- **Token metadata**: SOL token information including decimal places for proper unit conversion

## 3. Step-by-step calculation

### Component A: Raw fee extraction
- **Purpose**: Identifies and extracts all SOL transfers that represent fees paid to Trojan protocol
- **Logic**: Filters Solana native transfer events to include only transfers where the recipient address matches the hardcoded Trojan fee collection address `9yMwSPk9mrXSN7yDHUuZurAh1sjbJsfpUqjZ7SvVtdco`. Each transfer record includes the transfer amount, transaction details, and timestamp. The `token_address` is set to the native SOL token identifier `So11111111111111111111111111111111111111112` for all records.
- **Key fields**: `block_timestamp` for timing, `transaction_id` for deduplication, `transaction_signer` as the fee payer, `amount` in lamports (raw SOL units), and `token_address` identifying SOL

### Component B: Daily aggregation and unit conversion
- **Purpose**: Converts raw lamport amounts to SOL and aggregates fees by day
- **Logic**: Groups all fee transfers by day using timestamp truncation to daily boundaries. Converts amounts from lamports to SOL by dividing by 1e9 (since 1 SOL = 1,000,000,000 lamports). Sums all converted amounts for each day to get total daily fees in SOL. Groups by timestamp, chain identifier, product identifier, and token address to maintain proper dimensional structure.
- **Key fields**: `timestamp` truncated to day level, `fees` as the summed SOL amount, `chain_id` set to 'solana', `token_address` for SOL

### Component C: USD conversion and schema finalization
- **Purpose**: Converts SOL amounts to USD and applies final data quality measures
- **Logic**: Uses end-of-day price feeds to convert daily SOL fee amounts to USD values. The conversion process maintains the existing decimal structure since amounts are already properly converted from lamports to SOL units. Applies schema validation to ensure consistent field structure and data types. Implements zero-filling strategy to create records with zero values for any missing days, ensuring complete time series data.
- **Key fields**: `fees` converted to USD values, standardized timestamp and dimensional fields

### Final aggregation
- **Combining components**: The components flow sequentially - raw transfers are filtered and extracted, then aggregated daily with unit conversion, then converted to USD and finalized with data quality measures
- **Currency conversion**: SOL amounts are converted to USD using end-of-day price feeds, with the conversion applied after daily aggregation to use appropriate daily exchange rates
- **Time aggregation**: All data is aggregated to daily boundaries using timestamp truncation, with timezone handling preserving the original Solana block timestamps
- **Final calculation**: The final metric value represents the total USD value of fees collected by Trojan protocol each day, calculated as the sum of all SOL transfers to fee collection addresses, converted from lamports to SOL (divided by 1e9), then converted to USD using end-of-day exchange rates

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

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

Trojan

Fees

Fees

Competitive landscape