twitter

discord

etherscan

website

Infrastructure

Aethir

# Aethir Expenses Methodology

## 1. Overview

The Aethir expenses metric measures the total operational costs of the Aethir decentralized cloud infrastructure protocol, aggregated daily in USD. This metric combines two primary expense categories: cost of revenue (service fees paid to infrastructure providers) and token incentives (rewards distributed to providers). The calculation identifies specific protocol events on Arbitrum blockchain, matches them with corresponding token transfers to determine actual payment amounts, and aggregates these into a comprehensive daily expense figure that reflects the protocol's operational costs.

## 2. Data sources

- **Arbitrum blockchain events**: Parsed `AethirCore_ClaimServiceFee` and `AethirCore_ClaimReward` events from the Aethir protocol contract `0xc87b37a581ec3257b734886d9d3a581f5a9d056c`
- **Arbitrum token transfers**: Token transfer records on Arbitrum blockchain used to capture actual payment amounts
- **External data**: End-of-day token price feeds for USD conversion and token metadata for decimal precision correction

## 3. Step-by-step calculation

### Component A: Cost of revenue identification
- **Purpose**: Identifies service fee payments made to infrastructure providers
- **Logic**: Extracts `AethirCore_ClaimServiceFee` events from the Aethir protocol contract on Arbitrum. Each event contains metadata including `block_timestamp`, `transaction_hash`, `log_index`, account addresses, and `provider` address. Events are classified with business line as "Infrastructure", market sector as "infrastructure", and business segment as "infrastructure". All events are associated with protocol version "v1" and the specific Aethir token contract address.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for event identification, `address` as account address, `provider` as the recipient infrastructure provider address

### Component B: Token incentives identification  
- **Purpose**: Identifies reward payments distributed to infrastructure providers
- **Logic**: Extracts `AethirCore_ClaimReward` events from the same Aethir protocol contract on Arbitrum. These events follow identical structure to service fee events but represent protocol rewards rather than direct service payments. Events receive the same business classification and metadata tagging as cost of revenue events.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for event identification, `address` as account address, `provider` as the recipient infrastructure provider address

### Component C: Amount determination for cost of revenue
- **Purpose**: Matches service fee events with actual token transfer amounts
- **Logic**: Joins the identified `AethirCore_ClaimServiceFee` events with Arbitrum token transfer records using exact matches on `block_timestamp`, `transaction_hash`, and provider address (where event `provider` equals transfer `to_address`). This ensures each service fee event is paired with its corresponding token transfer to capture the actual payment amount. The `value` field from token transfers provides the raw payment amount.
- **Key fields**: `value` from token transfers representing the raw payment amount in token units

### Component D: Amount determination for token incentives
- **Purpose**: Matches reward events with actual token transfer amounts  
- **Logic**: Applies identical matching logic as cost of revenue component, joining `AethirCore_ClaimReward` events with Arbitrum token transfer records on `block_timestamp`, `transaction_hash`, and provider address matching. This captures the actual token amounts distributed as rewards to infrastructure providers.
- **Key fields**: `value` from token transfers representing the raw reward amount in token units

### Component E: Cost of revenue aggregation and conversion
- **Purpose**: Aggregates daily cost of revenue and converts to USD
- **Logic**: Groups the matched cost of revenue events by day using `timestamp_trunc` on `block_timestamp`, chain identifier, product identifier ("aethir"), and `token_address`. Sums the `amount` values to get total daily cost of revenue. Applies the `convert_to_usd_and_correct_decimals` macro to handle token decimal precision and convert amounts to USD using end-of-day price feeds. Uses the `finalize_metric_cost_of_revenue` macro to ensure proper schema, validate identifiers, and fill any date gaps with zeros.
- **Key fields**: Daily aggregated `cost_of_revenue` amount in USD

### Component F: Token incentives aggregation and conversion
- **Purpose**: Aggregates daily token incentives and converts to USD
- **Logic**: Follows identical aggregation pattern as cost of revenue, grouping by day, chain, product, and token address. Sums token incentive amounts and applies the same USD conversion and decimal correction process. Uses the `finalize_metric_token_incentives` macro for schema validation and gap filling.
- **Key fields**: Daily aggregated `token_incentives` amount in USD

### Final aggregation
- **Combining components**: Unions the daily cost of revenue amounts and daily token incentives amounts into a single expenses dataset, with each component labeled by its expense type
- **Currency conversion**: Both components are converted to USD using end-of-day price feeds, with token decimal precision automatically corrected based on token metadata
- **Time aggregation**: All amounts are aggregated to daily boundaries using day-truncated timestamps, with timestamp grain marked as "day"
- **Final calculation**: The total daily expenses represent the sum of all cost of revenue and token incentive payments made by the Aethir protocol to infrastructure providers, providing a comprehensive view of the protocol's operational costs

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

Total project operating and incentive expenses.

AethirATH

Expenses

Expenses

Competitive landscape

Chain breakdown