HyENA 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. HyENA's deployerFeeScale is 0.1111, so its deployer share of each user-paid fee is reduced versus the standard HIP-3 split. Revenue is read from the realized on-chain deployerFee field per fill rather than assumed.

HyENA offers USDC-settled perpetual contracts on crypto-native assets (BTC, ETH, SOL, BNB, XRP, DOGE, HYPE, FARTCOIN, PUMP, LINK, SUI, LTC, BCH, ADA, ...) plus gold, silver, and XMR. All 24 markets are deployed under the HIP-3 `hyna` namespace and execute on Hyperliquid's HyperCore order book.

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

website

Derivative exchanges

HyENA

# HyENA Trade count Methodology

## 1. Overview

Trade count measures the total number of trades executed on HyENA products, such as `hyna:BTC` and `hyna:ETH`. The frequency of user activity and market liquidity for assets traded through the project is reflected by this metric. All trades are executed on the HyperCore infrastructure and are identified through specific market namespacing.

## 2. Data sources

- **Blockchain events**: `node_fills` data from HyperCore, covering Hyperliquid

## 3. Step-by-step calculation

### Component A: Trade identification and filtering

- **Purpose**: Isolate HyENA-specific trades and prevent double-counting of transaction sides
- **Logic**: Fill records are parsed from HyperCore data. Markets are identified by filtering for the `hyna:` prefix within the asset identifier field, which denotes HyENA-attributed markets under the HIP-3 namespacing standard. To prevent the double-counting of trades, which are recorded for both the maker and taker sides in the underlying data, the dataset is filtered to include only the taker side where the `crossed` attribute is true.
- **Key fields**: `coin` (market identification), `crossed` (side identification)

### Component B: Daily aggregation

- **Purpose**: Generate daily trade totals
- **Logic**: The identified trade events are summed to produce a total count. Results are grouped by day using the block timestamp. A zero-filling strategy is applied to ensure data continuity for days with no recorded trading activity.
- **Key fields**: `block_timestamp` (timing)

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

Number of trades executed on a decentralized exchange.

HyENA

Trade count

Trade count

Competitive landscape