Hyperliquid's starting point is a working market rather than a catalogue of unrelated applications. Its documentation describes an independent Layer 1 secured by HyperBFT, with HyperCore and HyperEVM as two execution environments. Orders, cancellations, trades and liquidations belong to the chain's financial state. It is therefore misleading to describe the exchange as an ordinary application secured by Ethereum, even though developers can use Ethereum-compatible tooling on HyperEVM.

The official ambition extends well beyond perpetual futures: the team wants an open financial system whose markets and supporting applications operate onchain. That ambition explains why an exchange project built its own infrastructure. It is a statement of intended direction, not evidence that every financial instrument, legal claim or real-world settlement process has already moved onto Hyperliquid.

Hyperliquid Labs describes its origins in proprietary crypto trading in 2020, followed by a deeper move into decentralised finance in 2022. Its contributors page names Jeff and iliensinc as leaders and describes them as Harvard classmates. The founders' explanation is practical: existing decentralised markets had technical and user-experience problems that they wanted to solve. That history helps explain the emphasis on execution, order management and an interface that active traders can recognise.

The same account says development was self-funded. That describes development financing, not a lack of contributor interests. The separate genesis allocation includes contributor tokens and vesting. Funding history and ownership therefore need to be examined independently.

Perpetual futures need reference prices as well as buyers and sellers. Hyperliquid's oracle documentation explains that validators submit prices derived from specified trading venues, with aggregation across validator submissions. Those prices help determine funding and contribute to the mark price used for margin and liquidation. A trader should consequently distinguish an order-book execution price, an external reference price and the accounting price used to assess a position's risk.

This design exposes a concrete dependency behind the phrase fully onchain. Agreement and accounting occur on the network, while some reference information originates in other markets. The documentation treats assets with primary Hyperliquid liquidity differently from assets whose main spot market is elsewhere. Market design must therefore be evaluated asset by asset; one successful highly liquid contract cannot establish the safety of every thinly traded listing.

HyperEVM is part of the same consensus system as HyperCore. Its purpose is to let contracts use a general programming environment alongside the chain's specialised financial machinery. For an application team, the attraction is the possibility of building around an existing trading audience and market infrastructure. Sharing consensus does not make every third-party contract part of the exchange's security review, nor does it erase the application's own permissions and failure modes.

The EVM uses separate fast, smaller blocks and slower, larger blocks. The stated engineering aim is to accommodate quick confirmations and larger transactions without forcing both onto one block-size schedule. A deployment that needs the larger block path has different timing from a simple transaction. The meaningful developer question is whether the actual workload behaves reliably under that arrangement, rather than whether a headline throughput number sounds impressive.

Builder codes give application developers a direct commercial mechanism. A user authorises a maximum fee for a particular builder; eligible orders can then carry that builder's fee, processed by the chain. The documentation distinguishes these application builders from block builders in consensus. A trading interface, bot or other application can therefore earn revenue from the service it provides without having to launch a speculative token first.

The authorisation is bounded and revocable, and the documented fee rules differ between spot and perpetual trading. Those details matter to users comparing interfaces that reach the same underlying market. Shared liquidity does not imply identical total costs. They also give developers a measurable test of product demand: continuing fee-paying use is stronger evidence of a useful interface than social attention alone.

HIP-3 allows builders to deploy perpetual markets using HyperCore infrastructure. This opens market creation beyond the original validator-operated listings, but the deployer still makes consequential choices about oracles, specifications and settlement. The current documentation requires substantial HYPE stake. Permissionless in this setting means an eligible participant can meet published requirements; it does not mean that deploying a financial market is free or technically effortless.

The specification also describes validator action against harmful deployer conduct, including slashing and burning stake. Slashed value is not described as a compensation fund for affected traders. Deployer control, oracle quality, key security and settlement rules therefore deserve attention before a market is used. A familiar exchange interface can conceal very different responsibilities underneath individual listings.

The November 2024 genesis announcement allocated 31% of the one-billion-token initial maximum supply to the genesis distribution and 23.8% to current and future core contributors. It separately reserved supply for future emissions and community rewards, the Foundation and grants. Eligible genesis tokens were unlocked; contributor tokens had a lock and vesting schedule. These are distinct groups and timelines, not one uniformly liquid community allocation.

The announcement specified no allocation to private investors, centralised exchanges or market makers. This supports the community-first narrative without guaranteeing equal user ownership, preventing later concentration or creating a contractual claim on a company.

HYPE holders can delegate stake, while validators perform the work of consensus. The staking documentation describes a self-delegation requirement, lock periods and a withdrawal queue. Rewards come from the future-emissions reserve. Receiving additional tokens is therefore different from receiving external business profit: holders must also consider issuance, validator performance and the conditions under which stake becomes liquid again.

At this review, the staking documentation says automatic consensus slashing is not implemented; it separately describes validator jailing. That should not be confused with the deployer-specific slashing rules in HIP-3. Hyper Foundation dates permissionless validator registration to April 21, 2025. Registration being open is an important change, while active-set selection, stake concentration and operational capacity remain separate measures of decentralisation.

The protocol vault HLP gives depositors exposure to strategies including market making and liquidation activity. Its documentation says depositors share profit and loss, and specifies a withdrawal lock that resets after the latest deposit. The community appeal is understandable: activities often associated with specialist firms become accessible through a shared pool. Accessibility, however, changes who can take the risk rather than eliminating that risk.

A vault participant should examine adverse market moves, liquidation exposure and withdrawal conditions together. A profitable recent period is a record of that period, not a promise about the next one. HLP also helps explain why the community debates emergency market interventions so intensely. Some participants are traders in an individual contract, while others are capital providers exposed to the system's handling of difficult positions.

The current fee documentation describes flows to HLP, deployers and the assistance fund. It says the assistance fund converts fees to HYPE and that its HYPE is burned, reducing supply. This is more specific than older shorthand about tokens merely sitting in a buyback wallet. Trading and staking tiers also affect the fees users pay, so gross activity should not be mistaken for one fixed revenue rate.

A tokenholder can construct a thesis around recurring useful activity and supply reduction. The additional claim that this necessarily produces a higher market price is a hypothesis. It depends on activity quality, competing venues, issuance, sales and the price already paid for the token. A burn is an observable protocol mechanism; it is not a dividend guarantee, a valuation model or evidence that every holder benefits equally.

Hyperliquid's current USDC documentation describes native USDC issued on the network through Circle's HyperEVM contracts. It still documents a legacy Arbitrum bridge, but that bridge should no longer be treated as the entire stablecoin architecture. The distinction matters when analysing custody, transfer routes and contract risk: two assets with a similar dollar label can reach the trading account through different technical paths.

Circle announced native USDC and CCTP V2 on HyperEVM on September 16, 2025. In May 2026 it announced a further role as technical deployer for USDC as an aligned quote asset. Those are dated statements by the issuer and a commercial participant. They show integration and commitment; they do not remove issuer risk, guarantee redemption for every user or audit every application that subsequently accepts USDC.

The points programme began on November 1, 2023 and used weekly distributions. A later Layer 1 phase began in May 2024. Such repeated events gave early users a shared calendar: trading, comparing progress and waiting for the next distribution could become social habits as well as financial activity. The historical programme documentation is evidence of that organised participation, not a promise that another season will reward a new user's activity.

A community-maintained wiki uses the name The Hyper Liquidated and explicitly embraces cult language as part of its self-description. Its enthusiasm centres on traders, builders and users helping the ecosystem grow. This is useful cultural evidence precisely because it is attributed: a participant publication describes a particular identity. It cannot establish that every HYPE owner shares that identity, or that intense belonging is a substitute for independent judgement.

Hyper Foundation's 2024 retrospective highlights explorers, trading applications, regional groups and community-led collectives. These examples explain what supporters can actually contribute beyond posting price predictions: make data easier to inspect, organise people locally, improve trading interfaces and help newcomers understand the system. The account is promotional and selected by the Foundation, so it is evidence of recognised activities rather than a comprehensive census of unpaid work.

The node repository offers another form of participation: operating a non-validator node and producing data for applications. Its instructions include machine requirements and signed binary verification. Running infrastructure can reduce dependence on one hosted endpoint, but it requires resources and technical maintenance. The presence of a public operational repository should not be misrepresented as proof that every component's implementation has an equally complete public source release.

The official JELLY announcement says validators convened and voted to delist the perpetual market after suspicious activity. It also announced a Foundation-funded make-whole process excluding flagged addresses and promised improvements to voting transparency. This establishes that discretionary collective intervention was part of the response. It should be described as such, rather than rewritten as an entirely automatic outcome of immutable market rules.

In an April 2026 r/defi discussion, participants used this episode to question whether users of a decentralised exchange should accept emergency intervention. Replies also argued that solvency and orderly markets can justify difficult decisions. Those are competing participant judgements, not an audited verdict or a representative survey. Current delisting documentation provides a separate rulebook to inspect, including validator voting and a settlement-price methodology.

In a June 2025 essay, Jeff Yan argues that transparent order information can help market makers understand flow and compete to execute it. He distinguishes financial privacy from execution quality and acknowledges that the argument is controversial. This is a substantive founder thesis about market structure, not merely a slogan about decentralisation. Its evidence should be tested against execution costs and behaviour under stress, including cases that do not flatter the venue.

Users bring a less abstract test. A May 2026 community discussion asks about withdrawals and treatment of successful traders; respondents describe their experiences and raise infrastructure risks. These accounts show why reliability and predictable access matter to users deciding where to trade. Individual reports cannot prove universal availability, however. A convincing user case combines inspectable rules with observed performance over time, rather than treating either a good anecdote or a hostile anecdote as conclusive.

The official audits page identifies Zellic work on the legacy bridge and points separately to Circle's contracts. That scope is narrower than a claim that the entire network, every market and all HyperEVM applications have been audited as one system. Users need to identify the exact contract, software version and dependency involved in the action they are considering. An audit badge without that context can obscure more than it explains.

The practical research agenda follows the system's divisions: inspect validator participation, follow the market deployer's controls, identify the stablecoin route and review the application's own permissions. Hyperliquid's appeal lies in making a large amount of financial activity inspectable. Maintaining that appeal requires preserving uncomfortable evidence too, including interventions, operational restrictions and disagreement inside the community that helped the project grow.