Sources & coverage
See what is available, when it was observed and where the gaps remain.
WorkspaceResearch & Learn / Sources & coverageBrowse
In Research & Learn
06 / RESEARCH & CONTEXT
Data status.
See when each source was checked, when its observation arrived and which reporting date it describes. Missing observations remain unavailable.
Need attention—Failed, incomplete, overdue or dated observations
Not yet checked—No recorded source observation
Recent server observations—Within the recorded freshness boundary
This browser · market streamConnectingAwaiting a valid market frame
Checking saved source health…
Collection jobs
Each job has its own latest attempt and last complete run. Native market updates do not refresh protocol, holder or institutional archives.
Run times show saved activity, not whether a schedule is enabled. Jobs become overdue after 90 minutes; paused jobs may be expected to remain overdue. Refresh status only reads saved evidence.
| Collection job | Latest result | Latest attempt / UTC | Last complete run / UTC | Recovery details |
|---|
Funding recovery resumes at unobserved hours. Conflicted rates remain unavailable while later history can continue. Missed open-interest samples cannot be reconstructed from a new snapshot.
Source observations.
Attention first · then source name
Awaiting source status
How to read these timestamps
- Last check
- When the server most recently checked the source, including unsuccessful checks.
- Last observation
- When the recorded observation was received. This may predate the latest check.
- Provider date
- The source’s reporting time, where supplied. A successful check does not make an older report current.
| Source / dataset | Server observation | Last check / UTC | Last observation / UTC | Provider date / UTC | Details |
|---|
Reading saved source health…
History & retention.
Live values, saved observations and provider history cover different things. This audit reads saved public records; it does not refresh providers or fill gaps.
Reading saved history…
Dataset inventory.
17 public dataset families
How each family reaches the page, what we retain and what still needs work. A recovery snapshot replaces the previous payload; it does not create a growing historical archive.
01Market prices, funding and open interest
- Used on
- Briefing · Dashboard · Screener · Heatmap · Terminal
- Delivery
- Supported market fields stream while the browser is active; the catalog also refreshes over HTTP. A stream does not update every field.
- Retained history
- Latest recovery snapshots and dated native aggregate observations. BTC/ETH/SOL/HYPE funding events retain original receipts and unresolved-hour coverage. Per-market open interest retains each collected native sample; charts select the last receipt per UTC hour, preserving gaps and base/USDC units.
- Next improvement
- Inspect funding, historical funding-cost scenarios and open-interest history in Data health. Funding scenarios use saved settlements and withhold full-window totals across gaps. Markets/all collection advances the funding target and native OI samples; earlier OI is not backfilled. Automatic collection is a separate setting.
- Monitored sources
- Market catalog archive · Native market overview · Market catalog recovery snapshot
02Candles, comparisons and chart indicators
- Used on
- Terminal · Dashboard · Compare markets · Price & funding
- Delivery
- Selected market candles load on demand from Hyperliquid; the terminal subscribes to the selected candle stream.
- Retained history
- Up to 5,000 requested candles. Terminal server requests accumulate the latest 500 valid closed candles per request, preserving per-candle receipts. Browser-direct fallback and live stream updates do not write the archive.
- Next improvement
- Archive inspection includes gap counts. Automatic chart recovery from archived candles, scheduled market coverage and older backfills remain open.
- Monitored sources
- Selected on-demand requests; not a fixed background feed.
03Order books, trades and HIP-3 depth
- Used on
- Liquidity · Terminal · HIP-3 deployers
- Delivery
- Selected books and trades stream in the browser. HIP-3 research polls every 90 seconds and samples one book per active deployer, up to 24. Venues with zero returned active markets are not book requests.
- Retained history
- Latest sampled contexts, plus native aggregate daily observations. No complete order-book or trade replay archive.
- Next improvement
- Repair missing sampled books and disclose the returned sample; full replay requires a dedicated collector.
- Monitored sources
- HIP-3 contexts and sampled depth
04Venue comparisons
- Used on
- Market share
- Delivery
- CoinGecko comparison snapshots are collected hourly when Demo access is configured. Pages check the shared archive every two minutes; visitor refreshes do not call the provider.
- Retained history
- Daily venue observations when returned. Provider failures leave older values dated.
- Next improvement
- Provider activation is deferred under the Hyperliquid-first migration. Cross-exchange comparisons require non-Hyperliquid evidence and matching units; they cannot be reconstructed from Hyperliquid alone.
- Monitored sources
- Hyperliquid venue comparison · Binance venue comparison · Bybit venue comparison · OKX venue comparison
05HYPE supply and tracked burns
- Used on
- Supply & holders · Token mechanics · Burn ledger
- Delivery
- Current Hyperliquid supply refreshes every 30 seconds on research pages.
- Retained history
- Daily supply-state observations and at most one reconciled observation per UTC hour. The hourly chart reads the latest 720 records. These are states, not a full burn/unlock event ledger.
- Next improvement
- Continue collection; historical supply states cannot be reconstructed from today’s balance.
- Monitored sources
- Supply and tracked burns
06Native HYPE price and circulating value
- Used on
- Supply & holders
- Delivery
- Calculated here from Hyperliquid only, refreshed every minute. Verified HYPE/USDC token IDs, a dated two-sided order book and reconciled supply produce midpoint, spread and circulating value in USDC.
- Retained history
- Separate daily USDC series start with collected observations. Valid server refreshes and core collections save inputs and receipts; browser-direct fallback does not write history. The book has a source time; supply has a separate receipt only. Background accumulation requires an enabled collector.
- Next improvement
- Expand native history from verified raw observations. No USD peg, midnight close, complete earlier history or executable sale value is inferred.
- Monitored sources
- HYPE native price and circulating value
07Assistance Fund balances and purchases
- Used on
- Revenue & buybacks · Burn ledger
- Delivery
- Current balances and returned executions refresh every 30 seconds.
- Retained history
- Partial daily purchase totals plus a separate native execution archive: raw fill evidence, exact decimals, first receipts, request boundaries and durable conflicts. Fee currencies stay separate; unseen fills remain unknown.
- Next improvement
- Inspect saved execution records and account fees in the Burn ledger or Data health. Core/all collection resumes bounded pages within the public API retention limit. Full protocol fee reconciliation needs wider native event coverage.
- Monitored sources
- Assistance Fund balances and purchases
08Protocol fees and revenue
- Used on
- Revenue & buybacks · Dashboard
- Delivery
- DefiLlama is checked every five minutes on research pages; figures follow provider reporting dates.
- Retained history
- Returned daily fee and revenue series are persisted by their original dates and revised when validated source updates arrive.
- Next improvement
- Replace aggregation only after a checkpointed Hyperliquid execution/fee index reconciles fee definitions, rebates and complete date coverage. Existing provider history remains separately attributed until then.
- Monitored sources
- Protocol fees · Protocol revenue
09HYPE holders and distribution
- Used on
- Supply & holders · Holder analysis
- Delivery
- Holder count refreshes every five minutes; distribution uses a separate 15-minute source interval.
- Retained history
- Daily holder count plus a latest top-holder/history snapshot. The core collector requests up to seven older dates per run and retries up to two queued dates, within its one-year target.
- Next improvement
- Continue the checkpointed backfill and retry internal date gaps. Only an observation on the requested UTC day resolves a retry; unavailable dates remain explicit.
- Monitored sources
- HYPE holder count · Holder distribution and history
10External HYPE USD reference
- Used on
- Institutional USD valuation comparisons
- Delivery
- One-minute refresh in institutional comparisons. CoinGecko is primary; a dated, validated DefiLlama quote is alternate delivery. Core collection now uses native HYPE/USDC calculations instead.
- Retained history
- Latest validated quote with source and receipt times. No independent USD price archive.
- Next improvement
- Retain only where comparisons require USD. Keep attribution visible; alternate delivery is not independent corroboration and USDC is not assumed to equal USD.
- Monitored sources
- HYPE dollar quote for valuation comparisons
11ETF reports, treasuries and equity valuation
- Used on
- ETFs & valuation · Institutional treasuries
- Delivery
- Fund sources are checked every five minutes; equity inputs every 15 minutes. Reports and filings retain their publication dates.
- Retained history
- Dated ETF NAV, shares, assets and eligible estimated flows; latest equity inputs and issuer disclosures. Missing NAV or nonconsecutive sessions can withhold a flow estimate.
- Next improvement
- THYP can use a matching dated issuer-page disclosure when both history services fail. This does not backfill missing sessions. HYPG is reference-only until an accessible numerical issuer feed is verified.
- Monitored sources
- THYP issuer reports · BHYP issuer reports · HOOD valuation inputs · CME valuation inputs · ICE valuation inputs · Institutional company disclosures
12TVL, protocols, HLP and stablecoins
- Used on
- Network overview · TVL & HLP · Protocol history · Stablecoins
- Delivery
- Public Hyperliquid and DefiLlama datasets refresh on their page intervals; individual protocol history loads on demand.
- Retained history
- All/network collections accumulate up to 2,000 completed-day observations each for Hyperliquid L1 TVL (USD) and public HLP account value (USDC). Unchanged points retain their receipt times. Protocol and stablecoin payloads still use latest-snapshot recovery.
- Next improvement
- Extend dated storage to protocols and stablecoins, verify longer coverage and integrate archived data into chart recovery. Stored balances are not inferred net capital flows.
- Monitored sources
- Chain TVL history · HLP portfolio · Ecosystem protocols · Stablecoin history
13Lending reserves and yield pools
- Used on
- HyperCore lending · HyperEVM lending · Yields
- Delivery
- Hyperliquid reserve states and DefiLlama pool snapshots; selected pool history loads on demand.
- Retained history
- Latest validated reserve/pool snapshots. Yield history is bounded to the last 180 returned points, not necessarily 180 days; no independent reserve history.
- Next improvement
- Archive dated reserve and pool observations before offering historical utilization or rate claims.
- Monitored sources
- Lending reserves · Yield pools
14Bridges, validators and HyperEVM
- Used on
- Cross-chain · Validators · HyperEVM · Burn ledger
- Delivery
- Recent Hypurrscan bridge events, Hyperliquid validator states, an eight-block live HyperEVM sample and a separate official-RPC gas-fee archive.
- Retained history
- Core/network/all runs retain up to eight consecutive receipt-verified EVM blocks with base/priority fees and a durable next-block checkpoint. Earlier and uncollected blocks remain unknown. Bridges and validators retain bounded samples.
- Next improvement
- Expand native block capture and reconcile wider fee/holder sources before claiming complete event coverage. A saved checkpoint does not mean continuous collection is enabled.
- Monitored sources
- Recent bridge activity · Validator stake · HyperEVM recent block sample
15Outcomes and deployment auctions
- Used on
- HIP-4 outcomes · Auctions
- Delivery
- Public outcome metadata and Hypurrscan auction lists refresh as snapshots.
- Retained history
- Latest directory and provider-returned auction history. No complete outcome trading or settlement archive.
- Next improvement
- Keep directory coverage distinct from live prices, traded volume and settlement history.
- Monitored sources
- Outcome market directory · Spot deployment auctions · Perpetual deployment auctions · Pair deployment auctions
16Wallet research, trader tape and builders
- Used on
- Wallet research · Wallet charts · Trader tape · Builder codes
- Delivery
- Selected public addresses load on demand. The tape samples up to 28 wallets, with up to eight browser streams. Leaderboard data is a provider snapshot.
- Retained history
- Latest public tape sample; selected wallet portfolio/fills and builder-fee samples are provider-bounded. This public audit excludes saved private watchlists, rules and activity.
- Next improvement
- Expose per-query limits and avoid extrapolating sampled fills into complete wallet or builder revenue history.
- Monitored sources
- Monitored public trader sample
17News, research and source library
- Used on
- News · Journal · Primary-source library
- Delivery
- Publisher feeds refresh on page intervals. Editorial research and source links are dated reference material.
- Retained history
- Latest publisher payloads and authored material, not a complete historical news corpus. Share cards are fixed dated exports.
- Next improvement
- Preserve original publication and source dates when refreshing or exporting.
- Monitored sources
- Policy Center news · Official announcements · CoinDesk headlines · HyperliquidNews headlines
What this status covers.
Server observations and browser streams have separate checks. A source can be reachable while its latest report is dated, its returned sample is incomplete, or its recovery snapshot cannot be saved. Fees and issuer reports follow their publication dates.
Wallet investigations run for the selected address. Private Watching requires an authenticated monitoring connection for background checks. The public trader tape covers a bounded sample; HIP-3 depth and HyperEVM activity are also sampled. Editorial research and downloaded exports retain their publication dates.