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

Injective is a smart contract platform for decentralized finance applications (a blockchain) and an orderbook exchange protocol. Injective was founded by Eric Chen, Albert Chon etc. and launched in 2020. Note that this dashboard only tracks Injective's blockchain business.

INJ holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue) via Burn Auctions. Injective's investors include Binance, Jump Crypto, Mark Cuban, etc.

github

twitter

discord

website

Blockchains (L1)

Injective

# Injective Active users (daily) Methodology

## 1. Overview

Daily active users (DAU) for Injective measures the number of unique addresses that initiated at least one transaction on either the Injective Cosmos blockchain or Injective EVM blockchain within a 24-hour period. This metric captures user engagement across Injective's dual blockchain architecture, providing insights into platform adoption and usage patterns. The calculation uses probabilistic counting techniques to efficiently aggregate unique users across multiple dimensional breakdowns while handling the scale and complexity of blockchain transaction data.

## 2. Data sources

The metric relies on the following raw blockchain data sources:

- **Injective Cosmos message events**: Blockchain transaction message events containing sender information extracted from event attributes, representing user activity on the Cosmos-based Injective chain
- **Injective EVM transaction records**: Complete transaction records from the Ethereum Virtual Machine compatible Injective chain, including sender addresses (`from_address` field)
- **Chain availability configuration**: System configuration data that determines which chains and time periods should be included in the final metrics based on data quality and completeness criteria

## 3. Step-by-step calculation

### Component A: Injective EVM user extraction
- **Purpose**: Identifies unique daily active users from the Injective EVM blockchain
- **Logic**: Extracts all transaction records from Injective EVM blockchain data and identifies the `from_address` field as the transaction sender. Each transaction sender represents an active user. Data is truncated to daily boundaries using timestamp truncation, and each unique address per day is counted as a daily active user. Users are classified as "Transaction sender" type and attributed to the "Injective EVM" product and chain.
- **Key fields**: `block_timestamp` for daily boundary determination, `from_address` as the user identifier, `transaction_hash` for transaction tracking

### Component B: Injective Cosmos user extraction  
- **Purpose**: Identifies unique daily active users from the Injective Cosmos blockchain
- **Logic**: Processes message events from Injective Cosmos blockchain where `event_type` equals "message". Extracts the sender address from the `event_attributes` JSON field using the "sender" key. Each message sender represents an active user. Data is truncated to daily boundaries, and each unique sender address per day is counted as a daily active user. Users are classified as "Transaction sender" type and attributed to the "Injective Cosmos" product and "injective" chain.
- **Key fields**: `block_timestamp` for daily boundary determination, `event_attributes` JSON containing sender information, `transaction_hash` for transaction tracking

### Component C: User combination and deduplication
- **Purpose**: Combines users from both Injective blockchain architectures while maintaining chain attribution
- **Logic**: Merges Injective EVM and Injective Cosmos users using union operations, preserving the distinct chain identifiers and product attributions. Each user record maintains its original chain context ("Injective EVM" or "injective" for Cosmos), user type classification, and product identification. The combination process maintains the daily timestamp boundaries and applies incremental processing filters for efficiency.
- **Key fields**: Combined `user_dau` field (representing user addresses), `chain` identifier, `product_id`, `user_type`, daily `timestamp`

### Component D: HyperLogLog aggregation initialization
- **Purpose**: Prepares user data for efficient probabilistic unique counting across multiple dimensions
- **Logic**: Initializes HyperLogLog (HLL) data structures for each combination of timestamp, chain, user type, and product. The HLL initialization uses a precision parameter of 15 bits, providing high accuracy for unique counting while maintaining computational efficiency. This step groups the combined user data by all relevant dimensions and creates HLL sketches that can be efficiently merged and aggregated.
- **Key fields**: `hll` sketches initialized from `user_dau` addresses, dimensional grouping fields (`timestamp`, `chain`, `user_type`, `product_id`)

### Component E: Multi-dimensional DAU breakdowns
- **Purpose**: Creates separate DAU aggregations for different analytical perspectives
- **Logic**: Generates four distinct dimensional views of daily active users: 1) Project-level DAU aggregating all users regardless of chain or user type, 2) Chain-level DAU broken down by blockchain (Injective EVM vs Injective Cosmos), 3) User-type-level DAU (currently all "Transaction sender" but allows for future expansion), 4) Product-level DAU broken down by specific products. Each breakdown merges the appropriate HLL sketches and extracts the final unique count using `hll_count.extract` and `hll_count.merge_partial` functions.
- **Key fields**: `dimensions` field indicating breakdown type, `chain_id`, `product_id`, `user_type` for dimensional attribution, `user_dau` containing the final unique user count

### Final aggregation
- **Combining components**: All dimensional breakdowns are combined using union operations to create a comprehensive view that supports multiple analytical perspectives in a single dataset
- **Currency conversion**: Not applicable for user count metrics
- **Time aggregation**: Daily boundaries are maintained throughout the calculation, with timestamp truncation ensuring consistent 24-hour periods aligned to UTC day boundaries
- **Final calculation**: The final DAU value represents the unique count of addresses that initiated transactions on either Injective blockchain within each day, calculated using probabilistic HyperLogLog counting for computational efficiency and scalability. Missing days are filled with zeros to ensure complete time series continuity.

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

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

InjectiveINJ

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown