Hyperliquid founder Jeff Yan has called on regulators to direct enforcement at the individuals and teams who deploy applications, rather than at the underlying blockchain protocols they build on, CoinDesk reports. The remarks place one of the most closely watched executives in decentralized finance squarely inside a live policy debate: who bears liability when permissionless infrastructure carries a违规 or failed application.

Yan's position, as reported by CoinDesk, is that the base blockchain is neutral infrastructure. Responsibility, in his framing, should attach to deployers — the named parties who ship code, control upgrade keys and set parameters. The argument echoes a long-running line of defense used across the crypto industry: prosecute the operator, not the network.

That distinction carries real operational weight. Hyperliquid itself runs a fully on-chain perpetuals venue on its own layer-1 chain, a structure that has attracted regulatory attention before. If supervisors accept the deployer-liability framing, teams behind token launches and trading front-ends absorb the legal risk; if they reject it, base-layer validators and core developers remain exposed. Yan did not, according to the report, specify which regulator or jurisdiction he was addressing — a gap worth noting.

Why the deployer-versus-protocol question matters

Regulators in the United States and Europe have so far avoided a clean answer. Enforcement actions have variously targeted foundations, token issuers, exchanges and, in some cases, individual developers. A deployer-first standard would in theory narrow that surface: liability would follow whoever controls the contract at deployment, not whoever maintains the chain beneath it.

Skeptics will read Yan's argument as self-protective. Hyperliquid's growth depends on the perception that its chain is neutral plumbing; a liability shield for base layers shifts exposure onto third-party application teams building on top. The report does not record whether Yan addressed the obvious counterpoint — that some deployers are anonymous, making them poor enforcement targets.

What was not said

According to the CoinDesk report, Yan framed the issue at the level of principle. The account includes no specific legislative proposal, no named agency and no jurisdiction. It also does not indicate whether he discussed Hyperliquid's own compliance posture or its handling of past incidents on the platform. Those omissions matter; a founder's policy pitch is only as strong as the enforcement detail left unspecified.

For market structure, the stakes are straightforward. Clear deployer liability would push professional teams toward registered entities and audited deployments, while leaving truly decentralized front-ends in a gray zone. Anything short of that keeps the ambiguity — and the enforcement discretion that comes with it — in place.

The debate will test whether supervisors can be persuaded by an infrastructure-liability argument that the industry has made, largely unsuccessfully, for a decade. Absent statutory change, the working standard remains whatever the next enforcement action decides it is.