Capacity and configuration history
Inspect builder capacity and recorded changes.
Where is HIP-3 capacity concentrated, and what changed?
HypeBasis joins current DEX limits, market state, metadata, and public open interest. Saved snapshots become an event ledger for cap, margin, funding, fee, operator, and lifecycle changes. A polling difference proves only that a value changed between two observations; it does not prove the exact action time or actor.
Current official state
Builder-DEX capacity
| DEX | Open interest | DEX cap | Cap used | Net deposit | Markets |
|---|---|---|---|---|---|
| XYZxyz | $3.6B | $10B | 35.9% | $1.1B | 104 / 119 |
| EntropyIOio | $35.1M | $100M | 35.1% | $22.8M | 5 / 7 |
| Paragonpara | $14.6M | $50M | 29.2% | $10.7M | 25 / 33 |
| Markets By Kinetiqmkts | $5.4M | $100M | 5.4% | $5M | 4 / 23 |
| Felix Exchangeflx | $0 | $200M | 0.0% | $6.5K | 0 / 16 |
| Ventualsvntl | $0 | $50M | 0.0% | $23K | 0 / 15 |
| HyENAhyna | $0 | $150M | 0.0% | $2M | 0 / 25 |
| Markets by Kinetiqkm | $0 | $100M | 0.0% | $24.1K | 0 / 23 |
| ABCDExabcd | $0 | $50M | 0.0% | $0 | 0 / 1 |
| dreamcashcash | $0 | $200M | 0.0% | $127.6K | 0 / 17 |
Markets nearest their reported cap12 marketsCollapse
| Market | Open interest | Market cap | Cap used | Margin mode |
|---|---|---|---|---|
| io:NBIS | $9.4M | $10M | 94.0% | strictIsolated |
| io:OAI | $4.4M | $5M | 87.1% | noCross |
| io:ANTH | $15.4M | $18M | 85.5% | strictIsolated |
| io:SNDK | $5.4M | $10M | 53.7% | strictIsolated |
| xyz:TSLA | $47.1M | $100M | 47.1% | Unreported |
| xyz:BABA | $11.6M | $25M | 46.5% | noCross |
| xyz:MSTR | $43.6M | $100M | 43.6% | noCross |
| xyz:AAPL | $82.6M | $200M | 41.3% | Unreported |
| xyz:GOLD | $308.7M | $750M | 41.2% | Unreported |
| xyz:NBIS | $59.8M | $150M | 39.8% | noCross |
| xyz:CRCL | $57.8M | $150M | 38.5% | noCross |
| xyz:HOOD | $57.6M | $150M | 38.4% | noCross |
Prospective public history
Configuration event ledger
No readable saved capture exists in this environment. The ledger begins prospectively because the public endpoints provide current state rather than a complete change history.
Download observed configuration changes
0 captures · 0 events · CSV reads KV only.
Evidence boundary
Current state is not an exact event timestamp
- 1. Read public DEX identity, limits, status, market metadata, and market contexts.
- 2. Save one bounded mainnet snapshot every six hours on a dedicated minute-47 schedule.
- 3. Diff only configuration fields; ordinary open-interest movement does not create an event.
- 4. Label every change “observed between” the earlier and later capture until action-level provenance is added.
Event CSV columns and units10 fieldsCollapse
| Column | Unit | Meaning |
|---|---|---|
| observed_after_utc | ISO 8601 UTC | Last capture with the earlier value. |
| observed_before_utc | ISO 8601 UTC | First capture with the changed value. |
| time_precision | enum | Always observed-between for snapshot differences. |
| scope | enum | DEX or market configuration. |
| dex | text | Builder-deployed perp DEX short name. |
| market | text | Market name when the change is market-scoped. |
| field | text | Configuration field that changed. |
| previous_value | field unit | Value in the earlier capture. |
| current_value | field unit | Value in the later capture. |
| unit | text | Unit or value type for the changed field. |
Interpretation limit
A cap is a configured boundary, not a liquidity guarantee or a forecast that trading will halt. Open interest uses reported mark price and base size. Snapshot differences can miss changes that occur and reverse between captures, and must not be used to infer misconduct, intent, or causation.
How to read this dataReviewed 2026-09-04 · ExpandCollapse
- Where this comes from
- Official Hyperliquid perpDexs, allPerpMetas, perpDexLimits, perpDexStatus, perpsAtOpenInterestCap, and metaAndAssetCtxs requests.
- How fresh it is
- Current state uses an hourly server cache. Saved snapshots use 47 */6 * * * UTC. Latest live read: Sep 5, 04:17.
- Last reviewed
- 2026-09-04
- How to use it
- The event ledger compares public state, preserves both observation timestamps, excludes user addresses, and does not claim exact action timing.
Sources
3 references · ExpandCollapse
- Hyperliquid Docs: HIP-3 builder-deployed perpetualsAccessed 2026-09-04Supports: HIP-3 builder-deployed perp mechanics, deployer responsibilities, 500,000 HYPE staking requirement, minimum stake duration, deployment rules, configurable fees, settlement, oracle duties, slashing risk, cross margin, and backstop liquidation.
- Hyperliquid Docs: Perpetuals info endpointAccessed 2026-09-04Supports: Core and HIP-3 perpetual DEX discovery, current market contexts including rolling dayNtlVlm, perpetual metadata, funding history, predicted funding, DEX and market limits, DEX status, configuration metadata, clearinghouse state, and open-interest cap fields.
- Hyperliquid Docs: Rate limits and user limitsAccessed 2026-09-04Supports: Current REST request-weight, WebSocket, and user-limit constraints for public-data tooling.