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 Active addresses (daily) Methodology

## 1. Overview

The Viction active addresses daily metric measures the number of unique addresses that initiated at least one transaction on the Viction blockchain each day. This metric serves as a key indicator of network activity and user engagement, tracking how many distinct addresses are actively sending transactions rather than just receiving them. The calculation treats each transaction sender address as an active address, providing insights into the daily usage patterns of the Viction network.

## 2. Data sources

- **Viction transaction data**: Raw transaction records from the Viction blockchain containing sender addresses, timestamps, and transaction hashes
- **Chain availability configuration**: Metadata defining periods when Viction data is considered reliable and complete for metric calculation

## 3. Step-by-step calculation

### Component A: User data extraction
- **Purpose**: Extracts and standardizes user activity data from raw Viction transactions
- **Logic**: Processes raw Viction transaction data to identify transaction senders. Each transaction record provides the sender address (`from_address`), block timestamp, and transaction hash. All senders are classified as "Transaction sender" user type, representing addresses that actively initiated transactions. The component also applies standard categorization, classifying Viction as a layer-1 blockchain in the blockchains market sector.
- **Key fields**: `block_timestamp` for timing, `from_address` as the user address, `transaction_hash` for transaction identification, and `user_type` set to "Transaction sender"

### Component B: Daily active user calculation  
- **Purpose**: Aggregates unique sender addresses by day to calculate daily active users
- **Logic**: Groups transaction data by day using timestamp truncation and identifies distinct sender addresses within each day. This creates a daily snapshot of unique addresses that sent at least one transaction. The calculation treats each unique sender address per day as one active user, regardless of how many transactions they sent.
- **Key fields**: `timestamp` truncated to day level, `user_address` representing the unique sender address, and dimensional categorization fields

### Component C: HyperLogLog aggregation
- **Purpose**: Efficiently aggregates unique user counts across multiple dimensions using probabilistic counting
- **Logic**: Applies HyperLogLog (HLL) algorithm to enable scalable distinct counting across different breakdowns. Creates HLL sketches for each day and dimension combination, then merges and extracts counts for various groupings including project-level (project_dbt_tag), chain-level, user-type-level, and product-level breakdowns. This approach allows for efficient handling of large datasets while maintaining accuracy for distinct counting operations.
- **Key fields**: `hll` structures for probabilistic counting, `dimensions` indicating the breakdown type, and `user_dau` containing the final extracted counts

### Component D: Active addresses mapping
- **Purpose**: Maps user DAU metrics to active addresses daily format
- **Logic**: Selects specifically the chain-level and project-level dimensional breakdowns from the user DAU aggregations, as these represent the relevant perspectives for active addresses reporting. Directly maps the `user_dau` field to `active_addresses_daily` since for blockchains, the concept of active users (unique transaction senders) is equivalent to active addresses.
- **Key fields**: `user_dau` renamed to `active_addresses_daily`, `dimensions` filtered to 'chain' and 'project_dbt_tag' only

### Final aggregation
- **Combining components**: The user DAU counts from the HyperLogLog aggregation are directly used as active addresses daily values, with no additional mathematical operations required
- **Currency conversion**: Not applicable for this address-counting metric
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level, ensuring each day represents a complete 24-hour period
- **Final calculation**: The final metric value represents the count of unique addresses that sent at least one transaction on the Viction blockchain during each calendar day, with missing days filled with zero values to maintain continuous time series and filtered to exclude periods when chain data availability is unreliable

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

Unique active addresses over a fixed 24-hour window.

VictionVIC

Archived

Active addresses (daily)

Active addresses (daily)

Competitive landscape