Validators process transactions and receive fees from users (supply-side fees). DA costs for users are reflected in the transactions fees paid.

Celestia is a proof of stake blockchain optimized for data availability (DA). Celestia was founded by Mustafa Al-Bassam, etc. and launched in 2023.

TIA holders own and govern the protocol. They currently do not take a cut of the total transaction fees paid by users (revenue). Celestia's investors include Polychain Capital, Placeholder, Coinbase Ventures, etc.

github

twitter

discord

website

Blockchains (L1)

Celestia

# Celestia Active addresses (daily) Methodology

## 1. Overview

Active addresses daily for Celestia measures the number of unique addresses that initiated transactions on the Celestia blockchain each day. This metric tracks daily user engagement by counting distinct transaction senders, providing insight into the network's user activity and adoption. The calculation uses HyperLogLog probabilistic counting to efficiently handle large-scale address deduplication across multiple dimensional breakdowns.

## 2. Data sources

- **Celestia blockchain message events**: Raw blockchain events from Celestia's message system containing transaction details and metadata
- **Event attributes**: JSON-formatted attributes within message events that contain sender address information
- **Incremental processing metadata**: Table modification timestamps used to optimize data processing for updated records

## 3. Step-by-step calculation

### Component A: User address extraction
- **Purpose**: Extract transaction sender addresses from Celestia blockchain message events
- **Logic**: Filter message events to only include those with event type 'message'. Parse JSON attributes using a JavaScript user-defined function to extract sender addresses from the event attribute arrays. Each message event represents a transaction with an associated sender address. Classify all extracted addresses as 'Transaction sender' user types within the 'blockchains_l1' market sector and 'blockchain' business segment.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for transaction identification, `event_attributes` JSON containing sender information, `user_address` as the extracted sender address

### Component B: Daily user preparation  
- **Purpose**: Prepare distinct daily user records for aggregation
- **Logic**: Take the extracted user addresses and truncate block timestamps to daily boundaries using day-level granularity. Create distinct records for each combination of day, chain, user type, market sector, business segment, product, and user address. This deduplication ensures each user address is counted only once per day regardless of how many transactions they initiated.
- **Key fields**: `timestamp` truncated to day, `timestamp_grain` set to 'day', `chain` identifier, `user_type`, `product_id`, `user_address` as the unique identifier

### Component C: HyperLogLog aggregation
- **Purpose**: Calculate distinct daily active users across multiple dimensional breakdowns using probabilistic counting
- **Logic**: Create HyperLogLog sketches for each day, chain, user type, and product combination to enable efficient distinct counting. Generate four separate dimensional aggregations: project-level totals (project_dbt_tag dimension), chain-level breakdowns, user type breakdowns, and product-level breakdowns. Use HLL merge operations to combine sketches within each dimension while maintaining cardinality accuracy. Extract final distinct counts from the merged HLL sketches.
- **Key fields**: `timestamp` and `timestamp_grain` for time boundaries, `dimensions` indicating breakdown type, `chain_id`, `product_id`, `user_type` for dimensional attributes, `user_dau` as the distinct user count

### Final aggregation
- **Combining components**: Select records from the HLL aggregation that have dimensions of 'chain' or 'project_dbt_tag' to focus on chain-level and total project-level active address counts
- **Terminology conversion**: Rename the `user_dau` field to `active_addresses_daily` to align with blockchain-specific terminology where users are referred to as active addresses
- **Time aggregation**: Data is aggregated to daily boundaries with complete time series coverage
- **Final calculation**: The final active addresses daily value represents the distinct count of addresses that initiated at least one transaction on Celestia blockchain for each day, calculated using HyperLogLog probabilistic counting and presented with zero-filling for missing days to ensure complete time series data

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

Unique active addresses over a fixed 24-hour window.

CelestiaTIA

Active addresses (daily)

Active addresses (daily)

Competitive landscape