Hyperliquid remains blocked in the U.S., not because the product cannot be accessed technically, but because its permissionless onchain design conflicts with how U.S. market structure law assigns regulatory duties. The policy push around the protocol now points to a more specific route: keep Hyperliquid as neutral infrastructure and let regulated entities use permissioned HIP-3 deployments on HyperCore to offer compliant access.
Reframing Hyperliquid as market infrastructure
Over the past year, most of the work around Hyperliquid has centered on changing how it is framed. Rather than presenting it simply as a decentralized perpetuals venue, the source describes it as modern market infrastructure: a globally accessible and composable platform for financial instruments spanning perpetuals, spot markets, and prediction markets.
That framing differs from vertically integrated crypto platforms such as Coinbase and BN, where user onboarding, custody, and trade execution are handled within one stack. Hyperliquid’s infrastructure layer is presented as closer to the separation of functions seen in traditional finance. A trading venue, or DCM, lists contracts and matches trades. A clearinghouse, or DCO, manages margin and settlement. A broker, or FCM, handles customer access and routes order flow.
Hyperliquid maps that same division onto a modular onchain stack. HyperCore acts as the trading and clearing layer, running matching, margin accounting, and settlement in protocol logic. It marks positions using validator oracles and liquidates through a deterministic liquidation waterfall. Deployers must post 500,000 HYPE as slashable collateral. They handle token listings, contract specifications, leverage caps, and oracle settings, and can keep up to 50% of the fees generated by their market. Builders fill a broker-like role by onboarding users and routing order flow into HyperCore in exchange for a share of trading fees.
The break from traditional structure is that these layers are rebuilt onchain and enforced in code. Market creation and access can be permissionless. Assets remain fully self-custodied. Other applications can build on top. Trading runs around the clock on a single global platform. That removes many of the geographic and legal separations found in traditional finance, but it also creates friction with the U.S. rulebook that was written for a different architecture.
Why U.S. rules collide with the protocol design
The source argues that Hyperliquid’s regulatory problem is structural. U.S. market structure law was built around traditional intermediaries, and each statutory registration category clashes in some way with the protocol’s base design.
- A designated contract market, or DCM, must comply with 23 core principles under Section 5(d) of the Commodity Exchange Act, including market surveillance and customer identification. HyperCore, by contrast, can be accessed by anyone with a wallet.
- A derivatives clearing organization, or DCO, must calculate margin using a board-approved model at a 99% confidence level and settle through approved settlement banks under 17 CFR §§39.13–39.14. HyperCore calculates margin through protocol logic and settles at the consensus layer.
- A futures commission merchant, or FCM, must segregate customer funds under Section 4d of the Commodity Exchange Act. Hyperliquid users self-custody their assets, which is far removed from the custodial FCM model.
The source uses Coinbase as an example of how demanding those rules are. Even with centralized KYC, a platform operating in the U.S. must register as an FCM and acquire an existing DCM for domestic business. Hyperliquid cannot copy that model without giving up the premise of reworking the underlying market infrastructure itself. Its response has been to geoblock the U.S. and step away from the world’s largest capital market.
What the Hyperliquid Policy Center is trying to change
The project is not positioned as permanently offshore. In February 2026, Hyperliquid announced the launch of the Hyperliquid Policy Center, or HPC, with 1 million HYPE in funding. The source values that allocation at about $72.5 million at current prices. Its stated goal is to bring this newer form of market structure into the U.S. legal framework.
In July, HPC and Phantom asked the Commodity Futures Trading Commission to confirm that publishing onchain software should not by itself trigger licensing requirements. They also argued that already licensed firms should be allowed to run matching, settlement, and margin functions on top of onchain infrastructure, and that a carveout should permit non-custodial wallets to route users to regulated derivatives products.
In August, HPC and TradeXYZ took the same logic to the Securities and Exchange Commission. Their filing addressed a framework for pre-IPO perpetual contracts, including instruments tied to companies such as SpaceX and Cerebras, both cited in the source as names already traded on Hyperliquid. The proposal also included disclosure and eligibility standards needed to open those products to U.S. investors.
The source says early signs suggest the strategy is gaining traction and that the U.S. regulatory stance appears open. It points in particular to Trump’s statement that Chair Selig planned to push Hyperliquid onshore.
The compliance theory behind the proposal
HPC is not asking for Hyperliquid’s native, non-KYC front end to be opened directly to U.S. investors. Its argument is narrower. Hyperliquid should be treated as neutral infrastructure, and if a U.S. company can satisfy the compliance duties imposed by current law while using that infrastructure, then Hyperliquid should be available as an option alongside a traditional DCM stack.
Under that framework, a broker that fulfills KYC obligations could route customer order flow into HyperCore. A deployer could also take on the role expected of a registered trading venue, keeping discretion over listings, handling market surveillance, and exercising emergency powers when needed. The compliance burden sits with the entity providing access, while the protocol remains the underlying venue and clearing logic.
Permissioned HIP-3 deployments on testnet
As the Washington effort has moved forward, Hyperliquid Labs has pushed testnet updates that make this approach technically possible. The clearest example in the source is the new class of permissioned HIP-3 deployers.
Unlike Hyperliquid’s native markets and existing HIP-3 deployments, which are open, these new deployments are limited to whitelisted users. That creates a more concrete path for regulated firms to launch markets, run KYC, and admit only approved users to a trading whitelist.
Those compliant venues would show up as fragmented order books because each market, whether in BTC or real-world assets, would need to be relisted. But the source says whitelisted market makers could bridge liquidity between the two books, reducing fragmentation. New deployments would therefore keep their own order books while still inheriting Hyperliquid’s deeper liquidity.
The article notes that separate order book structures are not new. It points to early BN US and Lighter’s current deployment on Robinhood Chain as precedents. Hyperliquid’s difference is that both markets run on the same L1 and share collateral and margin. There is no need to move between chains or across separate trading venues, so liquidity can move between books rather than being trapped in silos.
PA permissions and account control
The compliant setup also includes other controls. The source highlights the “PA” permission in the payload, which lets a DEX act directly on a user account by submitting reduce-only orders, canceling orders, and moving USDC within the DEX.
That is compared in the article to the close-out authority an FCM holds over customer accounts. Taken together with permissioned HIP-3 deployments, these controls are presented as the toolset needed for U.S. brokers and institutions to build compliant Hyperliquid products on HyperCore.
The source is also explicit that this path is additive, not substitutive. Hyperliquid’s native markets would remain permissionless. The protocol’s role as neutral infrastructure would stay intact even if regulated access layers are built on top.
Research view in the source
The article’s closing view is that Hyperliquid’s recent moves in Washington show that compliant entry into the U.S. market is now the central priority. At the same time, it says the native non-KYC front end cannot be operated compliantly for U.S. investors under current law.
Its conclusion is that HPC has outlined a route to KYC-compliant access: firms that provide the access layer would fully meet regulatory requirements while using Hyperliquid underneath. With permissioned HIP-3 deployers and PA account controls now appearing on testnet, the path for U.S. investors to reach Hyperliquid markets through a compliant channel is becoming more concrete, while the protocol itself stays positioned as neutral infrastructure.