Name: Ink Active users (daily) Metrics
Creator: Token Terminal
License: https://tokenterminal.com/terms

Ink batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Ink is an Ethereum Layer 2 (L2) blockchain built on Optimism's Superchain, focused on providing a secure, scalable infrastructure for Web3 applications.

Kraken team owns and governs the protocol. Kraken's investors include RIT Capital Partners, Hummingbird Ventures, Money Partners Group, etc.

github

website

twitter

discord

Blockchains (L2)

# Ink Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) measures the number of unique addresses that initiated at least one transaction on the Ink blockchain within a given day. This metric provides insight into user engagement and network adoption by tracking distinct transaction senders on a daily basis. The calculation identifies unique wallet addresses that have sent transactions, providing a proxy for active user behavior on the Ink network.

## 2. Data sources

- **Ink blockchain transaction records**: Complete transaction data from the Ink blockchain including block timestamps, transaction hashes, and sender addresses
- **Transaction metadata**: Block-level timing information used to determine daily boundaries and transaction occurrence

## 3. Step-by-step calculation

### Component A: User identification
- **Purpose**: Extract and classify all transaction senders as active users from raw blockchain data
- **Logic**: Retrieve all transaction records from Ink blockchain transaction data, extracting the sender address (`from_address`) from each transaction along with the block timestamp and transaction hash. Each transaction sender is classified as a "Transaction sender" user type and assigned to the blockchain business segment under the layer 2 blockchain market sector. The `product_id` is set to null as this metric tracks general blockchain usage rather than specific product interaction.
- **Key fields**: `block_timestamp` for timing, `from_address` for user identification, `transaction_hash` for transaction reference, static classification fields for categorization

### Component B: Daily aggregation  
- **Purpose**: Group users by day and count distinct active addresses
- **Logic**: Truncate block timestamps to day granularity using day-level time boundaries, ensuring each transaction is assigned to the correct calendar day. Group all transactions by the truncated timestamp and apply distinct count logic to the user addresses, ensuring each unique address is counted only once per day regardless of how many transactions they sent. Include metadata fields for chain identification, timestamp grain specification, user type classification, and business categorization.
- **Key fields**: `timestamp` (truncated to day), `user_address` (for distinct counting), `chain`, `user_type`, classification metadata

### Final aggregation
- **Combining components**: The final metric combines the user identification and daily aggregation by selecting distinct user addresses per day from the processed transaction data
- **Currency conversion**: Not applicable - this is a count-based metric measuring user addresses rather than monetary values  
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day granularity, ensuring consistent daily reporting periods
- **Final calculation**: The final DAU value represents the count of distinct user addresses that sent at least one transaction on each given day, filtered by chain availability to ensure data quality and completeness

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