Hyperliquid

What it does / key features

• The /index page is the primary product entry point for the Hyper Foundation brand and the Hyperliquid chain narrative.
• It frames the platform proposition: “The Blockchain To House All Finance” and a succinct problem statement: “Crypto is fragmented today, but it doesn’t need to be.”
• It functions as a routing hub into the rest of the ecosystem: trading app, developer resources, and ecosystem discovery.

Visible page elements & UI affordances

• Top navigation includes explicit route-level modules: “Stats”, “Docs”, “Ecosystem”, and “Launch App” (visible as header items).
• Primary CTAs in the hero:
  • “Start Trading” (intended to deep-link into the exchange application experience).
  • “Start Building” (intended to deep-link into developer onboarding/documentation).
• The hero copy also references the product anchor: “The flagship application: the premier exch…” (truncated in the preview, but clearly positioning a flagship exchange front-end).

Data points present

• No concrete metrics (e.g., TVL, volume, open interest, active wallets) are shown in the provided view of /index; “Stats” appears as a navigational destination rather than embedded KPIs.

Strategic significance

• This module is the funnel coordinator: it separates audiences into two high-value tracks—traders (Launch App / Start Trading) and builders (Docs / Start Building).
• By keeping the landing page lightweight (messaging + routing), it reduces friction and pushes users to specialized modules where the platform can enforce wallet connection, risk disclosures, and chain-specific onboarding.

What it does / key features

• The /genesisEventTerms page provides the legal wrapper for the “HYPER FOUNDATION Genesis Event Terms and Conditions.”
• It establishes the binding agreement for participating in the genesis event, explicitly tying acceptance to user actions.

Visible legal/functional mechanics

• The document header includes:
  • Title: “HYPER FOUNDATION Genesis Event Terms and Conditions”
  • Revision marker: “Last Revised on October 10, 2024”
• The opening acceptance clause is action-linked:
  • > “BY PARTICIPATING IN THE GENESIS EVENT, INCLUDING BUT NOT LIMITED TO CONNECTING A WALLET…”
  • This language indicates the platform treats wallet connection (or equivalent participation steps) as a legal acceptance event.

Interactive elements / forms

• This page is structured as long-form terms text; no visible input fields, tables, or calculators are indicated in the preview.
• Functionally, it supports other modules by being linkable during flows like:
  • genesis eligibility checks,
  • wallet connect gates,
  • claim/participation confirmations.

Data points present

• No numeric parameters (allocation sizes, schedules, caps) are visible in the provided excerpt; the value is in the compliance anchor and versioning.

Strategic significance

• Genesis events are high-risk from a regulatory and user-dispute perspective; this module creates a single canonical reference that other front-end flows can cite.
• The explicit mention of wallet connection as acceptance is important for front-end engineers: it implies the UI must surface links to these terms at every on-chain action that could be construed as “participation,” ensuring enforceable consent capture.

What it does / key features

• The /nftTerms page defines the contractual and IP/license rules for the “Hypurr NFT collection.”
• It clarifies what NFT holders own (token) versus what they are licensed to use (associated IP), and under what conditions.

Visible scope & on-chain specificity

• The document header includes:
  • Title: “Hypurr NFT Terms and License”
  • Revision marker: “Last Revised on September 11, 2025”
• Collection definition is explicit and quantitative:
  • “a set of 4,600 unique digital collectibles”
  • Represented by non-fungible tokens deployed on the Hyperliquid blockchain (“Hyperliquid”)
• It also states custody of IP:
  • “with associated intellectual property rights held by …” (holder entity text is truncated in the preview, but the ownership concept is explicit).

Interactive elements / forms

• Presented as a static legal page (terms + license). No visible mint UI, trait tables, or marketplace widgets appear in the preview.
• Practically, this page is intended to be referenced from:
  • NFT mint pages,
  • marketplace listings,
  • profile/collection views that show holder rights.

Data points present

• The primary concrete datum is supply size: 4,600 NFTs.

Strategic significance

• For an ecosystem that positions itself as a financial chain, a well-defined NFT license module reduces ambiguity for creators, holders, and integrators building marketplaces or using NFT imagery commercially.
• The explicit chain deployment (“Hyperliquid blockchain”) anchors the collection to the L1/L2 identity and supports ecosystem-native NFT tooling, while the revision date provides a governance/audit trail for license evolution.