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

Viction is a smart contract platform for decentralized applications (a blockchain). Viction was founded by Ninety Eight and launched in 2018.

VIC holders own and govern the protocol. They currently don't take a cut of the total transaction fees paid by users (revenue). Ninety Eight's investors include Binance Labs, The Spartan Group, Multicoin Capital, etc.

website

twitter

Blockchains (L1)

Viction

# Viction Average fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average amount of transaction fees paid per daily active user on the Viction blockchain. This metric helps assess user engagement value and network monetization efficiency by dividing total daily fees collected by the number of unique users transacting on the platform. The calculation uses Viction's native token (wVIC) for fee payments and converts all values to USD for standardized reporting.

## 2. Data sources

The AFPU calculation relies on several core data sources:

- **Viction blockchain transactions**: Complete transaction records from the Viction blockchain containing transaction hashes, sender and recipient addresses, gas usage amounts, gas prices, block timestamps, and block numbers
- **VRC21 token registry**: Registry of special VRC21 tokens on Viction that use fixed gas pricing instead of market-based gas prices
- **End-of-day price feeds**: Daily price data for wVIC token conversion to USD values for standardized reporting
- **Token metadata**: Information about the wrapped VIC token (wVIC) used as the primary fee token on Viction

## 3. Step-by-step calculation

### Component A: Transaction fee calculation
- **Purpose**: Calculate the total gas fees paid in wVIC tokens for each transaction
- **Logic**: For each Viction transaction, gas fees are calculated by multiplying `gas_used` by `effective_gas_price`. The effective gas price uses conditional logic: for transactions involving VRC21 tokens (identified by matching the `to_address` against the VRC21 token registry), a fixed rate of 2.5 × 10⁻¹⁰ wVIC per gas unit is applied. For regular transactions, the standard `gas_price` field is divided by 10¹⁸ to convert from wei to wVIC units. All transactions are associated with the wVIC token address and tagged with the Viction chain identifier.
- **Key fields**: `gas_used` (gas consumed per transaction), `gas_price` (market gas price in wei), `effective_gas_price` (calculated gas price in wVIC), `to_address` (transaction recipient for VRC21 detection)

### Component B: Daily fee aggregation and USD conversion
- **Purpose**: Sum all transaction fees by day and convert to USD values
- **Logic**: Transaction fees are grouped by day using timestamp truncation to daily boundaries. The daily fee totals are then converted to USD using end-of-day wVIC price feeds. The conversion process maintains proper decimal handling and applies the appropriate exchange rates for each day. Fees are classified under the 'blockchains_l1' market sector and 'blockchain' business segment, with the Viction chain identifier.
- **Key fields**: `gas_fee` (calculated fee per transaction), `timestamp` (daily truncated), `chain_id` (viction), `token_address` (wVIC address)

### Component C: Daily active user identification
- **Purpose**: Count unique users transacting daily on Viction using efficient probabilistic counting
- **Logic**: Users are identified as unique `from_address` values (transaction senders) from Viction transactions, truncated to daily time boundaries. The system uses HyperLogLog (HLL) data structures for efficient distinct counting of user addresses. Users are classified as 'Transaction sender' type within the 'blockchains_l1' market sector. The HLL approach allows for accurate distinct user counts while maintaining computational efficiency across large datasets.
- **Key fields**: `user_address` (from_address of transactions), `user_type` (always 'Transaction sender'), `user_dau` (distinct user identifier)

### Component D: Multi-dimensional user aggregation
- **Purpose**: Aggregate user counts across different analytical dimensions for comprehensive reporting
- **Logic**: The HLL user data is aggregated across four dimensions: project-level (overall totals), chain-level (Viction-specific), user-type-level (transaction sender breakdown), and product-level (currently null for Viction). Each dimension uses HLL merge operations to combine daily user sketches and extract final distinct counts. This creates a comprehensive view of user activity suitable for various analytical breakdowns.
- **Key fields**: `dimensions` (aggregation level), `chain_id`, `user_type`, `product_id`, `user_dau` (final count)

### Final aggregation
- **Combining components**: The AFPU calculation uses the `calculate_arpu` macro to divide the total daily fees (from Component B) by the daily active user count (from Component D). Both metrics are matched by date and combined to produce the daily AFPU values.
- **Currency conversion**: All fee values are converted to USD using end-of-day wVIC price feeds, ensuring consistent currency representation across the metric.
- **Time aggregation**: Both fees and user counts use daily time boundaries (timestamp truncation to day level) to ensure proper alignment and daily metric calculation.
- **Final calculation**: AFPU = Total Daily Fees (USD) ÷ Daily Active Users. The `finalize_metric_afpu` macro applies schema validation, fills missing days with zeros using the 'fill_zeros' strategy, and ensures data quality standards are met across the complete time series.

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

VictionVIC

Archived

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape