Hyperliquid entity primary sources — 2026-08-10

This file captures the primary-source packet used to split Hyperliquid’s protocol note from the named entity boundaries around Hyperliquid Labs and the Hyper Foundation.

1) Hyperliquid Labs as the named core-development organization

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors
• Why it matters: first-party statement that Hyperliquid Labs is a core contributor supporting the growth of Hyperliquid, led by Jeff and iliensinc.
• Key excerpts / claims:
  • The team previously did proprietary market making in crypto and then built Hyperliquid after deciding existing platforms had poor market design, bad tech, and clunky UX.
  • The docs explicitly frame Hyperliquid Labs as the named organization leading this work rather than as a generic anonymous contributor set.
  • The page says Hyperliquid Labs is self-funded and has not taken any external capital.

2) Hyperliquid Labs as the lead core-development boundary

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/hyperliquid-101-for-non-crypto-audiences
• Why it matters: strongest concise first-party statement that core development is led by Hyperliquid Labs.
• Key excerpts / claims:
  • Core development is led by Hyperliquid Labs, with multiple teams contributing to the blockchain and ecosystem.
  • The same page ties Hyperliquid’s chain, trading volume, HYPE buybacks, validator security, and builder-code ecosystem into one vertically integrated narrative.

3) Protocol-layer staking and validator structure

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/how-to-stake-hype.md
• Why it matters: confirms the user-facing staking flow and validator choice at the protocol/product layer.
• Key excerpts / claims:
  • Users move HYPE from Spot Balance to Staking Balance and choose a validator.
  • Staking and unstaking timings are documented as one-day lockup to unstake from a validator and seven days to return to Spot Balance.

4) Validator-set mechanics

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/validators/running-a-validator.md
• Why it matters: clarifies the permissionless validator story at the protocol layer.
• Key excerpts / claims:
  • Running validating and non-validating nodes is described as permissionless.
  • The active validator set is determined transparently based on the top twenty-seven by stake.

5) Hyper Foundation delegation and validator-admission policy

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/validators/delegation-program.md
• Why it matters: strongest first-party source for the Foundation as a distinct control-bearing entity.
• Key excerpts / claims:
  • The Hyper Foundation Delegation Program is designed to enhance network security, promote diversity, and support ecosystem growth.
  • The Foundation reserves the right to cease delegation at any time.
  • Eligibility includes 10k HYPE self-delegation, high-uptime public non-validator nodes, KYC/KYB, and jurisdiction restrictions.
  • The Foundation validators will strongly consider participation in the Delegation Program as a factor for trusting peer validators.

6) Hyper Foundation-operated low-latency access lane

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/nodes/foundation-non-validating-node.md
• Why it matters: shows the Foundation is not only a symbolic shell; it also operates an official node service.
• Key excerpts / claims:
  • The Hyper Foundation runs a non-validating node to provide reliable, low latency data access.
  • The node is offered on a best-efforts basis and may be modified, rate-limited, or discontinued at any time.
  • The docs say the node runs in apne1-az1 on AWS.

7) Official foundation identity and site mapping

• Source: https://hyperliquid.gitbook.io/hyperliquid-docs/support
• Why it matters: ties the docs to the official foundation website.
• Key excerpts / claims:
  • The support guide says The official Hyper Foundation website is https://hyperfoundation.org/.
  • The guide also distinguishes official Hyperliquid and Hyper Foundation accounts and warns users about lookalike domains.

8) Foundation website and terms shell

• Sources:
  • https://hyperfoundation.org/
  • client-side site assets fetched from the homepage on 2026-08-10 for text verification
• Why it matters: confirms the entity’s legal framing and its public token-governance messaging.
• Key excerpts / claims:
  • Homepage metadata describes Hyperliquid as the blockchain to house all finance.
  • Client-rendered homepage text includes Anyone can own, govern, and secure Hyperliquid through HYPE, the network's native token.
  • Client-rendered terms text identifies Hyper Foundation as a Cayman Islands foundation company.

Working conclusion

• hyperliquid should stay the protocol-layer note.
• hyperliquid-labs is justified because the docs explicitly say core development is led by Hyperliquid Labs.
• hyper-foundation is justified because the docs explicitly give the Foundation validator-delegation, validator-admission, and foundation-operated node responsibilities that matter separately from the protocol and lab layers.