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 Average trading volume (per trade) Methodology

## 1. Overview

The trading volume average per trade count metric measures the mean USD value per trade on the Honeypop decentralized exchange. This metric is calculated by dividing the total daily trading volume in USD by the number of distinct trades executed that day. It provides insight into the typical trade size and trading patterns on the Honeypop platform, helping assess market depth and user behavior.

## 2. Data sources

The calculation relies on several key data sources:

- **Blockchain events**: Parsed Honeypop v1 `Pool_Swap_event` logs from Scroll blockchain containing trade execution data including token amounts and pool addresses
- **Trading pair definitions**: Parsed Honeypop v1 `Factory_PoolCreated_event` logs from Scroll blockchain defining valid trading pairs with token addresses, fee tiers, and pool configurations
- **Transaction data**: Scroll transaction records providing user addresses and transaction metadata
- **External data**: End-of-day token price feeds for USD conversion and token metadata including decimal precision and symbols for proper amount conversion
- **Configuration data**: Denylist of trading pairs (currently empty) to exclude pairs with limited price feed support

## 3. Step-by-step calculation

### Component A: Trade event extraction
- **Purpose**: Captures all swap transactions on Honeypop v1 pools
- **Logic**: Extracts `Pool_Swap_event` logs from Scroll blockchain for Honeypop v1 contracts. Each event contains the pool address, token amounts (`amount0` and `amount1`), sender address, and transaction details. Events are filtered to exclude any denylisted trading pairs, though the current denylist is empty. The process joins with Scroll transaction data to obtain the actual user addresses from transaction `from_address` fields.
- **Key fields**: Pool `address`, token amounts (`amount0`, `amount1`), `sender` address, transaction `hash`, `log_index`, and `block_timestamp`

### Component B: Trading pair enrichment  
- **Purpose**: Adds token metadata and trading pair information to raw trades
- **Logic**: Joins trade events with trading pair definitions from `Factory_PoolCreated_event` logs to obtain token addresses (`token0`, `token1`), fee tiers, and pool configurations. Further enriches data by joining with token metadata to get decimal precision for each token and create human-readable pair names using token symbols. Converts raw token amounts to decimal-adjusted values by dividing by 10 raised to the power of each token's decimal precision.
- **Key fields**: `token0_address`, `token1_address`, token decimals (`token0_decimals`, `token1_decimals`), `fee_tier`, and decimal-adjusted token amounts

### Component C: USD conversion and volume calculation
- **Purpose**: Converts token amounts to USD values and calculates trading volume
- **Logic**: Joins decimal-adjusted token amounts with end-of-day price feeds matched by timestamp (daily grain), token address, and chain. For each trade, multiplies token amounts by their respective USD prices to get USD values for both tokens. To prevent price manipulation, takes the lesser of the two USD values as the trade volume. Aggregates these volumes by day, chain, product, version, and fee tier. Trades without valid price data for either token are excluded from volume calculations.
- **Key fields**: `price_usd` from price feeds, calculated USD values for each token, and final `trading_volume` using the minimum USD value

### Component D: Trade count calculation
- **Purpose**: Counts the number of distinct trades per day
- **Logic**: Uses the same base trade data from the enriched trading volumes but focuses on counting unique transactions rather than calculating volumes. Groups trades by day and counts distinct transaction hashes, ensuring each transaction is counted only once regardless of how many swap events it contains. Applies daily aggregation and the same chain and product groupings as the volume calculation.
- **Key fields**: Distinct `transaction_hash` counts aggregated as `trade_count` by day

### Final aggregation
- **Combining components**: The daily trading volume totals are joined with daily trade counts using timestamp matching. Both components use identical time boundaries and aggregation logic to ensure proper alignment.
- **Currency conversion**: All volume calculations are performed in USD using end-of-day price feeds, with price manipulation protection via minimum USD value selection between token pairs
- **Time aggregation**: Both volume and trade count use daily boundaries defined by truncating block timestamps to day precision
- **Final calculation**: The average trading volume per trade is calculated by dividing the daily trading volume by the daily trade count using safe division to handle cases where trade count might be zero, returning null in such scenarios

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

Honeypop

Average trading volume (per trade)

Average trading volume (per trade)

Competitive landscape