website

twitter

github

Blockchains (L2)

Invarch

# Invarch Active users (daily) Methodology

## 1. Overview

Daily active users (DAU) for Invarch measures the number of distinct addresses that performed any transaction on the Invarch network each day. This metric combines activity from both the native Substrate layer and the EVM compatibility layer to provide a comprehensive view of user engagement across Invarch's dual-chain architecture.

## 2. Data sources

The calculation uses two primary blockchain data sources:
- **Native Invarch extrinsics**: Substrate-based transaction records containing user addresses and transaction metadata
- **Invarch EVM events**: Event logs from the EVM compatibility layer, specifically filtered for execution events that indicate user activity

## 3. Step-by-step calculation

### Component A: User identification from native transactions
- **Purpose**: Identifies users from native Substrate transactions on Invarch
- **Logic**: Extracts user addresses from Invarch extrinsics data where users are classified as transaction senders. The `id` field contains the user address for each extrinsic. All records are tagged with 'invarch' as the chain identifier and classified as 'Transaction sender' user type
- **Key fields**: `block_timestamp` for timing, `id` as user address, transaction metadata for classification

### Component B: User identification from EVM events  
- **Purpose**: Identifies users from EVM-compatible transactions on Invarch
- **Logic**: Extracts user addresses from Invarch event logs, specifically filtering for events where `event_pallet` equals 'evm' and `event_method` equals 'Executed'. User addresses are parsed from the first element of the `event_data` array using JSON extraction. These records are tagged with 'invarchevm' as the chain identifier
- **Key fields**: `block_timestamp` for timing, `event_data[0]` as user address source, `event_pallet` and `event_method` for filtering

### Final aggregation
- **Combining components**: The two user identification components are combined using a union operation to create a unified view of all user activity across both Substrate and EVM layers
- **Time aggregation**: Block timestamps are truncated to daily boundaries using day-level granularity, creating discrete 24-hour periods for user counting
- **Deduplication**: Within each day, distinct user addresses are selected to ensure each unique address is counted only once regardless of transaction volume
- **Final calculation**: The daily active user count represents the number of unique addresses that performed at least one transaction on either the native Substrate layer or EVM compatibility layer of Invarch on each given day

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

Unique revenue-generating users over a fixed 24-hour window.

Invarch

Archived

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown