Paragon earns a deployer share of trading fees on the perpetual markets it has deployed under Hyperliquid's HIP-3 framework. Markets execute on Hyperliquid's HyperCore L1 order book; it does not operate its own matching engine. The default HIP-3 fee split allocates 50% of each user-paid fee to Hyperliquid and 50% to the deployer; deployerFeeScale is 1.0, so the standard split applies.

Paragon offers USDC-settled perpetual contracts on crypto index and basket products (BTC dominance, TOTAL2, OTHERS) and AVGO. All 4 markets are deployed under the HIP-3 `para` namespace and execute on Hyperliquid's HyperCore order book.

Paragon is a HIP-3 (builder-deployed perpetuals) deployer on Hyperliquid, deployed by wallet 0x8888888c43cbb7e1c4132542e46831bffd866ed3. Paragon is operated as a private company; no token has been issued.

website

github

Derivative exchanges

Paragon

# Paragon Average revenue per user (ARPU) Methodology

## 1. Overview

Average revenue per user (ARPU) is calculated as the revenue generated per active user over a fixed 24-hour window for Paragon Perps. The protocol's ability to monetize individual traders on a daily basis is reflected by this metric. Revenue is derived from the 50% share of user-paid trading fees allocated to Paragon as a HIP-3 deployer on Hyperliquid, while the user base is comprised of unique addresses participating in trades on Paragon-deployed markets.

## 2. Data sources

- **Revenue**: Derived from the Revenue metric
- **Active users (daily)**: Derived from the Active users (daily) metric
- **Blockchain events**: fills from Hyperliquid HyperCore, covering HyperCore
- **External data**: Asset metadata for fee-token identification

## 3. Step-by-step calculation

### Component A: Paragon Perps trade identification

- **Purpose**: Trading activity occurring on Paragon-deployed perpetual markets is identified.
- **Logic**: Fills are filtered from Hyperliquid HyperCore records where the market identifier contains the `para:` prefix. This namespacing identifies markets registered under the Paragon deployer wallet. Data is aggregated from both legacy and current fill records to ensure full historical coverage.
- **Key fields**: `coin`, `trader_address`, `fee`, `fee_token`

### Component B: Revenue calculation

- **Purpose**: The daily protocol revenue retained by Paragon is determined.
- **Logic**: User-paid fees are extracted from identified fills. Because fees are paid in USDC, amounts are treated as USD-denominated without additional price conversion. Protocol revenue is calculated by applying a 50% allocation to the total user-paid fees, representing the standard HIP-3 deployer share.
- **Key fields**: `fee`, `fee_token`

### Component C: Active user tracking

- **Purpose**: The daily unique participant count for Paragon Perps is calculated.
- **Logic**: active users (daily) are identified by extracting the unique set of trader addresses that appear on either the maker or taker side of a matched trade. These addresses are aggregated daily to provide the denominator for the ARPU calculation.
- **Key fields**: `trader_address`

### Component D: Final ARPU derivation

- **Purpose**: The average revenue generated per individual user is calculated.
- **Logic**: Total daily revenue is divided by the count of active users (daily). The calculation is performed at a daily granularity using UTC day boundaries. In instances where no activity is recorded, the value is zero-filled to maintain data continuity.
- **Key fields**: `revenue`, `user_dau`

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

Paragon

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape