twitter

discord

etherscan

website

Infrastructure

Aethir

# Aethir Token holders Methodology

## 1. Overview

The Aethir tokenholders metric counts the total number of unique addresses that hold Aethir (ATH) tokens with a balance greater than zero across Ethereum and Arbitrum networks. This metric provides insight into token distribution and adoption by measuring the size of the active holder base. The calculation processes token transfer events from both supported chains to determine current token balances and identify addresses with positive holdings.

## 2. Data sources

The calculation relies on several key blockchain data sources:

- **Token transfer events**: Parsed ERC-20 `Transfer` events from Ethereum and Arbitrum networks for the Aethir token contracts
- **Transaction logs**: Ethereum and Arbitrum transaction event logs containing token movement data
- **Token contract addresses**: Aethir token contract addresses on Ethereum (`0xbe0ed4138121ecfc5c0e56b40517da27e6c5226b`) and Arbitrum (`0xc87b37a581ec3257b734886d9d3a581f5a9d056c`)
- **Balance snapshots**: Historical and current token balance data derived from transfer events
- **Chain availability data**: Metadata about data completeness and synchronization status for each blockchain network

## 3. Step-by-step calculation

### Component A: Ethereum tokenholder identification
- **Purpose**: Identifies all addresses holding Aethir tokens on the Ethereum network
- **Logic**: The system processes all `Transfer` events for the Aethir token contract on Ethereum. For each transfer event, it extracts the `from` address, `to` address, and `value` transferred. The system then calculates running balances for each address by summing all incoming transfers and subtracting all outgoing transfers. Only addresses with a final balance greater than zero are counted as tokenholders. Special handling excludes the zero address (`0x0000000000000000000000000000000000000000`) which represents token burns or mints.
- **Key fields**: The process tracks `holder_address` (the wallet address), `balance` (current token balance), and `date` (calculation date)

### Component B: Arbitrum tokenholder identification  
- **Purpose**: Identifies all addresses holding Aethir tokens on the Arbitrum network
- **Logic**: Similar to the Ethereum component, this processes all `Transfer` events for the Aethir token contract on Arbitrum. The system calculates running balances for each address by processing transfer events chronologically. It sums incoming transfers and subtracts outgoing transfers to determine current balances. Only addresses with positive balances are counted as active tokenholders. The zero address is excluded from the count as it represents protocol-level operations rather than user holdings.
- **Key fields**: Tracks `holder_address`, `balance`, and `date` for each qualifying address

### Component C: Cross-chain aggregation
- **Purpose**: Combines tokenholder data from both Ethereum and Arbitrum networks
- **Logic**: Results from both chains are merged using a union operation to create a comprehensive view of all Aethir tokenholders. If the same address holds tokens on both chains, it is typically counted as a single unique tokenholder to avoid double-counting, though this depends on the specific implementation in the `calculate_tokenholders` macro.
- **Key fields**: Maintains `holder_address`, `balance`, `date`, and adds `chain_id` to identify the source network

### Final aggregation
- **Combining components**: The combined tokenholder data undergoes final processing through the finalization macro, which standardizes the output format, adds project metadata, and ensures consistent time boundaries
- **Time aggregation**: Daily snapshots are created showing the tokenholder count for each date, with calculations typically performed at the end of each day
- **Data quality filtering**: Chain availability filters ensure that only data from properly synchronized and validated blockchain networks is included in the final count
- **Final calculation**: The final metric represents the distinct count of addresses holding Aethir tokens with balance greater than zero across both supported networks on each given date

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

Unique addresses holding a non-zero balance of the project's native token.

AethirATH

Token holders

Token holders

Competitive landscape

Chain breakdown