website

github

Blockchains (L2)

Settlus

# Settlus Active addresses (daily) Methodology

## 1. Overview

Active addresses daily for Settlus measures the number of unique addresses that initiated at least one transaction on the Settlus blockchain within each 24-hour period. This metric provides insight into daily user engagement and network activity on the Settlus Layer 2 blockchain. The calculation identifies transaction senders as active addresses and counts distinct addresses per day using efficient HyperLogLog aggregation techniques.

## 2. Data sources

The methodology relies on the following raw data sources:
- **Settlus blockchain transactions**: Raw transaction records from the Settlus blockchain containing transaction metadata including sender addresses (`from_address`), transaction hashes, block timestamps, and other transaction details
- **Chain availability configuration**: Data availability periods for the Settlus chain used to filter results to periods with complete data coverage

## 3. Step-by-step calculation

### Component A: User identification
- **Purpose**: Extract and classify transaction senders as users from raw Settlus blockchain data
- **Logic**: Raw Settlus transaction records are processed to identify unique users. Each transaction's sender address (`from_address`) is extracted and classified with metadata including chain identifier ('settlus'), market sector ('blockchains_l2'), business segment ('blockchain'), and user type ('Transaction sender'). Block timestamps are converted to timestamp format for temporal analysis.
- **Key fields**: `block_timestamp` for timing, `from_address` for user identification, `transaction_hash` for transaction tracking, plus classification metadata fields

### Component B: Daily user aggregation
- **Purpose**: Calculate daily unique active users by aggregating transaction senders per day
- **Logic**: Block timestamps are truncated to day boundaries using day-level timestamp truncation. For each day, distinct user addresses are identified from all transactions that occurred within that 24-hour period. The aggregation uses 'day' as the timestamp grain and maintains user address as the primary identifier for uniqueness calculation.
- **Key fields**: `timestamp` (day-truncated), `timestamp_grain` (always 'day'), `user_address` for distinct counting, plus metadata fields for classification

### Component C: HyperLogLog aggregation across dimensions
- **Purpose**: Efficiently aggregate daily active users across multiple dimensional breakdowns using probabilistic counting
- **Logic**: Daily user data is processed using HyperLogLog sketches with precision parameter 15 to enable scalable distinct user counting. The aggregation creates multiple dimensional views: project-level aggregation ('project_dbt_tag') for overall Settlus metrics, chain-level breakdown ('chain') for chain-specific metrics, user type breakdown ('user_type') for different user classifications, and product breakdown ('product_id') for product-specific analysis. HyperLogLog sketches are merged across time periods and extracted to produce final distinct user counts.
- **Key fields**: `timestamp`, `timestamp_grain`, `dimensions` (breakdown type), `chain_id`, `product_id`, `user_type`, `user_dau` (distinct user count)

### Final aggregation
- **Combining components**: The active addresses daily metric is derived by selecting user DAU counts from the HyperLogLog aggregation, specifically filtering for 'chain' and 'project_dbt_tag' dimensions which represent the core active addresses metrics
- **Metric conversion**: The `user_dau` field is renamed to `active_addresses_daily` to reflect that transaction senders represent active blockchain addresses
- **Time aggregation**: Daily boundaries are maintained from the initial timestamp truncation, with each day representing a complete 24-hour period of blockchain activity
- **Data completeness**: Missing days are filled with zero values using the finalize metric macro to ensure continuous time series data, and chain availability filtering excludes periods with incomplete data coverage
- **Final calculation**: The final metric represents the count of distinct addresses that initiated at least one transaction on the Settlus blockchain within each daily period, calculated using HyperLogLog distinct counting for accuracy and performance

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

Unique active addresses over a fixed 24-hour window.

Settlus

Active addresses (daily)

Active addresses (daily)

Competitive landscape