website

twitter

github

Blockchains (L2)

Aventus

# Aventus Revenue Methodology

## 1. Overview

Aventus revenue represents the total daily fees collected by the Aventus blockchain from transaction processing. This metric captures both base transaction fees and tips paid by users, providing insight into the economic activity and fee generation of the Aventus network. The calculation aggregates all successful transaction fees on a daily basis and converts them to USD for standardized reporting.

## 2. Data sources

- **Aventus blockchain events**: Parsed `TransactionFeePaid` events from the Aventus blockchain that record fee payments for successful transactions
- **Transaction data**: Aventus extrinsic data including block timestamps, transaction hashes, and event indices for proper transaction tracking
- **External data**: End-of-day price feeds from CoinGecko for AVT token to enable USD conversion
- **Token metadata**: Aventus token decimal information (18 decimals) for proper unit conversion

## 3. Step-by-step calculation

### Component A: Raw fee extraction
- **Purpose**: Extract and process individual transaction fee payments from Aventus blockchain events
- **Logic**: Filter for `TransactionFeePaid` events where the transaction was successful. Parse the event data JSON structure to extract two fee components: the base `amount` (from the second array element) and the `tip` (from the third array element). Convert both values from the native 18-decimal format to standard decimal representation by dividing by 1e18. Include transaction metadata such as `block_timestamp`, `block_number`, `extrinsic_hash`, and `event_index` for proper tracking and deduplication.
- **Key fields**: `amount` and `tip` values extracted from `event_data` JSON array, `block_timestamp` for daily aggregation, `success` flag for filtering valid transactions

### Component B: Daily fee aggregation and USD conversion
- **Purpose**: Aggregate individual transaction fees into daily totals and convert to USD value
- **Logic**: Group all fee data by day using timestamp truncation to daily boundaries. For each day, sum the total fees by adding both the base `amount` and `tip` components for all transactions. Apply USD conversion using end-of-day CoinGecko price feeds for the AVT token, matching the aggregation date to the appropriate price feed date. Include standard dimensional fields for chain identification and product categorization.
- **Key fields**: Daily aggregated `fees` representing total AVT collected, `timestamp` truncated to day boundaries, `chain_id` as 'aventus', `product_id` as 'aventuschain'

### Final aggregation
- **Combining components**: The daily aggregated USD-denominated fees flow directly to the final metric without additional combination steps
- **Currency conversion**: USD conversion occurs at the daily aggregate level using CoinGecko end-of-day price feeds for AVT token, ensuring consistent valuation timing
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation, with all transaction fees within each calendar day summed together
- **Final calculation**: The final revenue value equals the sum of all transaction fees (base amounts plus tips) for each day, converted to USD using the corresponding day's AVT token price from CoinGecko price feeds. A forward-fill strategy is applied to handle any missing days in the data series.

*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.

AventusAVT

Archived

Revenue

Revenue

Competitive landscape

Chain breakdown