twitter

discord

etherscan

website

Infrastructure

Aethir

# Aethir Supply-side fees Methodology

## 1. Overview

The Aethir fees supply side metric measures the total fees distributed to infrastructure providers (supply side participants) in the Aethir network on a daily basis. Aethir operates a decentralized GPU infrastructure network where users pay fees to access computing resources. However, this metric explicitly returns zero for all time periods, indicating that Aethir's current fee structure does not distribute collected fees to infrastructure providers on the supply side.

## 2. Data sources

The calculation uses the following data sources:
- **Arbitrum blockchain event logs**: Parsed `DepositServiceFee` events from Aethir's core smart contract
- **Aethir Core contract events**: Fee payment events captured when users deposit fees for infrastructure services
- **Token metadata**: Aethir token contract information for the native token used in fee payments
- **Chain availability data**: Arbitrum network availability information for data completeness validation

## 3. Step-by-step calculation

### Component A: Fee event collection
- **Purpose**: Extracts all fee payment events from Aethir's infrastructure network
- **Logic**: Collects parsed `DepositServiceFee` events from Aethir's core contract deployed on Arbitrum at address `0xc87b37a581ec3257b734886d9d3a581f5a9d056c`. Events are deduplicated using all available fields to ensure each fee payment is counted exactly once. The system extracts the fee `amount`, transaction metadata including `block_timestamp`, `transaction_hash`, and `log_index`, plus the paying `address`
- **Key fields**: Event `amount` representing fees paid by users, `block_timestamp` for temporal aggregation, `address` for the fee payer, and contract `address` for the Aethir token

### Component B: Business classification and standardization  
- **Purpose**: Categorizes fee events and applies business logic classifications
- **Logic**: All collected fee events are classified under the 'Infrastructure' business line since Aethir operates GPU infrastructure services. The system maps all fees to the 'infrastructure' market sector and business segment. Events are tagged with version 'v1' and associated with the Arbitrum chain identifier
- **Key fields**: `business_line` set to 'Infrastructure', `market_sector_id` and `business_segment_id` both set to 'infrastructure', `chain` identifier set to 'arbitrum'

### Final aggregation
- **Combining components**: Fee events are aggregated by day using timestamp truncation to daily boundaries. The system explicitly sets `fees_supply_side` to 0 for all records, regardless of the actual fee amounts collected from users
- **Currency conversion**: Not applicable since the final metric value is hardcoded to 0
- **Time aggregation**: Daily aggregation boundaries are created by truncating `block_timestamp` to day level, ensuring consistent daily reporting periods
- **Final calculation**: The metric calculation takes all processed fee events, groups them by day, token address, and chain, but assigns a constant value of 0 to `fees_supply_side`. This indicates that while Aethir collects fees from users for infrastructure services, none of these fees are currently distributed to infrastructure providers on the supply side. The finalize metric macro ensures proper schema compliance, validates project and chain identifiers, and fills any gaps in the time series with zero values using a forward-fill strategy.

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

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

AethirATH

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown