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.

github

twitter

discord

etherscan

website

governance

Blockchains (L2)

Starknet

# Starknet Active users (daily) Methodology

## 1. Overview

Daily active users (DAU) measures the number of unique addresses that interact with the Starknet network on a given day. This metric counts distinct user addresses from both traditional transactions and account abstraction interactions, providing a comprehensive view of network activity. The calculation combines regular transaction participants with smart contract wallet users who interact through sponsored or externally executed transactions.

## 2. Data sources

The calculation uses the following raw data sources:
- **Starknet transaction records**: Complete transaction data including sender addresses, recipient addresses, transaction types, fees, and timestamps
- **Starknet execution traces**: Detailed execution traces that capture smart contract interactions, including entry point selectors and recipient addresses
- **Account abstraction patterns**: Predefined entry point selectors that identify specific smart contract wallet interaction types

## 3. Step-by-step calculation

### Component A: Transaction users
- **Purpose**: Identifies users who participate in regular Starknet transactions as either senders or recipients
- **Logic**: Extracts user addresses from Starknet transaction records by taking both `sender_address` and `to_address` fields. Each transaction contributes up to two user addresses (sender and recipient). Users are classified by their `transaction_type` which indicates the nature of their blockchain interaction
- **Key fields**: `sender_address` and `to_address` as user identifiers, `transaction_type` for user classification, `block_timestamp` for temporal grouping

### Component B: Account abstraction users  
- **Purpose**: Captures users who interact with Starknet through smart contract wallets and sponsored transactions
- **Logic**: Identifies users from Starknet execution traces by filtering for specific entry point selectors that indicate account abstraction patterns. The filtering includes five distinct entry point selectors: three variants of `execute_from_outside` and two variants of `execute_gas_sponsored`. These selectors identify smart contract wallet interactions where the `to_address` represents the user wallet being called via external or sponsored execution. Only traces from April 20, 2025 onwards are included
- **Key fields**: `to_address` as the user wallet identifier, `entry_point_selector` for filtering account abstraction patterns, `block_timestamp` for temporal grouping

### Final aggregation
- **Combining components**: Transaction users and account abstraction users are combined using a union operation, creating a comprehensive dataset of all user interactions
- **Time aggregation**: User addresses are grouped by day using timestamp truncation to daily boundaries, ensuring each user is counted once per day regardless of how many interactions they have
- **User type classification**: Users retain their classification as either their original `transaction_type` (for transaction users) or as `account_abstraction` (for trace users)
- **Final calculation**: The final DAU count represents the distinct number of user addresses active on each day, combining both traditional transaction participants and account abstraction users into a single comprehensive metric

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

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

StarknetSTRK

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown