7 daily intervals
Building- Circulating change
- Withheld
- Total change
- Withheld
- Coverage
- 1 of 8 required daily captures
Live official supply, observed change history, and a source-by-source map of what calendar claims can prove.
Hyperliquid's official API does not publish a complete future HYPE release calendar. It currently reports 298,692,928 HYPE in circulating supply and 998,990,774 HYPE in total supply. A securities filing describes some contributor distributions while stating that concrete schedules for other allocations remain unannounced. HypeBasis therefore labels calendar dates from other services as third-party models rather than official protocol commitments.
Read Aug 26, 2026, 5:09 AM UTC
A release, transfer, distribution, and circulating-supply update are different events. The official circulating field is the current classification used here; it does not explain who controls each balance or whether any token was sold.
Each result compares official supply endpoints across complete daily capture intervals. Missing days, old data, or malformed fields suppress the change.
| Window | Status | Circulating change | Total change | Coverage |
|---|---|---|---|---|
| 7 daily intervals | Building | Withheld | Withheld | 1 of 8 required daily captures |
| 30 daily intervals | Building | Withheld | Withheld | 1 of 31 required daily captures |
Net field changes describe official classifications between two saved endpoints. They do not identify a recipient, transfer, sale, or price effect. The shared hourly cron saves at most one valid record per day.
Sources answer different questions. HypeBasis keeps current protocol fields, filing disclosures, and modeled calendars in separate rows.
Current total and circulating-supply fields for the HYPE spot pair.
No complete future release calendar or recipient intent.
Reported contributor-distribution mechanics and historical allocation context.
The filing is not protocol documentation and says other concrete schedules remain unannounced.
A transfer-based allocation model with published assumptions.
A tracked transfer does not establish the official circulating classification or a future commitment.
A separate vesting and event-calendar interpretation.
Its categories and dates remain third-party model output.
Treat supply changes as one input beside market liquidity, revenue, staking emissions, and actual transfer evidence. A calendar event does not prove a sale, and a price move around a date does not prove that the event caused it.
Inspect the full supply ledgerReview eligibility, fees, and trading risk before acting on any supply claim.
Reconcile current supply, validator stake, burned HYPE, allocations, and modeled staking rewards.
Test circulating or maximum-supply value against complete revenue windows.
Inspect protocol-side revenue estimates and official Assistance Fund balance captures.
Check price, funding, open interest, execution, scheduled flow, and public positioning.