This build contains 1,818 HIP-4 outcome-token rows representing $403,183,505.4047749 in cumulative indexed notional and 5,723,936 fills. Those are archive totals from Purrdict's index, not claims about current liquidity or unique prediction-market questions.
What the Purrdict index contains
The unit of analysis is an outcome token, identified by a HIP-4 coin such as #1731. It is intentionally not labelled a “market count.” A binary question generally has two outcome-token rows, while a multi-outcome question has one row for each possible outcome.
The figures refresh when the landing site builds. They are descriptive of what Purrdict has indexed at that moment; they do not estimate missing intervals or silently discard rows with incomplete metadata.
Market-class coverage is measurable—and incomplete
Purrdict parses human-readable HIP-4 descriptions into recurring price binaries, price buckets, named outcomes, and fallback rows. Historical descriptions are not always complete enough to classify. The archive keeps those rows and labels the gap rather than forcing them into the wrong category.
| Parsed class | Rows | Indexed notional | Fills |
|---|---|---|---|
| Unclassified | 1,391 | $216,664,945.74324852 | 2,162,357 |
| Recurring price binary | 72 | $96,736,630.55150996 | 2,058,553 |
| Named outcome | 140 | $76,938,965.93162754 | 1,237,442 |
| Price bucket | 214 | $12,840,341.345073303 | 265,532 |
| Fallback | 1 | $2,621.83331558 | 52 |
1,391 rows are currently unclassified. Their fills and volume remain in the archive totals, but Purrdict does not infer a market type without sufficient description data.
Largest indexed outcome rows by cumulative notional
This ranking is historical. A large cumulative row can already be settled, and average execution price is not the current midpoint. Use the live Purrdict app or Hyperliquid's own order book before placing an order.
| Outcome | Coin | Class | Indexed notional | Fills | Row traders | Avg. price |
|---|---|---|---|---|---|---|
| Argentina | #1731 | Named outcome | $10,374,317.40038 | 77,448 | 283 | 0.7611868497572565 |
| Argentina | #1730 | Named outcome | $8,816,103.66695569 | 79,960 | 1,099 | 0.24169579302626312 |
| Spain | #2121 | Named outcome | $8,482,727.37891 | 133,744 | 322 | 0.7875820469703314 |
| Spain | #2120 | Named outcome | $6,736,698.38941262 | 143,986 | 1,260 | 0.23388513440383094 |
| France | #1891 | Named outcome | $5,990,841.35061 | 106,762 | 307 | 0.682929736797737 |
| France | #1890 | Named outcome | $4,129,262.25390169 | 107,107 | 1,056 | 0.3057663280932152 |
| Portugal | #2051 | Named outcome | $3,680,740.95498 | 15,214 | 159 | 0.8930680649401866 |
| Recurring | #1541 | Recurring price binary | $3,495,337.60798 | 69,569 | 300 | 0.6787103298883124 |
| Recurring | #200 | Recurring price binary | $3,369,601.94489 | 47,343 | 631 | 0.7370036592526878 |
| Unnamed outcome | #5100 | Unclassified | $3,185,476.89011327 | 4,452 | 391 | 0.7947072027448338 |
| Unnamed outcome | #8131 | Unclassified | $2,873,304.57071 | 9,649 | 415 | 0.5097525836874287 |
| Recurring | #601 | Recurring price binary | $2,552,490.88919 | 85,334 | 378 | 0.5570411555769096 |
How this snapshot is produced
- Index fills. Purrdict's data pipeline ingests HIP-4 outcome fills and preserves the protocol's outcome-token identifiers.
- Group by outcome token. The overview endpoint aggregates cumulative fill count, indexed notional, per-row trader count, and average execution price for each coin.
- Parse descriptions defensively. Known description shapes become named classes. Missing or ambiguous metadata remains unclassified.
- Generate a static research page. The landing build fetches the JSON distribution, calculates only transparent sums, prints the UTC build date, and exposes the source.
The page does not manufacture a protocol-wide unique-trader number by summing overlapping row counts. It also does not turn a token-row count into a unique-question count. Both would be visually impressive and analytically wrong.
What the data cannot tell you
- Current executable liquidity. Cumulative notional does not reveal today's spread or depth.
- Protocol-wide unique traders. Addresses overlap across outcome-token rows.
- Unique questions from row count. One question can produce two or many tradeable rows.
- Complete metadata coverage. Some historical rows lack a parseable public description.
- Missing-data estimates. The totals include only successfully indexed records; no backfilled estimate is added for unavailable intervals.
- Investment performance. Historical volume, fills, and average prices do not predict future returns.
For protocol identity and settlement mechanics, use the canonical HIP-4 guide. For current market prices, use Purrdict's live mainnet interface or query Hyperliquid directly.
Download, inspect, and cite the source
The complete overview distribution is public JSON at https://api.purrdict.xyz/api/markets/overview. The response exposes the same fields used on this page, so every displayed aggregate can be reproduced independently.
The public Purrdict HIP-4 market-data repository preserves dated snapshots, a machine-readable methodology, and a tested generator. Download the latest JSON snapshot or CSV snapshot under CC BY 4.0.
Suggested attribution: “Purrdict HIP-4 Indexed Market Overview, snapshot generated August 3, 2026 UTC.” Link to this landing page so readers get the methodology and limitations alongside the numbers.
HIP-4 market-data FAQ
How many HIP-4 markets does this dataset contain?
The current build contains 1,818 outcome-token rows. A row is not the same as a unique question: binary questions normally create two outcome tokens, and multi-outcome questions create more.
Is the volume figure live trading volume?
No. It is cumulative indexed notional across the rows returned by the Purrdict data API at build time. It is not open interest, TVL, current liquidity, or an execution quote.
Why are some rows unclassified?
The index preserves rows even when historical description metadata is missing or cannot be parsed into a known market class. Unclassified does not mean invalid; it means the public classification layer cannot make a reliable claim.
Can I sum the trader counts?
No. One address can trade several outcome tokens, so per-row trader counts overlap. The page deliberately does not present their sum as protocol-wide unique traders.
Where can I get the raw HIP-4 data?
Open the JSON distribution at https://api.purrdict.xyz/api/markets/overview. Builders that need streaming, webhooks, or normalized historical tables can use mute.sh.