website

twitter

github

Blockchains (L2)

Aventus

# Aventus Token holders Methodology

## 1. Overview

The Token holders metric is used to measure the number of unique addresses holding a non-zero balance of the native asset on Aventus. This metric provides insights into asset distribution and adoption by measuring how many distinct wallet addresses maintain active accounts. Active accounts are monitored on-chain through account creation and termination events to maintain a running count of unique addresses with non-zero balances.

## 2. Data sources

- **Blockchain events**: `NewAccount` and `KilledAccount` events from the Aventus network, covering Aventus

## 3. Step-by-step calculation

### Component A: Account change tracking

- **Purpose**: Track daily net changes in active accounts on the network
- **Logic**: `NewAccount` and `KilledAccount` events are extracted from the Aventus network events. A daily net change is calculated by assigning a value of `1` to `NewAccount` events (representing account creation) and `-1` to `KilledAccount` events (representing account termination), which are then summed for each day.
- **Key fields**: `block_timestamp` (timing), `event_method` (event type identification)

### Component B: Cumulative tokenholder calculation

- **Purpose**: Calculate the running total of unique tokenholders
- **Logic**: The daily net changes are aggregated cumulatively over time to determine the total number of active accounts for each day. A fill-forward method is applied to ensure continuous daily data, and only days with a tokenholder count greater than zero are retained.
- **Key fields**: `timestamp` (timing), `tokenholders` (cumulative count of active accounts)

### Component C: Metric standardization

- **Purpose**: Format the tokenholder data to align with Token Terminal's schema
- **Logic**: The tokenholder count is cast to a high-precision numeric format to prevent precision loss. Standardized metadata, including the project identifier and chain identifier, is applied, and a chain availability filter is enforced to ensure data validity.
- **Key fields**: `timestamp` (timing), `timestamp_grain` (aggregation granularity), `chain_id` (network identification), `tokenholders` (standardized count)

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

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

AventusAVT

Archived

Token holders

Token holders

Competitive landscape

Chain breakdown