Hyperliquid Regulation: Jeff Yan’s Deployer Model11 min read2,276 words

Hyperliquid Regulation: Jeff Yan’s Deployer Model

Jeff Yan says regulators should oversee firms deploying financial products on Hyperliquid, not the blockchain itself. Explore the stakes for U.S. markets.

Hyperliquid regulationJeff Yancrypto regulationCFTC oversightdecentralized trading
Hyperliquid Regulation: Jeff Yan’s Deployer Model

Who Should Regulators Oversee on Hyperliquid: The Network or Its Operators?

Crypto regulation often comes down to a deceptively simple question: who's actually running the financial activity? Hyperliquid founder Jeff Yan argues that U.S. regulators should focus on the firms that deploy financial products and operate markets on the blockchain - not on the underlying network itself.

The distinction matters because traditional financial companies are looking for ways to use blockchain tech. Kraken parent Payward plans to offer U.S. investors derivatives using Hyperliquid's technology through a regulated exchange, while Hyperliquid's own perpetual futures market remains unavailable to U.S. customers. That sets up a real-world test: can a regulated firm use blockchain infrastructure without the infrastructure itself turning into a regulated exchange?

Yan's argument isn't just about lighter rules. It's about where responsibility can realistically sit. This piece explains the deployer model, why it appeals to both crypto builders and traditional financial firms, where it breaks down, and what regulators would have to nail down for it to work in practice.

What Jeff Yan is proposing

Yan's core position is that regulatory duties should attach to the actors with meaningful control over the financial services - not to the blockchain infrastructure that the services use. In his words, "the regulation sits at the layer where there are controls," and deployers are the parties exercising those controls.

That's a practical separation between a network and a business running on top of it. A blockchain can provide transaction processing and shared infrastructure. A firm can use that infrastructure to offer a trading product, set customer terms, manage access, or operate a regulated market. Yan's point is that regulators should look at what the firm does - and what it can control - when deciding who has to follow financial rules.

Infrastructure is not the same thing as a trading business

The internet is a decent analogy, even if it doesn't map perfectly onto financial law. A financial company can use internet infrastructure without making the internet itself a broker, exchange, or bank. Yan's argument is similar: blockchain networks can function like underlying plumbing that supports applications, without being the entity that's offering a financial product to customers.

This shift matters because it moves the question from "Is there a blockchain here?" to "Who is doing what, and who can change or control it?" It also helps avoid treating every technical layer as if it carries the same duties as a customer-facing financial firm.

That said, the analogy doesn't settle the legal issue. Blockchain systems can work very differently: how transactions are ordered, how software is updated, who controls user interfaces, and whether anyone can restrict access. A network labeled "infrastructure" may still have influential operators or governance mechanisms. Labels alone can't answer who's responsible.

The proposal is about where obligations attach

Based on Yan's reported comments, he's not arguing that financial activity should be free from oversight. He's saying the rules should apply to the firms that deploy and control the activity. The basic distinction is this: "regulate the operator" isn't the same as "do not regulate the product."

In practice, a regulator would still have to examine what the business offers, who can access it, what risks it creates, and which laws apply. The unanswered part is whether the relevant operator can be identified - and whether it has enough control to actually carry out the obligations regulators would impose.

So the deployer model is really about regulatory design, not a way to dodge oversight. It works best when a responsible firm can be clearly identified and can implement the required controls. It gets harder when control is scattered, disputed, or limited by the system's own design.

Why the distinction matters for U.S. markets

The immediate relevance is the possibility that established financial firms can use blockchain technology while staying within familiar regulatory frameworks. CoinDesk reported that Payward, Kraken's parent company, plans to offer U.S. investors derivatives using Hyperliquid technology through a regulated exchange. At the same time, Hyperliquid's perpetual futures market remains closed to U.S. customers.

Taken together, those facts point to two different routes to market. One is the existing Hyperliquid platform, which doesn't serve U.S. customers. The other is a regulated operator using Hyperliquid technology to offer derivatives in the United States. That second route could let a company adopt parts of Hyperliquid's infrastructure without simply opening the existing platform to U.S. users.

Why a regulated operator may be a practical bridge

For a financial company, using new infrastructure doesn't remove its obligations to customers or regulators. A regulated operator can build an offering around the technology while using its own compliance processes, customer access rules, and operational controls. Whether a specific arrangement satisfies legal requirements still depends on how the deal is structured and what the law requires; the reported plan alone doesn't equal regulatory approval for every use case.

For the broader blockchain ecosystem, this approach could help institutional adoption move forward without forcing regulators to treat the entire network like a conventional exchange. Firms can evaluate the technology as infrastructure, while regulators focus on the entity responsible for the customer-facing product.

This separation could also make experimentation less risky. A firm can test whether the technology fits its operational needs without assuming every network participant must become a regulated intermediary. In real projects, the boundary matters: when responsibilities are fuzzy, legal uncertainty can stall deployment even if the technical system works.

What it does not establish

A regulated firm using blockchain technology doesn't automatically make every activity on that blockchain regulated, and it doesn't automatically make every activity compliant. It also doesn't mean the network is always beyond regulators' reach. The determining factors still include who controls the application, who can change its rules, how customers interact with it, and who can step in when something goes wrong.

The difference between "integrating technology" and operating a regulated market also matters. "Uses Hyperliquid's technology" doesn't, by itself, explain which parts Payward plans to use, how the offering will be structured, or what conditions will apply. Those details are what determine the actual regulatory picture - not the headline.

The broader point is straightforward: blockchain adoption by a regulated company is a specific business arrangement that has to be evaluated on its own facts. It isn't a blanket endorsement of the network or a generic statement about the legal status of decentralized finance.

The hard part: identifying control and responsibility

The deployer model sounds simple - until a regulator has to decide who qualifies as the deployer. Traditional financial firms typically have clear legal entities, management structures, and defined customer relationships. Blockchain applications can involve multiple parties: software developers, interface providers, governance participants, validators, liquidity providers, and companies offering products built on top.

Those parties don't necessarily have the same powers or obligations. A developer might publish software but not operate customer support. An interface provider could control how users reach a market without controlling the underlying protocol. A firm might make the commercial decisions while depending on infrastructure it doesn't own. Treating all these roles as interchangeable would be a shaky way to map accountability.

Control should be tested, not assumed

A practical assessment would start with questions like these:

  • Who sets the terms of the financial product?
  • Who decides which customers may use the service?
  • Who operates the interface customers actually use?
  • Who can pause, change, or restrict the relevant functionality?
  • Who handles customer communications, complaints, and operational incidents?
  • Which entity is responsible for compliance and recordkeeping?

These questions won't answer every legal issue, but they help separate technical contribution from operational responsibility. If a party can meaningfully control access or how the product behaves, regulators may see a different regulatory case than they would for a participant whose role is limited to open-source code and who can't direct how the service is used.

The toughest cases are the ones where power is split. If one entity controls onboarding, another controls the front end, and a third maintains a critical system component, regulators may need to look at the combined structure. And the reverse is also true: a protocol contributor shouldn't automatically be treated as a market operator just because its code shows up inside a financial product.

Decentralization does not remove the need for accountability

Decentralization describes how a system is organized; it doesn't automatically tell you who's responsible for a specific financial service. A system can be decentralized in technical ways while still having concentrated control at the interface, governance, or business layer. It may also lack a single actor with the authority to handle every task a regulator would expect from a conventional operator.

That's why a workable regulatory framework can't rely only on "centralized" versus "decentralized." It has to identify what activities are happening, which parties have practical control, and what risks the rules are meant to address. Otherwise, responsibility can end up assigned too broadly to infrastructure providers - or become hard to enforce when everyone points to someone else.

Yan's focus on deployers addresses part of that problem. It pushes regulators toward actors with actual controls. The remaining work is defining control in a consistent way and ensuring the identified entity can truly meet the obligations being attached to it.

What to watch next

The reported comments land amid ongoing attention to the U.S. regulatory status of crypto markets. CoinDesk noted that President Donald Trump said in August that the Commodity Futures Trading Commission was working to bring Hyperliquid into the United States under federal regulations. That statement and Yan's proposal provide useful context, but they don't add up to a published regulatory framework or a final decision about how any specific business will be treated.

The practical test will be whether a regulated operator can use the technology in a way regulators view as accountable and sufficiently controlled. That's narrower than asking whether a public blockchain should be regulated as an exchange. It's also more likely to be resolved through the details of a specific product than through general statements about the technology.

Signals worth monitoring

For institutions, developers, and users, these are the kinds of details that would clarify what's actually happening:

  1. The operating structure. Which legal entity offers the product, and what role does it play in the trading activity?
  2. The scope of the technology use. Which parts of Hyperliquid's technology are involved, and what does the regulated firm actually operate?
  3. Customer access and safeguards. How are eligible customers identified, and what processes govern access and support?
  4. Responsibility during incidents. Who can respond to outages, errors, or other operational problems, and how is that authority defined?
  5. Regulatory treatment. What requirements apply to the operator, and what - if anything - is expected of other participants?

These aren't predictions about how regulators will rule. They're the questions that determine whether the deployer model is more than theory. A workable architecture isn't enough if nobody can actually carry out the responsibilities assigned to the operator.

For crypto firms, the takeaway is to design accountability alongside the technology. For financial institutions, it's about checking where control really sits instead of relying on a broad claim that a system is decentralized. For regulators, the challenge is keeping responsibility clear without treating underlying infrastructure as if it were automatically the same thing as a customer-facing financial business.

Conclusion

Jeff Yan's proposal reframes the debate from whether a blockchain should be regulated like an exchange to whether the parties that actually control and operate the financial service are covered. It's a more practical starting point, but it isn't a complete answer. The deployer model depends on clear accountability, real control, and a close match between what the operator is required to do and what it can actually do.

Payward's reported plans are a concrete case to watch, but the details will matter more than the headline. Follow how the product is structured, what responsibilities fall on the operator, and how regulators treat the arrangement before concluding what this model means for U.S. crypto markets. For more context, read CoinDesk's report on Yan's comments and consult the CFTC's official resources.

Frequently Asked Questions

Yan argued that U.S. oversight should focus on financial firms deploying products and exercising control on Hyperliquid, rather than automatically regulating the underlying blockchain as an exchange. His proposal places responsibility at the layer where operational controls exist.
According to the source report, Hyperliquid’s perpetual futures market remains closed to U.S. customers. Separately, Payward, the parent company of Kraken, plans to offer U.S. investors derivatives using Hyperliquid technology through a regulated exchange.
No. Using blockchain technology does not establish regulatory compliance by itself. The operator, product structure, customer access, and controls all matter, and the applicable requirements depend on the specific arrangement and legal analysis.
In Yan’s argument, a deployer is a firm that puts a financial application or market into operation and exercises meaningful controls over it. The hard question is identifying which parties have enough practical authority to be responsible for particular obligations.

Related articles