# Starknet Active addresses (daily) Methodology

## 1. Overview

Active addresses daily measures the number of unique addresses that participated in any transaction on the Starknet network each day. This metric treats daily active users as active addresses in the blockchain context, providing insight into daily network participation and user engagement. The calculation identifies all addresses that either sent a transaction or received activity through transaction events, then uses HyperLogLog algorithms for efficient distinct counting across large datasets.

## 2. Data sources

- **Starknet transaction records**: Raw on-chain transaction data including sender addresses, transaction types, timestamps, and execution details
- **Transaction receipt events**: Event logs from transaction receipts containing recipient addresses and contract interaction details  
- **Transaction fee data**: Native fee amounts and fee units from transaction execution
- **Chain metadata**: Starknet network classification data (layer 2 blockchain, blockchain business segment)

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Standardize raw Starknet transaction data and extract key address information
- **Logic**: Extract transaction records from Starknet blockchain data, converting timestamps to daily boundaries using day truncation. Extract sender addresses directly from transaction data and derive recipient addresses from the first event in transaction receipts when available. Convert transaction fees from native units to ETH by dividing by 1e18. Classify all transactions with Starknet chain metadata and blockchain business segment identifiers.
- **Key fields**: `sender_address` (transaction initiator), `to_address` (derived from receipt events), `block_timestamp` (transaction execution time), `transaction_type` (classification of transaction), `actual_fee_amount` (converted fee in ETH)

### Component B: Daily active user identification  
- **Purpose**: Identify all unique addresses that participated in transactions each day
- **Logic**: For each transaction, combine sender and recipient addresses using coalesce logic to capture both transaction initiators and receivers. Truncate block timestamps to day boundaries to create daily groupings. Create distinct address lists per day, treating each unique address that appears in any transaction (either as sender or recipient) as an active user for that day. Include transaction type as user classification.
- **Key fields**: `user_dau` (distinct daily address), `timestamp` (daily boundary), `user_type` (transaction type classification), `chain` (network identifier)

### Component C: HyperLogLog aggregation
- **Purpose**: Efficiently aggregate distinct address counts across multiple dimensions using probabilistic counting
- **Logic**: Create HyperLogLog sketches for each daily address list using precision level 15 for high accuracy. Generate aggregations across four dimensions: project-level (overall Starknet), chain-level (Starknet network), user type (transaction classification), and product-level breakdowns. Use HyperLogLog merge operations to combine sketches and extract final distinct counts. Apply zero-filling strategy for missing days to ensure continuous time series data.
- **Key fields**: `hll` (HyperLogLog sketch), `user_dau` (extracted distinct count), `dimensions` (aggregation level), `timestamp_grain` (day-level granularity)

### Final aggregation
- **Combining components**: Select the aggregated user DAU counts from the HyperLogLog component and rename to active addresses daily, focusing specifically on chain-level and project-level dimensions while excluding user type and product breakdowns
- **Currency conversion**: No currency conversion required as this is a count metric, though underlying transaction fees are converted to ETH for consistency
- **Time aggregation**: Daily boundaries determined by truncating block timestamps to day level, with missing days filled with zero values to maintain continuous time series
- **Final calculation**: The final active addresses daily value represents the distinct count of unique addresses that participated in any Starknet transaction on a given day, calculated using HyperLogLog probabilistic counting for scalability and accuracy

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

Unique active addresses over a fixed 24-hour window.

Active addresses (daily)

Starknet

Starknet is a Validity-Rollup (ZK-Rollup) Layer 2 network that operates on top of Ethereum, enabling dApps to massively scale without compromising on security. It achieves this by bundling transactions into an off-chain computed STARK proof. This proof is then submitted to Ethereum as a single transaction, resulting in significantly higher throughput, faster processing times, and much lower costs, all while retaining the robust security of the Ethereum settlement layer.

Starknet aims to be governed by a decentralized, community-driven process centered around STRK token holders. While StarkWare originally developed the technology, the network is transitioning to a completely decentralized model where the broader community makes decisions regarding protocol upgrades, development, and the future of the network.

Starknet is a Layer 2 that uses STARK technology to validate off-chain transactions, enabling unlimited scale while preserving Ethereum's security and decentralization.

StarknetSTRK

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown