Hyperliquid remains geoblocked in the United States because its permissionless on-chain infrastructure clashes with U.S. market structure law, which confines futures trading to registered trading venues, clearinghouses, and brokers. The MarsBit report says Hyperliquid Policy Center has urged the Commodity Futures Trading Commission and the Securities and Exchange Commission to update those frameworks so regulated firms can build on HyperCore through builder and deployer seats while taking on the compliance obligations themselves.
In the report’s account, that makes permissioned HIP-3 DEX deployments a likely route for bringing Hyperliquid onshore in the U.S., especially after what it describes as confirmation from statements by Trump.
Recasting Hyperliquid as market infrastructure
Over the past year, much of the work around Hyperliquid has focused on redefining it from a decentralized perpetual futures exchange into what the article calls modern market infrastructure. In that framing, it is a globally accessible and composable platform for financial products spanning perpetuals, spot, and prediction markets.
The report contrasts that structure with vertically integrated crypto platforms such as Coinbase and BN, where onboarding, custody, and execution sit under one roof. Hyperliquid’s infrastructure layer is presented as closer to the division of responsibilities seen in traditional finance. In that setup, a designated contract market, or DCM, lists contracts and matches trades; a derivatives clearing organization, or DCO, manages margin and settlement; and a futures commission merchant, or FCM, handles customer onboarding and trading access.
Hyperliquid’s modular stack mirrors that same split. HyperCore, which functions as the trading venue and clearing layer, runs matching, margin accounting, and settlement at the protocol level. It marks positions using validator oracles and liquidates through a deterministic liquidation waterfall.
Deployers must stake 500,000 HYPE as slashable collateral. They are responsible for token listings, contract specifications, leverage caps, and oracle settings, and can keep as much as 50% of the fees generated by their markets. Builders act in a broker-like role, bringing in users and routing order flow to HyperCore in exchange for part of the trading fee stream.
What separates Hyperliquid from the conventional model is that these layers are rebuilt on-chain and enforced through code. Access and market creation can be permissionless, users self-custody assets, third-party applications can build on top, and assets trade on a single global venue around the clock.
Where U.S. rules collide with the protocol design
The article argues that Hyperliquid’s biggest obstacle is regulatory fit. U.S. market structure law was written for traditional architectures, and each statutory registration category conflicts in some way with Hyperliquid’s design.
- DCMs must comply with 23 core principles under Section 5(d) of the Commodity Exchange Act, including market surveillance and customer identification, while anyone with a wallet can access HyperCore.
- DCOs must calculate margin using board-approved models with a 99% confidence level and settle through approved settlement banks under 17 CFR §§39.13–39.14, while HyperCore computes margin through protocol logic and settles at the consensus layer.
- FCMs must segregate customer funds under Section 4d of the Commodity Exchange Act, whereas Hyperliquid users self-custody.
The report says these requirements are strict enough that even Coinbase, despite using centralized KYC, had to register as an FCM for its U.S. business and acquire an existing DCM. Hyperliquid cannot simply copy that route because buying a DCM and conforming to the legacy framework would run against its goal of reworking the underlying infrastructure. As a result, it has chosen to geoblock itself from the world’s largest capital market.
HPC’s policy campaign in Washington
The report says Hyperliquid does not plan to stay offshore forever. In February 2026, it announced the creation of Hyperliquid Policy Center, or HPC, and committed 1 million HYPE to the effort, valued in the article at about $72.5 million at current prices. The goal is to bring this new market structure inside the U.S. legal framework.
In July, HPC and Phantom asked the CFTC to confirm that publishing on-chain software does not by itself trigger licensing requirements. They also argued that existing licensed firms should be allowed to run matching, settlement, and margining on top of on-chain infrastructure, and that non-custodial wallets should be able to route users to regulated derivatives under an exemption.
In August, HPC and TradeXYZ brought the same logic to the SEC. The filing outlined a framework for pre-IPO perpetual contracts, including products tied to companies such as SpaceX and Cerebras that the article says are already trading on Hyperliquid, along with the disclosure and eligibility rules needed to offer those markets to U.S. investors.
MarsBit says early signs suggest the strategy is gaining traction and that regulators in the U.S. are showing openness. The clearest signal cited in the piece is Trump’s announcement that Chair Selig planned to push Hyperliquid onshore.
HPC is not arguing for direct access to Hyperliquid by U.S. investors without KYC. Its position, as described in the report, is that Hyperliquid should be treated as neutral infrastructure. If U.S. firms can meet the obligations imposed by current law while using it, then it should stand alongside a traditional DCM as an available option.
Under that model, a broker that fulfills KYC duties could route client flow to HyperCore. A deployer could also take on functions associated with a registered trading venue, including discretion over listings, market surveillance, and emergency intervention.
Permissioned HIP-3 deployments on testnet
As policy work continues in Washington, Hyperliquid Labs has rolled out testnet updates that, in theory, could support compliant access. The clearest example is a permissioned HIP-3 deployer.
Unlike Hyperliquid’s native markets and the existing open HIP-3 deployments, these new deployments are open only to whitelisted users. For regulated entities, the report says, that creates a straightforward route to list markets, run KYC, and place compliant users on a trading whitelist.
Those compliant venues would have separate order books because every market, including BTC and real-world asset markets, would need to be relisted. The article says whitelisted market makers would bridge liquidity across the two books, reducing fragmentation and allowing the new venues to draw on Hyperliquid’s deeper liquidity even while keeping distinct books.
The piece notes that separate-book structures have precedents, citing early BN US and Lighter’s deployment on Robinhood Chain. The difference here is that both markets on Hyperliquid run on the same Layer 1, share collateral and margin, and do not require cross-chain or cross-venue movement. In that setup, liquidity can move between books instead of being isolated.
PA permissions and the broker-like control layer
The article also highlights another parameter in these trading venues: a payload-level “PA” permission that allows a DEX to act directly on user accounts. That includes placing reduce-only orders, canceling orders, and transferring USDC within the DEX.
The report compares that capability to the close-out authority an FCM holds over customer accounts. Taken together, these tools are presented as the building blocks for U.S. brokers and institutions to create compliant Hyperliquid products on HyperCore.
At the same time, the article says this is an additive option rather than a replacement. Hyperliquid’s native markets would remain permissionless, and the protocol’s identity as neutral infrastructure would stay intact.
Research view in the report
The piece closes by saying Hyperliquid’s recent moves in Washington show that compliant entry into the U.S. market is now a core priority. It also states just as plainly that operating in the U.S. through the project’s native non-KYC front end would not comply with current law.
Its conclusion is narrower than a full market opening: firms that provide access and fully satisfy regulatory requirements may be able to use the Hyperliquid backend. With permissioned HIP-3 deployers and PA account controls now live on testnet, the report says that path is starting to look operational for compliant access by U.S. investors.