Hyperliquid HIP-3 Gets Its First CFTC-Regulated Deployer: Payward's Permissioned Perps

Hyperliquid HIP-3 now has a named CFTC-regulated deployer in line. On October 26, Hyperliquid said in a post on X that it intends to make Payward, the parent company of Kraken, the first CFTC-regulated deployer of HIP-3 markets, with the goal of offering regulated perpetual futures to U.S. traders, according to The Block. The plan is still subject to regulatory approval, and no date has been given.

The detail that matters for orderflow is where the trades would print. Under the structure described by crypto.news, contracts would be listed under a U.S. exchange's rules, but matching and recording would happen on Hyperliquid's public order book. That makes it the first proposed case of regulated U.S. flow running through an onchain book that anyone can read.

Hyperliquid HIP-3 and the Payward Structure: Who Does What

Three entities split the job. Bitnomial, Payward's designated contract market (DCM) and derivatives clearing organization, would act as the HIP-3 deployer and handle clearing and settlement. NinjaTrader Clearing, Payward's CFTC-registered futures commission merchant, would carry client accounts if the plan is approved, per The Block.

Bitnomial received DCM status in April 2020, and the proposed contracts would be listed under Bitnomial Exchange's rules, with regulatory obligations sitting with the named exchange, clearinghouse and brokerage entities, according to crypto.news. Payward closed its acquisition of Bitnomial on May 1, in a deal initially valued at up to $550 million in cash and stock.

The plan has been public for a while. Bloomberg reported in August that Payward was exploring a route to Hyperliquid-linked perps through Bitnomial, and Payward announced it formally on September 16, per The Block. What changed on October 26 is that Hyperliquid itself named Payward as the intended first regulated deployer, describing the chain as "a neutral infrastructure layer with the goal of supporting large parts of the financial system."

HIP-3 Permissioned Markets: Allowlists on a Public Book

The mechanism that makes this possible is a new optional feature. HIP-3 adds an onchain allowlist managed by the deployer or by sub-deployers it appoints. Existing markets stay unchanged, and each deployer decides whether to use it. An initial release is on testnet with preliminary specifications, and support for the deployer configuration on mainnet would come in a future network upgrade, per crypto.news.

For the Payward markets, a customer would need to complete onboarding with NinjaTrader and appear on both NinjaTrader's and Bitnomial's allowlists before trading. Access requires a futures account with the registered broker, according to the same report. The Block notes it is still unclear how permissioning will work in practice, including whether a Payward market would carry built-in KYC checks.

For a trader reading the tape, the split is clean. Who can submit orders would be restricted. What those orders do would not be hidden, because fills land on a public chain. If the structure goes live as described, fills, sizes and addresses from a regulated U.S. channel would be readable by anyone watching the chain, the same way main-book Hyperliquid flow is today.

Separate Books, Separate Margin: Why This Is Not One Pool

A Payward market would not share liquidity with the main Hyperliquid perps. Under Hyperliquid's HIP-3 documentation, as summarized by crypto.news, each builder-deployed perp exchange has independent margining, order books and settings. Deployers set market definitions, contract specifications, oracle prices and margin limits.

That has direct consequences for orderflow. If Bitnomial lists a Bitcoin perp, it would be a separate market from the existing BTC perp on Hyperliquid, with its own depth, its own funding and its own open interest. Any gap between the two prices becomes a readable signal of whether allowlisted U.S. accounts are leaning harder in one direction than the open market.

Deployers also hold controls that the main book does not expose to them. A deployer can halt trading in an asset, cancel its orders and settle positions at the current mark price, then resume later. The documentation lists a 500,000 HYPE mainnet staking requirement for deployers, held for at least 183 days after deployment. The October post did not give separate staking terms for Payward, per crypto.news.

The idea is not new for Hyperliquid's policy work. On October 1, the Hyperliquid Policy Center told EU regulators that regulated firms could run markets on Hyperliquid with onchain access restrictions, according to The Block. Co-founder Jeffrey Yan described deployer-managed participant lists on September 3, per crypto.news. The Buildix blog covered his position in Jeff Yan Wants U.S. Rules on Deployers, Not the Chain.

Where Hyperliquid Volume and Open Interest Sit Before U.S. Flow

The starting point is a dominant open interest share and a smaller volume share. On October 25, Hyperliquid held $7.57 billion of open interest, 57% of the $13.38 billion tracked across 49 onchain perp venues, down 9.0% over 30 days, according to Castle Labs, which sources open interest from DefiLlama.

Volume tells a narrower story. Hyperliquid printed $4.98 billion over 24 hours, 42% of tracked DEX volume. Binance futures traded $38.08 billion over the same window, so Hyperliquid ran at about 13% of Binance, per the same Castle Labs data. Open interest that is large relative to volume points to positions that are held rather than churned.

A regulated U.S. channel would not change those numbers on day one. The markets would be new, separate books, and the allowlist requirement caps who can enter. The useful question for the first months is whether that capped flow trades with more conviction than the open market, and that shows up in depth and delta long before it shows up in a volume ranking.

What to Watch Before the First Regulated HIP-3 Market Goes Live

Three checkpoints decide the timing. First, the network upgrade that moves the deployer allowlist configuration from testnet to mainnet. Second, regulatory approval for the Bitnomial deployment and the NinjaTrader account structure, for which The Block reported no expected date. Third, the specific contracts listed, which neither report names yet.

Once a market is live, the work is comparative. Track the spread between the Bitnomial contract and the matching main-book perp, compare open interest growth in the two, and watch whether cumulative volume delta on the permissioned book leads or lags the open one. A permissioned book that consistently leads is telling you where the informed flow sits.

Buildix covers HIP-3 markets next to the main Hyperliquid perps, so new deployer books can be compared on the same screen. The screener ranks markets by open interest change, funding and delta, and each pair page shows CVD, order book imbalance and whale activity for spotting which book moves first.

The real test of a regulated HIP-3 market is not the headline. It is whether allowlisted U.S. flow prints on Hyperliquid's book with enough size to move price, and that will be visible onchain before any press release reports it.