Go to app

Executive Summary

Published 7/9/2026, 9:38:12 PM

Hyperliquid’s regulatory engagement is currently attempting to establish a precedent that technical transparency and lack of custody should exempt software developers from traditional financial registration. While the protocol has not yet secured a binding rule, its advocacy—alongside a pivotal 2026 CFTC no-action letter—has created a framework for "software-only" immunity that other non-custodial protocols are already citing.

Executive Summary

Hyperliquid’s strategy centers on the argument that on-chain immutability serves as a superior alternative to traditional market surveillance. As of July 2026, the Hyperliquid Policy Center (HPC) is pushing the CFTC to codify the "Phantom Precedent" (Letter No. 26-09), which granted temporary relief to non-custodial interfaces [Source: https://www.cftc.gov/PressRoom/PressReleases/9197-26]. However, this effort faces a significant counter-offensive from CME Group, which sued the CFTC in June 2026 to force Hyperliquid into a traditional registration framework [Source: https://www.tradingview.com/news/tradingview:ea6bc63c275f1:0-key-facts-cme-sues-cftc-urges-hyperliquid-reg-trading-outage/].


Key Regulatory Milestones and Precedents

Hyperliquid’s engagement with the CFTC has evolved from technical defense to active policy advocacy.

DateEventPrecedent/Argument Established
May 2025RFC ResponseTransparency as Compliance: Argued that HyperBFT consensus provides "verifiability typically absent in traditional financial systems" [Source: https://comments.cftc.gov/Handlers/PdfHandler.ashx?id=35635].
Mar 17, 2026CFTC Letter 26-09The Phantom Precedent: Granted no-action relief to a non-custodial wallet, stating that providing technical access does not require registration as an Introducing Broker (IB) [Source: https://www.cftc.gov/PressRoom/PressReleases/9197-26].
June 2026CME v. CFTCTradFi Pushback: CME Group sued the CFTC, specifically naming Hyperliquid's "offshore energy perpetuals" as a threat to regulated price discovery [Source: https://www.tradingview.com/news/tradingview:ea6bc63c275f1:0-key-facts-cme-sues-cftc-urges-hyperliquid-reg-trading-outage/].
July 9, 2026Joint HPC FilingSoftware Immunity: Hyperliquid and Phantom urged the CFTC to formally rule that software development without "ongoing control" does not trigger registration [Source: https://hyperliquidpolicy.org/cl/hpcphantomcftc-fintechrfi-response20260709.pdf].

The "Software-Only" Defense

The core of Hyperliquid’s legal argument is that the regulatory touchpoint should be the person performing a regulated function (e.g., a trader or a custodial intermediary), not the developer of the underlying open-source protocol [Source: https://cryptobriefing.com/phantom-and-hyperliquid-policy-center-urge-cftc-to-clarify-onchain-market-rules/].

The July 2026 filing proposes three specific pillars for non-custodial precedent:

  1. Registration Relief: Developing protocol software should not trigger registration if the developer lacks control over user funds.
  2. Interface Exemptions: Non-custodial front-ends should be exempt from exchange-trading requirements.
  3. On-chain Surveillance: Real-time, public data should satisfy the CFTC’s policy objectives for market resilience [Source: https://hyperliquidpolicy.org/cl/hpcphantomcftc-fintechrfi-response20260709.pdf].

Challenges to Precedent

The precedent is currently unresolved and contested. While the Phantom No-Action Letter provides a temporary shield, it is not a permanent regulation. The CME Group’s lawsuit argues that Hyperliquid’s "offshore" nature and its impact on domestic energy prices necessitate immediate enforcement action [Source: https://www.tradingview.com/news/tradingview:ea6bc63c275f1:0-key-facts-cme-sues-cftc-urges-hyperliquid-reg-trading-outage/].

Furthermore, the CFTC has not yet issued a formal rulemaking outcome on "software immunity." Until the commission moves beyond no-action letters to a codified rule, other non-custodial protocols remain in a state of "regulatory purgatory," relying on Hyperliquid’s advocacy to prevent a broader crackdown on DeFi interfaces.

Conclusion

Hyperliquid’s response has already set a procedural precedent by successfully securing a no-action letter for its partner (Phantom), but it has not yet established a legal precedent that protects all non-custodial protocols. The outcome of the CME lawsuit and the CFTC's response to the July 9, 2026, joint filing will determine if "software-only" immunity becomes a durable standard for the industry.