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

Fraxtal is an Ethereum Layer 2 (L2) blockchain built on the OP Stack by Frax Finance. It uses frxETH as the gas token and features a blockspace incentive system called Flox. Fraxtal launched in February 2024.

Frax Finance team owns and governs the protocol. Frax Finance's investors include Dragonfly Capital, Mechanism Capital, Galaxy Digital, etc.

twitter

discord

etherscan

website

Blockchains (L2)

Fraxtal

# Fraxtal Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Fraxtal measures the number of unique addresses that initiated at least one transaction on the Fraxtal blockchain each day. This metric provides insight into user engagement and adoption by tracking unique transaction senders, which represents the most basic form of blockchain activity. The calculation uses HyperLogLog sketches to enable efficient aggregation across multiple dimensional breakdowns while maintaining accuracy for large-scale distinct counting.

## 2. Data sources

- **Fraxtal blockchain transaction records**: Raw transaction data from the Fraxtal Layer 2 blockchain, containing transaction metadata including sender addresses, timestamps, and transaction hashes
- **Chain availability metadata**: Data availability windows and operational status information used to filter results based on when reliable data collection was active

## 3. Step-by-step calculation

### Component A: User identification
- **Purpose**: Identifies active users from transaction activity on Fraxtal
- **Logic**: Extracts transaction sender addresses from Fraxtal blockchain transaction records. Each transaction's `from_address` field represents a user who initiated blockchain activity. All identified users are classified as "Transaction sender" type since they represent addresses that actively sent transactions. The component also assigns metadata including chain identifier (fraxtal), market sector (blockchains_l2), and business segment (blockchain)
- **Key fields**: `block_timestamp` for timing, `from_address` as the user identifier, `transaction_hash` for transaction tracking, and `user_type` set to "Transaction sender"

### Component B: Daily user aggregation
- **Purpose**: Calculates daily distinct active user counts
- **Logic**: Groups transaction activity by day using daily timestamp truncation of the `block_timestamp` field. For each day, counts distinct user addresses who sent at least one transaction. Users are deduplicated within each day to ensure each unique address is counted only once, regardless of how many transactions they sent. The timestamp grain is set to "day" to indicate daily aggregation
- **Key fields**: `timestamp` truncated to daily boundaries, `user_address` for distinct counting, `timestamp_grain` indicating daily aggregation level

### Component C: HyperLogLog sketch generation
- **Purpose**: Converts daily user counts into probabilistic data structures for efficient aggregation
- **Logic**: Transforms daily distinct user counts into HyperLogLog sketches using 15-bit precision. This enables efficient merging and distinct counting across different dimensional breakdowns without losing accuracy. Each daily user count becomes an HLL sketch that can be combined with other sketches to calculate distinct counts across larger time periods or different grouping dimensions
- **Key fields**: `hll` sketches generated from `user_dau` using `hll_count.init` with 15-bit precision

### Final aggregation
- **Combining components**: Creates four separate dimensional views of the same underlying DAU data: project-level aggregation (combining all dimensions), chain-level breakdown, user type breakdown, and product ID breakdown. Each breakdown uses HLL sketch merging to calculate distinct user counts while maintaining null values for non-applicable dimensions
- **Currency conversion**: Not applicable - this is a user count metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation to day granularity, with incremental processing looking back additional days for data completeness
- **Final calculation**: The final DAU value is extracted from merged HLL sketches using `hll_count.extract(hll_count.merge_partial(hll))`, which provides the distinct count of users for each dimensional combination. Missing days are filled with zero values to ensure complete time series data

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

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

FraxtalFXTL

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown