Honeypop is an AMM and concentrated liquidity layer on Scroll, built for efficient swaps and real yield. It will also feature a Morpho-powered money market, enabling seamless lending and borrowing.

twitter

website

Exchanges (DEX)

Honeypop

# Honeypop Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Honeypop measures the count of unique user addresses that performed trading or flash loan activities on the Honeypop DEX protocol on any given day. This metric captures user engagement by identifying distinct addresses that initiated either swap transactions or flash loan operations on Honeypop's automated market maker pools. The metric provides a comprehensive view of active participation by combining both traditional trading activity and more advanced DeFi operations like flash loans into a single user activity measure.

## 2. Data sources

The metric relies on the following raw data sources:
- **Blockchain event logs**: Parsed `Pool_Flash_event` logs from Honeypop v1 smart contracts on Scroll blockchain, capturing flash loan operations with sender addresses and token amounts
- **Blockchain event logs**: Parsed `Pool_Swap_event` logs from Honeypop v1 smart contracts on Scroll blockchain, capturing trading activities with user addresses and token swap amounts
- **Transaction data**: Scroll blockchain transaction records containing transaction hashes and originating user addresses (`from_address`) that link contract interactions to actual users
- **Data quality filters**: Configuration for denylisted trading pairs to exclude pools with limited price feed support for low liquidity tokens (currently empty but available for future use)

## 3. Step-by-step calculation

### Component A: Flash loan user extraction
- **Purpose**: Identifies users who performed flash loan operations on Honeypop pools
- **Logic**: Extracts `Pool_Flash_event` logs from Honeypop v1 contracts on Scroll blockchain, capturing flash loan activities. Each event contains the contract interaction (`sender` address) and token amounts (`amount0` and `amount1`). The system joins these events with Scroll transaction records using `transaction_hash` to map contract interactions back to the actual user addresses that initiated the transactions. Events from denylisted trading pairs are excluded for data quality purposes
- **Key fields**: `block_timestamp` for timing, `sender` for contract user, `from_address` from transactions as the actual `user_address`, `amount0` and `amount1` for flash loan token quantities

### Component B: Trading user extraction  
- **Purpose**: Identifies users who performed trading activities on Honeypop pools
- **Logic**: Extracts `Pool_Swap_event` logs from Honeypop v1 contracts on Scroll blockchain, capturing swap transactions. Each event contains the trading interaction (`sender` address) and token amounts (`amount0` and `amount1`). Similar to flash loans, the system joins these events with Scroll transaction records to map contract interactions to actual user addresses. Trading pairs that appear in the denylisted configuration are excluded from the analysis
- **Key fields**: `block_timestamp` for timing, `sender` for contract user, `from_address` from transactions as the actual `user_address`, `amount0` and `amount1` for swap token quantities

### Final aggregation
- **Combining components**: Flash loan users and trading users are combined using a union operation that automatically removes duplicate user addresses appearing in both datasets on the same day. This ensures users who perform both activities are counted only once per day
- **Currency conversion**: Not applicable - this metric counts unique addresses rather than monetary values
- **Time aggregation**: Timestamps are truncated to daily boundaries using day-level granularity, grouping all activities within a 24-hour period. The metric uses incremental processing with a 29-day lookback window to ensure data completeness and handle any late-arriving blockchain data
- **Final calculation**: The result provides one record per unique user address per day, with each user classified as 'Trader' type regardless of whether they performed swaps, flash loans, or both activities. Chain availability filtering is applied to ensure only days with complete data coverage are included in the final metric

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

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

Honeypop

Active users (daily)

Active users (daily)

Competitive landscape