Hyperfoundation supports the Hyperliquid blockchain and its ecosystem
Hyperfoundation supports the growth of Hyperliquid, a blockchain that combines native trading with an environment for smart contracts. Its work includes validator delegation, access to blockchain data, security reporting, and funding for policy research. HyperCore runs the native order books, while HyperEVM hosts applications that developers build on the network. HYPE underpins validator staking and pays for gas on HyperEVM. These roles distinguish the foundation’s programs from the trading protocol and individual applications.
Delegation gives selected validators additional backing
The delegation program backs selected validators to support network security and a more diverse validator set. Validators participate in consensus, the process that determines the network’s agreed transaction history. Selection considers performance, including testnet records when mainnet measurements are unavailable. The foundation monitors delegations and may end its support at any time.
An operator must hold 10 000 HYPE in one address before applying to the program. The minimum validator self-delegation of 10 000 HYPE has a one-year lock. Accepted operators must also run at least two non-validating nodes with 95% uptime and static addresses. Their node IP addresses are public because other nodes use them as connection points. Excluded jurisdictions include the United States and Ontario, and the foundation can change its eligibility criteria. Acceptance requires application review, identity or business verification, and agreement to the program’s terms.
Trading and applications share a chain with different execution rules
HyperCore and HyperEVM provide different execution capabilities within the same Hyperliquid blockchain, secured by HyperBFT consensus. HyperCore handles native spot and perpetual-futures order books. An order book matches buy and sell orders, and perpetual contracts provide derivative exposure without a fixed expiry. The protocol processes trading activity onchain, including order cancellations, margin state, and liquidations.
The EVM, or Ethereum Virtual Machine, is the execution model that HyperEVM uses for general-purpose smart contracts.
Smart contracts execute application logic on the blockchain. Developers can build financial applications with familiar EVM tools, alongside the native trading engine. Each application supplies its own contracts and interfaces, so its functionality depends on what its team implements.
Integration uses defined interfaces between the execution environments. The CoreWriter system contract lets HyperEVM contracts submit supported actions to HyperCore. This makes native trading functions available to application code within the actions that the protocol implements. Submission and HyperCore execution remain distinct events. Order actions and vault transfers through CoreWriter enter an onchain delay before execution.
Balances also belong to specific execution environments. Supported transfers move assets between HyperCore and HyperEVM, with token linking governing transfers for non-native assets. HYPE uses native-token handling. For other linked assets, the transfer mechanism expects an ERC-20 token contract and a token-specific system address. Transfers depend on the linked contract’s behavior and the token balance at the relevant system address. The protocol does not check that the linked contract is a valid ERC-20 or that the system address has enough tokens.
What does HYPE do within the ecosystem?
HYPE supports validator staking on HyperCore and pays transaction gas on HyperEVM. Delegation assigns staking weight to a validator, which influences its role in network consensus. Gas accounts for the resources that an EVM transaction consumes. Transaction demand affects gas pricing, so the required fee varies with execution and network conditions. Native trading has separate spot and perpetual fee schedules, maker and taker rates, and staking-based discount tiers. Holding HYPE, delegating it, and spending it on gas involve different uses and balance requirements.
Data peering depends on the access arrangement
The foundation’s non-validating peer helps infrastructure access Hyperliquid’s public blockchain data with fewer hops to validators. A non-validating node follows chain activity and can support local data services without voting in consensus. Timely order and fill data can support locally operated systems.
Direct access under the operator arrangement depends on staking, maker activity, reliable peering, and applicable access restrictions. Discretionary access also exists for qualifying ecosystem work that requires low-latency data, subject to the program’s other criteria. The foundation also accepts qualifying infrastructure providers whose peering services builders can use. Provider eligibility covers operating history, uptime, service capacity, and fair access. Requirements for connecting directly to the foundation’s peer differ from the terms that providers offer their own customers.
Direct foundation peering operates on a best-efforts basis, and the foundation can limit or discontinue access. Availability, latency, and data completeness remain material considerations for time-sensitive systems. The foundation’s node should not serve as their sole data source. Provider charges belong to the selected service, and public-data access does not ensure that another application’s transaction will execute successfully.
Security rewards follow the bug bounty’s scope
The bug bounty program rewards qualifying disclosures of vulnerabilities affecting Hyperliquid’s infrastructure. Its mainnet scope covers defects that would cause outages or logic failures in nodes or API servers. Researchers need reproducible findings and a proof of concept. A mainnet-impacting issue can qualify even though the program prohibits testing on mainnet. Testing belongs on testnet or local forks. Experimental testnet features require an explicit scope announcement.
Eligibility also requires identity or business verification and the ability to receive USDC on Hyperliquid. Rewards depend on classification, impact, and likelihood. Confidentiality applies to reports and related communications until authorized disclosure. Testing third-party applications and systems falls outside the program’s permitted activity, and contributors cannot claim rewards for the code that they helped develop.
Policy funding extends the foundation’s ecosystem work
The foundation also supports policy research through funding for the Hyperliquid Policy Center, a separate research and advocacy organization. The center launched in the United States on February 18, 2026. Its launch included a funding commitment of 1 000 000 HYPE from Hyperfoundation. The center’s work concerns regulatory frameworks for decentralized finance, including perpetual derivatives and blockchain-based financial infrastructure.
HyperCore, HyperEVM, and foundation programs serve different tasks
Native trading uses HyperCore, while deploying or using smart contracts involves HyperEVM and the chosen application’s requirements. Foundation programs add separate routes for validator operators, infrastructure providers, and security researchers.
- Choose native spot or perpetual order books for trading, and account for the applicable market’s fee schedule.
- Identify the application’s signing requirements and the HYPE balance that pays for its HyperEVM transaction gas.
- A validator seeking foundation delegation needs operator eligibility, identity checks, and acceptance of program terms.
- For blockchain data, distinguish a direct foundation peering application from a provider’s service and pricing.
- Security reporting requires an in-scope issue and reproducible evidence, with testing confined to permitted environments.
The chosen interface’s permissions, balance requirements, and execution rules determine whether the intended interaction can proceed.
What to know about Hyperfoundation
Is Hyperfoundation the same organization as Hyperliquid Labs?
Hyperfoundation is distinct from Hyperliquid Labs, which is a core contributor to the network’s development. The foundation supports ecosystem growth through its programs and funding commitments, including validator backing and policy-center funding.
Can builders run a non-validating node without joining a foundation program?
Running a non-validating node on Hyperliquid is permissionless. Access to the foundation’s own peer has separate eligibility requirements. A builder’s ability to operate a node therefore does not depend on acceptance into the foundation’s delegation program, although the selected peer or data service can impose its own access terms.
Does the foundation handle support for every HyperEVM application?
Support for a specific HyperEVM application belongs with the team that builds and operates it. Applications on the network come from separate teams. Their contract behavior, user interfaces, and support arrangements can differ, even when they use the same blockchain.
When was Hyperfoundation established?
Hyperfoundation was established in 2024 to support the growth of the Hyperliquid blockchain and its ecosystem.
What happens if several researchers report the same vulnerability?
The bug bounty program honors the first report when multiple researchers report the same vulnerability. That report must still meet the program’s scope, reproducibility, and eligibility requirements; submission order alone does not establish entitlement to a reward.
Updated: