Creators create and sell NFTs on Zora. They receive a cut of the primary sales (supply-side fees).

Zora is a non-custodial NFT minting protocol built on Ethereum and launched in 2021.

Team and investors own and govern the protocol. They currently take a cut the primary sales paid by collectors (revenue).

github

twitter

discord

website

NFT marketplaces

Zora

# Zora Active addresses (daily) Methodology

## 1. Overview

The Zora active addresses daily metric counts the number of unique wallet addresses that interact with the Zora NFT marketplace platform on a given day. This metric captures both NFT buyers (minters) and NFT drop creators across Ethereum, Optimism, and Base chains. The calculation identifies unique users through their on-chain interactions with Zora's smart contracts, providing insight into daily platform engagement and user activity levels.

## 2. Data sources

The calculation uses parsed Zora V1 protocol events from three blockchain networks:
- **Zora 721Drop Sale events**: Captures NFT minting transactions from Ethereum, Optimism, and Base
- **Zora Factory721 CreatedDrop events**: Records new NFT drop creation events across all three chains  
- **Zora 1155 Purchased events**: Tracks ERC-1155 token purchases on Ethereum, Optimism, and Base
- **Zora Factory1155/Creator1155Factory SetupNewContract events**: Documents new ERC-1155 contract deployments across chains

These events are sourced from parsed blockchain event logs that extract specific Zora protocol interactions from the underlying transaction data.

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Identifies and classifies all user interactions with Zora protocol contracts
- **Logic**: Extracts user addresses from four types of Zora events across Ethereum, Optimism, and Base chains. For Sale and Purchased events, the `to` and `sender` parameters identify minters (buyers). For CreatedDrop and SetupNewContract events, the `creator` parameter identifies drop creators. Each interaction is timestamped using the `block_timestamp` and labeled with the appropriate chain and user type classification.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for deduplication, `user_address` containing the wallet address, `user_type` indicating 'Minter' or 'Drop Creator', and `chain` specifying the blockchain network

### Component B: Daily user aggregation  
- **Purpose**: Aggregates unique users per day while preserving dimensional breakdowns
- **Logic**: Truncates timestamps to daily boundaries using day-level time truncation. Selects distinct user addresses within each day to eliminate duplicate interactions by the same user. Preserves user type classifications and chain information for downstream dimensional analysis.
- **Key fields**: `timestamp` truncated to day level, `user_address` as the unique identifier, `user_type` for classification, `chain` for network identification

### Component C: HyperLogLog sketching and dimensional aggregation
- **Purpose**: Enables accurate distinct user counting across multiple dimensional breakdowns using probabilistic data structures
- **Logic**: Applies HyperLogLog initialization to user addresses for efficient distinct counting. Creates four dimensional breakdowns: project-level (all chains combined), chain-level (per blockchain network), user-type-level (minters vs creators), and product-level (currently null for Zora). Uses HyperLogLog merge operations to combine sketches and extract final distinct counts for each dimension.
- **Key fields**: `hll` containing the HyperLogLog sketch data, `dimensions` indicating the breakdown type, `chain_id` for chain-specific aggregations, `user_type` for user classification breakdowns, `user_dau` containing the final distinct user count

### Final aggregation
- **Combining components**: Filters the dimensional aggregations to include only 'chain' and 'project_dbt_tag' dimension types, which provide chain-level and project-level active address counts
- **Currency conversion**: Not applicable for this address counting metric  
- **Time aggregation**: Uses daily time boundaries with day-level timestamp truncation
- **Final calculation**: Renames the `user_dau` field to `active_addresses_daily` to align with the target metric schema. Applies schema finalization using the `finalize_metric_active_addresses_daily` macro which standardizes the output format and fills missing days with zero values 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.

ZoraZORA

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown