Hyperliquid names Kraken parent Payward as its first would-be CFTC-regulated deployer

Hyperliquid said on Monday that it intends to make Payward — the parent company of exchange Kraken — the first CFTC-regulated deployer on its HIP-3 markets, a move the protocol framed as a path toward regulated U.S. perpetual futures trading. The announcement came in a post on X, reported by The Block.

The mechanics, as described: HIP-3 is an upgrade that lets a market's "deployer" restrict access through onchain allowlists. In Payward's case, Bitnomial — Payward's CFTC-regulated designated contract market and derivatives clearing organization — would act as the deployer. If approved, NinjaTrader Clearing, Payward's CFTC-registered futures commission merchant, would carry client accounts. Hyperliquid characterized itself as "a neutral infrastructure layer," saying deployers "retain control and responsibility for their own markets."

Nothing here is live for U.S. traders. The functionality exists on testnet, and the deployment is, in Hyperliquid's own words, subject to regulatory approval. How the permissioning would actually work — including whether a Payward market would build in KYC checks — was not spelled out.

The arrangement didn't appear from nowhere. Bloomberg reported in August that Payward was exploring a structure to route Hyperliquid-linked perpetuals to U.S. traders through Bitnomial; Payward formally announced the plan on Sept. 16, saying Bitnomial would handle deployment, clearing and settlement, subject to regulatory approval. Separately, the Hyperliquid Policy Center argued in an EU regulatory submission that regulated firms could use the protocol to run markets with leverage limits and onchain access restrictions.

Key facts

• Hyperliquid said Monday (Oct. 26, 2026) via X that it intends to make Payward its first CFTC-regulated HIP-3 deployer — reported by The Block, citing the post.
• Bitnomial, Payward's CFTC-regulated DCM and DCO, would be the deployer; NinjaTrader Clearing, a CFTC-registered FCM, would carry client accounts (The Block).
• The functionality is on testnet only; the deployment is subject to regulatory approval (The Block).
• Bloomberg reported the exploratory structure in August; Payward formally announced it on Sept. 16 (The Block).

The real-world read

Read the verbs. Hyperliquid "intends to" make Payward a deployer; the deployment "remains subject to regulatory approval"; the code runs on testnet. This is a statement of intent originating from Hyperliquid's own X post — not a launched product, not a regulator sign-off, not a trade executed. The most concrete operational question — whether a Payward-deployed market would actually enforce KYC — is unanswered. Note too the "neutral infrastructure layer" language: it's a positioning that places compliance responsibility on deployers while the protocol keeps its hands clean, which is convenient framing to view skeptically given it comes from the protocol itself.

Opinion, and whose

The claim that HIP-3's onchain allowlists and leverage limits can satisfy regulators is an argument made by the Hyperliquid Policy Center in an EU submission — a position from an interested party, not a regulatory finding.

This is news coverage, not financial advice.

Sources

• The Block (Tier 2, secondary), Oct. 26, 2026 — the full account, citing Hyperliquid's own X post (primary), Bloomberg's August reporting, and Payward's Sept. 16 announcement. No sponsored or marketing material was involved, though the underlying claims originate with Hyperliquid and Payward themselves.