Supply
Circulating supply and total supply use different definitions. A supply number needs a timestamp, a stated methodology, and an explicit treatment of burns.
HYPE mechanics
Understand supply, staking, allocations and the accounting behind the token.
WorkspaceFinancials / Token mechanicsBrowse
In Financials
03 / HYPE & PROTOCOL
Token mechanics.
The token, in context. Understand supply, fees, staking and purchases before interpreting the numbers.
Read the methodologyThe current picture.
HYPE mark price—Perpetual reference · USDC
Circulating supply—HYPE · public token metadata
Assistance Fund HYPE—Current balance · not a burn-event total
Reported validator stake—HYPE · returned validator set
PRICE · HYPERLIQUID PUBLIC INFO APIReceived —
Supply & balances.
Circulating supply is part of total supply. Tracked burns use a separate accounting boundary.
Open supply dashboardFees & revenue.
Fees, reported revenue and executed purchases are different measures.
Open revenue & fees dashboardStaking & security.
Staking & validators.
CURRENT NETWORK SNAPSHOTReported validator stake—HYPE · sum of returned validators
Active validators—Provider active flag
Returned validators—Includes inactive records
| Validator data unavailable. | ||||
Hyperliquid · validatorSummaries · NO OBSERVATION RECEIVEDReceived —
Provider stake & estimated APR · not unique holders
Data & coverage
Stake units use HYPE’s metadata decimals. APR is the provider’s predicted daily-sample estimate, not a guaranteed return. Validator stake does not measure unique holders.
Executed purchases.
Inspect observed Assistance Fund fills with their execution dates and coverage.
Open buyback dashboard06 /ECONOMIC MECHANISMS
Follow the value.
Keep the distinctions.
Economics require more than one total. Each mechanism has a different source, unit, and time boundary.
Assistance Fund
The documentation describes automated conversion of trading fees to HYPE and states that HYPE in the Assistance Fund is burned. A sampled balance does not reconstruct the purchase history.
Burns
A mechanism description does not establish a measured total. Count verified source records, reconcile overlapping categories, and disclose the historical boundary.
Staking
Staking supports network security. Delegated or staked balances are holdings, not evidence of token destruction.
Holders
Addresses are not people. Holder counts need clear coverage of execution environments, account types, and exclusions.
07 /HOLDER RESEARCH
Addresses, with context.
Explore the connected holder index with its environment coverage and observation dates. Address counts do not measure unique people.
Open holder analysis08 /EVIDENCE & COVERAGE
The archive
behind the claim.
Trace burns, purchase history, and supply context in one place—with the limits kept visible.
Open protocol researchOpen Burn LedgerMethodology & coverage notes
Sampled Assistance Fund balances are not an event-complete ledger. Sampled EVM blocks are not full-chain totals. Provider-returned records may not cover every mechanism. Missing data stays missing; estimates must be labeled as estimates.
Supply, AF balances, recent purchase fills, and validator observations are read from public endpoints while the page is open. Fees and revenue use DefiLlama daily aggregates. The protocol workspace connects dated fee and revenue history, holder observations, collected supply snapshots and a partial archive of executed AF purchases. Each series states its historical boundary; a complete burn event ledger and all-environment holder index remain unavailable. The HYPE mark price, when available, comes from the public perpetual-market context and is not a spot execution price.
Fees & Assistance Fund (opens in a new tab)Staking documentation (opens in a new tab)HyperEVM fee mechanics (opens in a new tab)