website

twitter

github

Blockchains (L2)

Aventus

# Aventus Fees Methodology

## 1. Overview

The Aventus fees metric measures the total transaction fees paid by users on the Aventus blockchain on a daily basis, expressed in USD. This metric captures the total cost that users pay to execute transactions on the network, including both base fees and tips. The calculation aggregates all successful transaction fees from the Aventus blockchain and converts them to USD using end-of-day price feeds.

## 2. Data sources

- **Aventus blockchain events**: Parsed `TransactionFeePaid` events from the Aventus blockchain containing fee amount and tip data
- **Transaction metadata**: Aventus blockchain transaction records including timestamps, block numbers, and transaction success status
- **External price data**: End-of-day Aventus token price feeds from CoinGecko API using the 'aventus' token identifier

## 3. Step-by-step calculation

### Component A: Raw fee extraction
- **Purpose**: Extract and process individual transaction fee payments from Aventus blockchain events
- **Logic**: Query `TransactionFeePaid` events from Aventus blockchain event logs, filtering only for successful transactions. Parse the event data structure to extract two fee components: the base `amount` (first data field) and the `tip` (second data field). Convert both amounts from wei precision (18 decimals) to standard token units by dividing by 1e18. Include transaction metadata such as block timestamp, block number, extrinsic hash, and event index for traceability.
- **Key fields**: `amount` (base transaction fee), `tip` (additional tip amount), `block_timestamp` (transaction time), `success` (transaction status filter)

### Component B: Daily fee aggregation  
- **Purpose**: Aggregate individual transaction fees into daily totals in native Aventus tokens
- **Logic**: Group all fee transactions by day using timestamp truncation to day boundaries. Calculate total daily fees by summing both the `amount` and `tip` components for each transaction within each day. Assign consistent metadata including chain identifier as 'aventus' and product identifier as 'aventuschain' with daily timestamp grain.
- **Key fields**: `fees` (sum of amount plus tip), `timestamp` (daily boundary), `chain_id` ('aventus'), `product_id` ('aventuschain')

### Component C: USD conversion
- **Purpose**: Convert native Aventus token amounts to USD values using market prices
- **Logic**: Apply USD conversion using CoinGecko price feeds for the Aventus token (identifier 'aventus'). Match daily fee amounts with corresponding daily token prices to calculate USD equivalent values. Maintain all dimensional data including timestamp grain, chain identifier, and product identifier through the conversion process.
- **Key fields**: `fees` (USD-converted daily fee total), price data from CoinGecko API

### Final aggregation
- **Combining components**: The components flow sequentially - raw fee extraction provides transaction-level data, daily aggregation sums to daily totals, and USD conversion applies market pricing
- **Currency conversion**: USD conversion uses CoinGecko's Aventus token price feeds, applying daily prices to daily fee totals
- **Time aggregation**: Fees are aggregated using daily boundaries determined by timestamp truncation to day level
- **Final calculation**: The final metric value represents the total USD value of transaction fees (base amount plus tips) paid on the Aventus blockchain for each day, with forward-fill applied to handle any gaps in daily data

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

Total value users pay to use a protocol (gross fees, user-paid fees).

AventusAVT

Archived

Fees

Fees

Competitive landscape

Chain breakdown