website

twitter

discord

github

Blockchains (L1)

Sonic

# Sonic Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Sonic measures the count of unique addresses that initiated at least one transaction on the Sonic blockchain each day. This metric answers the question: "How many distinct users are actively using the Sonic blockchain daily?" The calculation identifies active users by tracking transaction senders, with each unique address that sends a transaction on a given day counted once toward that day's DAU total.

## 2. Data sources

The metric relies on raw Sonic blockchain transaction data containing:
- **Sonic transaction records**: Complete transaction logs from the Sonic blockchain including sender addresses, transaction hashes, and block timestamps
- **Block timestamp data**: Timing information for when each transaction was included in a block on the Sonic blockchain
- **Transaction metadata**: Basic transaction details used to identify unique user activity

## 3. Step-by-step calculation

### Component A: User activity identification
- **Purpose**: Extract and classify all user activity from Sonic blockchain transactions
- **Logic**: Pull all transaction records from Sonic blockchain data, extracting the sender address (`from_address`), transaction hash, and block timestamp for each transaction. Each transaction sender is classified as a "Transaction sender" user type and categorized under the "blockchains_l1" market sector and "blockchain" business segment. This creates a comprehensive record of all user activity on the Sonic blockchain.
- **Key fields**: `block_timestamp` for timing, `from_address` as the user identifier, `transaction_hash` for transaction reference, and standardized classification fields

### Component B: Daily user aggregation  
- **Purpose**: Count unique active users per day
- **Logic**: Group all user activity by daily time boundaries using timestamp truncation to day granularity. For each day, identify all distinct user addresses that initiated transactions, ensuring each unique address is counted only once per day regardless of how many transactions they sent. Apply incremental processing logic to only recalculate recent days during updates, using a configurable lookback period.
- **Key fields**: `timestamp` truncated to day level, `user_address` for deduplication, `user_dau` as the final user identifier

### Final aggregation
- **Combining components**: The processed user activity data flows directly into the daily aggregation without additional joins, as both components operate on the same underlying transaction dataset
- **Currency conversion**: Not applicable - this metric counts users rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day granularity, ensuring consistent daily reporting periods aligned with blockchain block timing
- **Final calculation**: The final DAU value represents the count of distinct user addresses that sent at least one transaction on the Sonic blockchain for each specific day, with chain availability filters applied to ensure data quality and completeness

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

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

SonicS

Archived

Active users (daily)

Active users (daily)

Competitive landscape