Skip to content
Regulation & PolicyLatest

Chervinsky: Hyperliquid is Infrastructure, Not Exchange

MissedBlock Desk · · 3 min read

Updated

Chervinsky: Hyperliquid is Infrastructure, Not Exchange

Hyperliquid CEO Clarifies Protocol’s Role as Infrastructure, Not Exchange

Jake Chervinsky, CEO of the Hyperliquid Policy Center, has sought to clarify the nature of the Hyperliquid protocol, asserting that it does not operate as an exchange. Speaking at TOKEN2049 in Singapore, Chervinsky described the protocol as neutral public infrastructure upon which anyone can build trading products.

While this distinction might appear semantic, in the realm of cryptocurrency regulation, such definitions can determine licensing requirements.

In an interview on October 7, Chervinsky explained that Hyperliquid’s protocol functions beneath the customer-facing platforms that traders directly interact with, positioning it “one level below” established exchanges like Coinbase and Kraken. He emphasized that the network is “not meant to compete” with these existing businesses.

Under this framework, regulated entities, including traditional exchanges, can develop their own products utilizing Hyperliquid’s technology. The exchange component would manage customer interactions, onboarding, and compliance, while the protocol would handle the underlying technical infrastructure.

Chervinsky drew parallels to well-known blockchain networks, likening Hyperliquid’s infrastructure to Bitcoin and Ethereum. He argued that, similar to these foundational networks, Hyperliquid does not require registration as an exchange.

Beyond definitions, Chervinsky offered a forecast contingent on the success of this model. He predicted that within a decade, all significant exchanges, whether crypto-native or traditional, would need to adopt public blockchain infrastructure to remain competitive. He cited transparency, resilience, and cost-effectiveness as the key advantages supporting this outlook.

Chervinsky also indicated that onchain markets are anticipated to operate under U.S. regulatory frameworks in the near future.

On October 8, Chervinsky further elaborated on Hyperliquid’s role as financial infrastructure at TOKEN2049, participating in a discussion with representatives from HyperliquidX and ICE (Intercontinental Exchange).

The Hyperliquid Policy Center was established in February 2026 as a nonprofit organization dedicated to advocacy and research concerning onchain markets and perpetual derivatives. Perpetual derivatives, or “perps,” are futures contracts without an expiration date, allowing traders to maintain leveraged positions on asset prices through ongoing funding payments. This feature has made perps one of the most actively traded products in the cryptocurrency space.

The center’s operations are supported by a donation of 1 million HYPE tokens from the Hyperliquid Foundation, a contribution valued at approximately $28-29 million.

In September 2026, Payward, the parent company of Kraken, announced its intention to offer permissioned perpetual futures on Hyperliquid to eligible U.S. customers. This arrangement combines public blockchain technology with an integrated compliance layer. Kraken would be responsible for managing user access and rule enforcement, while Hyperliquid would facilitate the market operations.

For Hyperliquid, this infrastructure-centric approach serves as both a technical description and a regulatory strategy. By being classified as infrastructure akin to Bitcoin or Ethereum rather than an exchange, the protocol can sidestep exchange registration requirements, shifting the compliance burden to the businesses building upon it. This division of responsibilities enables initiatives like Payward’s plan, allowing regulated firms to access an onchain order book without the protocol itself needing to become a regulated entity.

The next developments to monitor will be whether other exchanges follow Payward’s lead and how U.S. regulators respond to these evolving models.

Chervinsky: Hyperliquid is Infrastructure, Not Exchange · MissedBlock