Who is Jeff Yan? Hyperliquid founder

Jeff Yan is a cofounder of Hyperliquid, a project developing a trading market and the blockchain network running it. His team addressed a difficulty familiar to users: combining a fast interface with a verifiable record of operations.

Designing a market and its infrastructure together is an ambitious choice. It allows the full experience to be addressed while requiring responsibility for more layers of the system. The order book, the dedicated network and the environment for other developers help explain what the team set out to build.

Who is Jeff Yan?

Jeff Yan co-founded Hyperliquid and leads Hyperliquid Labs alongside iliensinc. The project documentation identifies them as former Harvard classmates. Iliensinc participates publicly under that pseudonym.

The same source places the team in proprietary market making in 2020 and its expansion into DeFi in summer 2022. That background matters: they had used trading infrastructure and understood the problems they wanted to solve. The documentation describes the team’s collective experience rather than attributing every previous position to Yan.

What problem did Hyperliquid address?

In an order-book market, participants specify how much they want to buy or sell and at what price. Placing, changing and cancelling orders quickly is part of the product. Moving those operations onto a public network requires coordinating execution, state and consensus while preserving a usable experience.

Hyperliquid approached that coordination as a whole-system problem. Instead of simply adapting an interface to existing infrastructure, the team developed an L1 designed around markets. The value of that choice should be assessed through operation, resilience and observable guarantees, rather than a maximum transactions-per-second figure alone.

This differs from the approach Hayden Adams popularized with Uniswap. An AMM calculates swaps against reserves according to a rule; Hyperliquid uses order books. These are different liquidity models with different execution and risk-management requirements.

HyperCore: markets within the network

HyperCore is the part of Hyperliquid incorporating spot and perpetual futures markets. The order book belongs to its state and execution rules, rather than existing solely as a private database behind a website.

That makes market activity inspectable, but does not make every dependency equivalent. Reference prices, liquidation rules, network connections and interfaces have distinct functions. An order sent from a screen is also different from a transaction that the chain has included and executed.

Perpetuals are derivatives without a fixed expiry. They involve margin, funding payments and possible liquidation. On-chain visibility makes these operations inspectable, but a position can still be liquidated under the market’s rules.

HyperEVM: from product to platform

HyperEVM adds an Ethereum Virtual Machine-compatible environment within Hyperliquid. It shares HyperBFT consensus with HyperCore; it is not an Ethereum rollup or a second network that automatically inherits Ethereum’s security by running compatible contracts.

Compatibility allows developers to reuse tools and languages. The project describes mechanisms for interacting with HyperCore state, although each integration must check which capabilities are actually enabled and their limits. Documentation of a planned feature does not establish availability in every version or environment.

This transition matters in Yan’s career. The objective extends beyond a trading screen to infrastructure on which other teams can build applications. That requires documentation, tooling and integration rules alongside performance.

Funding, the team and control

Hyperliquid Labs states in its documentation that it is self-funded and has taken no external capital. This is the team’s account of its financing, not sufficient evidence that power is broadly distributed. A token, a foundation or validators likewise do not establish an even distribution of influence by themselves.

Hyperliquid Labs, the Hyper Foundation, the protocol and HYPE should be distinguished. Labs contributes development; the foundation supports the ecosystem; the network executes its rules; and the token has functions within it. Buying HYPE is not equivalent to owning shares in Labs or receiving a personal guarantee from its founder.

Assessing effective control means checking who operates validators, how upgrades are adopted and what incident-response mechanisms exist. Market rules matter too: the liquidation documentation explains that the mark price combines external prices with the state of the order book. That specific dependency says more about the design than the word decentralized on its own.

Jeff Yan’s contribution to DeFi

Yan and his collaborators have treated market experience and network architecture as parts of the same problem. Hyperliquid illustrates a design direction in which an initial application justifies building specialized infrastructure that can subsequently support other products.

Its progress should be measured by more than popularity or volume: transparent rules, integration quality, operation under stress and the ability to sustain an ecosystem beyond one person. Those questions make it possible to assess a founder’s work while the project continues to change.