twitter

discord

etherscan

website

Infrastructure

Aethir

# Aethir Cost of revenue Methodology

## 1. Overview

The Aethir cost of revenue metric measures the total amount paid to infrastructure providers for their services on the Aethir decentralized computing platform. This metric captures the protocol's operational costs by tracking service fee payments made to providers when they claim their earned fees. The calculation aggregates daily payments across all providers and tokens, converted to USD, representing the direct cost of providing infrastructure services to users.

## 2. Data sources

The metric utilizes the following raw data sources:
- **Blockchain events**: Parsed Arbitrum `AethirCore_ClaimServiceFee` events from the core Aethir protocol contract (`0xc87b37a581ec3257b734886d9d3a581f5a9d056c`)
- **Transaction data**: Arbitrum token transfer records that capture the actual payment flows
- **External data**: End-of-day token price feeds for USD conversion and token metadata for decimal precision handling
- **Protocol data**: Provider address information and business classification metadata

## 3. Step-by-step calculation

### Component A: Service fee claim identification
- **Purpose**: Identifies when infrastructure providers claim their service fees from the Aethir protocol
- **Logic**: Filters for `AethirCore_ClaimServiceFee` events emitted by the core Aethir contract on Arbitrum. Each event represents a provider claiming earned fees for infrastructure services provided. The events include the provider address (`provider` field) and transaction details for matching with payment transfers
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for unique identification, `provider` address for the fee recipient, and contract address for the token being claimed

### Component B: Payment amount capture
- **Purpose**: Captures the actual token amounts paid to providers when they claim service fees
- **Logic**: Joins the service fee claim events with Arbitrum token transfer records using three matching criteria: same `block_timestamp`, same `transaction_hash`, and the provider address from the claim event must match the `to_address` in the token transfer. This ensures we capture only the specific token payments made to providers as part of their fee claims, representing the protocol's cost of revenue
- **Key fields**: `value` from token transfers representing the payment amount, `token_address` for the specific token being transferred, and recipient validation through address matching

### Component C: Daily aggregation
- **Purpose**: Aggregates all provider payments into daily totals by token and chain
- **Logic**: Groups all matched provider payment events by day using timestamp truncation, chain identifier, and token address. Sums the total `amount` paid to all providers for each day and token combination. This provides daily cost of revenue figures broken down by payment token
- **Key fields**: Daily truncated `timestamp`, `chain_id` for network identification, `token_address` for token-specific totals, and aggregated `cost_of_revenue` amounts

### Final aggregation
- **Combining components**: The daily aggregated provider payments form the base cost of revenue data, with each day representing the total amount paid to infrastructure providers
- **Currency conversion**: Token amounts are converted to USD using end-of-day price feeds, with proper decimal correction applied based on each token's decimal precision to ensure accurate USD valuations
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with the finalization process applying a zero-filling strategy for days with no provider payments
- **Final calculation**: The final metric represents the total USD value of payments made to infrastructure providers each day, calculated as the sum of all provider fee claim payments converted to USD with proper decimal handling and gap-filling applied for complete time series data

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

Expenses paid to third parties to deliver core service output.

AethirATH

Cost of revenue

Cost of revenue

Competitive landscape

Chain breakdown