Methodology
This page exists because product rule 7 requires it: the weights and known gaps behind every conclusion are published here, not hidden in scoring internals. They are explicit assumptions, not backtested constants, and will change as evidence shows they’re ineffective.
Engine weights by timeframe
| Engine | 7d | 30d | 90d | 12m |
|---|---|---|---|---|
| Whale Intelligence | 30% | 15% | 15% | 10% |
| Volume & Market Flow | 30% | 25% | 25% | 20% |
| Staking & Liquid Supply | 25% | 25% | 25% | 15% |
| HIP Ecosystem | 5% | 15% | 15% | 30% |
| Value Capture | 10% | 20% | 20% | 25% |
The spec’s 12-month table lists a “Protocol demand” line with no dedicated engine defined for it; it is mapped here to the Volume & Market Flow engine, the closest existing demand-side signal.
Data sources
- Hyperliquid Info API (api.hyperliquid.xyz/info) — funding, open interest, volume, mark/oracle price, spot supply, validator stakes, per-wallet delegation and positions, HIP-3 deployments. Public, no key required.
- Hyperliquid stats leaderboard (stats-data.hyperliquid.xyz) — full account leaderboard by value/PnL/volume, used to find whale candidates. Public, no key required.
- burn.a1ntel.com — Assistance Fund buyback activity and protocol fee history. Powers the Value Capture engine directly, as specified.
Upcoming unlock dates
The Staking engine’s “upcoming unlocks” chart is built from Hyperliquid’sdelegatorHistory endpoint, which emits a withdrawal “initiated” event when an unstake enters the queue. We verified live, on a real wallet, that “finalized” follows “initiated” at exactly +7 days (604,800,229ms measured) — so the estimated unlock date is a measured delay, not a guess. Like the rest of the staking data, this is sampled from the ~150 tracked accounts, not the full delegator base, and a scheduled unlock is never presented as confirmed intent to sell.
Known gaps
Per rule 8, this platform shows “insufficient evidence” rather than fabricating a number. As of this version:
- No public liquidations feed exists. Liquidation pressure is only inferred indirectly from open interest drops and funding extremes, and is never presented as a liquidation count.
- No confirmed public API for HyperEVM contract-level activity. The Ecosystem engine covers HIP-3 market launches and deployer concentration; HyperEVM activity, new collateral types, and deployer/treasury fee revenue are excluded rather than estimated.
- Staking, whale-position, and HIP-3 launch trends have no historical API. Hyperliquid only exposes current state for these — this platform’s own polling history is the only source of trend data, so these signals report “insufficient evidence” and mature in confidence as more polling cycles accumulate.
- Whale classification is a published heuristic, not a confirmed fact. Accounts are excluded from the whale set if registered as a vault or if their day volume exceeds 3× their account value (likely market-making/automated). This heuristic can misclassify.
- Unstaking/pending-withdrawal tracking is sampled, covering only the ~150 largest accounts by value, not the full delegator base — there is no public API to enumerate all delegators.
- Fee history beyond 7 days is extrapolated, not measured. burn.a1ntel.com exposes granular fee data for a maximum of 7 days; longer-timeframe fee figures are the measured 7-day daily rate multiplied by the window length, always labeled as an estimate. Assistance Fund buyback totals, by contrast, are measured from full history at every timeframe.