Validators process transactions and receive fees from users (supply-side fees).

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Revenue Methodology

## 1. Overview

The Astar revenue metric measures the total fees collected by the Astar network from both Layer 1 (native Substrate) and Layer 2 (EVM-compatible) transactions. All transaction fees paid to the network are considered protocol revenue, providing a comprehensive view of Astar's fee-based income across its dual-layer architecture.

## 2. Data sources

The calculation uses the following raw data sources:
- **Astar blockchain event logs**: Native Astar blockchain events containing transaction fee payments, including pallet-level event data with method signatures and parameters
- **Transaction metadata**: Astar transaction records with extrinsic IDs, block timestamps, and success status indicators  
- **End-of-day price feeds**: CoinGecko price data for ASTAR token to enable USD conversion of native fee amounts

## 3. Step-by-step calculation

### Component A: Layer 1 fee extraction
- **Purpose**: Captures transaction fees from native Astar Substrate transactions
- **Logic**: Filters blockchain events for `transactionPayment` pallet events with method `TransactionFeePaid`. Extracts fee amounts from the `event_data` JSON array, specifically the `transaction_fee` from position 1 and `transaction_tip` from position 2. Combines these amounts to get total Layer 1 transaction fees per extrinsic
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `timestamp`

### Component B: Layer 2 fee extraction  
- **Purpose**: Captures transaction fees from Astar EVM-compatible transactions
- **Logic**: Identifies EVM transactions through `ethereum` pallet events with method `Executed` to get transaction signers. Then processes `balances` pallet events with methods `Withdraw` and `Deposit` for these ethereum transactions. Matches signer addresses between the ethereum execution and balance changes to ensure proper attribution. Withdraw amounts are positive fees, deposit amounts are negative (refunds), creating a net fee calculation
- **Key fields**: `transaction_fee`, `signer_address`, `extrinsic_id`, `event_method`

### Component C: Fee aggregation
- **Purpose**: Combines Layer 1 and Layer 2 fees into unified daily totals
- **Logic**: Unions the Layer 1 and Layer 2 fee streams, applies decimal conversion by dividing amounts by 10^18 to convert from wei-equivalent units to standard ASTAR token units. Aggregates by day with `timestamp_grain` set to 'day' and assigns `product_id` as 'Astar Substrate'
- **Key fields**: `fees`, `chain_id`, `product_id`, `timestamp`

### Component D: USD conversion
- **Purpose**: Converts ASTAR token fees to USD values
- **Logic**: Uses CoinGecko price feeds with `coingecko_id` set to 'astar' to obtain end-of-day ASTAR/USD exchange rates. Multiplies daily fee amounts by corresponding daily prices to get USD-denominated values
- **Key fields**: `fees_usd`, `coingecko_id`, `daily_timestamp`

### Final aggregation
- **Combining components**: The revenue metric directly uses the USD-converted fees from the fee calculation without additional processing, since all chain fees are considered protocol revenue
- **Currency conversion**: End-of-day CoinGecko prices applied to convert native ASTAR amounts to USD
- **Time aggregation**: Daily boundaries using `timestamp_trunc` to day granularity  
- **Final calculation**: Revenue equals total daily fees in USD, representing all transaction fees collected by the Astar network across both its Layer 1 Substrate and Layer 2 EVM environments

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

AstarASTR

Revenue

Revenue

Competitive landscape

Chain breakdown