Ventuals 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.

Ventuals offers USDC-settled perpetual contracts on pre-IPO / private companies (OpenAI, Anthropic, SpaceX), thematic equity baskets (MAG7, SEMIS, BIOTECH, DEFENSE, ENERGY, INFOTECH, NUCLEAR, ROBOT), and commodities (gold, silver, soybeans, wheat). All 15 markets are deployed under the HIP-3 `vntl` namespace and execute on Hyperliquid's HyperCore order book.

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

website

github

Derivative exchanges

Ventuals

# Ventuals Active users (weekly) Methodology

## 1. Overview

Active users (weekly) measures the number of unique addresses that execute revenue-generating trades on Ventuals products, such as `vntl:SPACEX` and `vntl:OPENAI`. This metric captures both makers and takers participating in perpetual swap markets deployed via the Ventuals protocol. User activity is identified through trade fill events on the Hyperliquid blockchain, specifically targeting markets registered under the Ventuals namespace.

## 2. Data sources

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

## 3. Step-by-step calculation

### Component A: Trade fill extraction

- **Purpose**: Identify all trading activity occurring on Ventuals-deployed markets
- **Logic**: Trade fill data is parsed from HyperCore contracts on the Hyperliquid blockchain. Markets are filtered to include only those where the asset symbol carries the `vntl:` prefix, which signifies a market deployed by the Ventuals protocol. Trader addresses are extracted from the account fields of these fill events, capturing participants on both the maker and taker sides of every matched trade.
- **Key fields**: `account_address` (trader identification), `coin` (market identification), `block_timestamp` (timing)

### Component B: Weekly unique address aggregation

- **Purpose**: Calculate the total count of unique participants per 7-day window
- **Logic**: The extracted trader addresses are aggregated and deduplicated to determine the number of unique active users. This count is calculated over 7-day rolling windows. Weekly granularity is maintained using UTC day boundaries.
- **Key fields**: `trader_address` (unique identifier), `block_timestamp` (temporal grouping)

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

Unique revenue-generating users over a rolling 7-day window.

Ventuals

Active users (weekly)

Active users (weekly)

Competitive landscape