Hyperliquid Unveils HIP-3* Permissioned Perpetual Futures Framework with Payward as Intended CFTC-Regulated US Deployer

The move creates an institutional blueprint for routing regulated US derivatives through onchain order books by isolating compliance requirements entirely within deployer-controlled smart contract layers.

• A compliance-focused architecture went live: On October 26, 2026, Hyperliquid introduced HIP-3*, an additive framework enabling permissioned perpetual futures markets using optional onchain allowlists while maintaining the underlying decentralized layer-1 order book.
• Payward stepped up as anchor deployer: Payward, the parent firm of Kraken, signed on as the prospective initial CFTC-regulated deployer, using its subsidiaries Bitnomial and NinjaTrader Clearing to handle clearing, settlement, and customer onboarding.
• The product entered testnet: The technical standard launched in a testnet environment, establishing the legal and technical baseline needed to seek pending Commodity Futures Trading Commission (CFTC) approval before any mainnet deployment.

• Onchain market appetite is already proven: Builder-deployed perpetuals under the earlier HIP-3 standard generated 26.7% of Hyperliquid’s volume—accounting for roughly $17.27 billion of its $64.7 billion total volume over the 30-day window ending October 20, 2026.
• A multi-step institutional integration: This update follows a formal September 16, 2026, agreement between Payward and Hyperliquid to explore compliant US perpetual contracts, capitalizing on Payward’s ownership of CFTC-licensed infrastructure via Bitnomial.
• Strictly additive code architecture: HIP-3* leaves existing permissionless contracts completely untouched, layering secondary compliance controls exclusively over newly spun-up, dual-allowlisted institutional markets.

The traditional model of digital asset compliance has historically demanded a binary choice: either an exchange operates offshore to offer flexible perpetual futures, or it restricts its catalog to basic spot and dated futures under strict domestic rules. The HIP-3* deployment breaks that binary model by using modular onchain architecture to solve a regulatory problem.

Instead of altering Hyperliquid's core consensus or forcing the protocol into an onshore corporate registration, the HIP-3* proposal places the entire compliance burden onto external deployers. Payward operates as an institutional buffer between US traders and onchain liquidity. Under this structure, Bitnomial oversees the creation, administration, clearing, and trade settlement of contracts on Hyperliquid's execution engine. Concurrently, NinjaTrader Clearing maintains customer relationship accounts, onboarding, and identity screening.

Participants interact with the platform only if they are dual-allowlisted by the operating entities. For the protocol, the trades execute like any other deterministic order against an onchain order book. For regulators, every counterparty in the permissioned pool is identified, verified, and backed by a CFTC-regulated clearinghouse.

This incentive structure serves both sides. For Hyperliquid, it provides access to US capital pools that were previously locked out by regulatory enforcement, without needing to impose identity checks on its existing global, permissionless user base. For Payward, it enables the monetization of its regulated clearing licenses by capturing retail and institutional perpetual futures flow directly on decentralized rails.

The strategy also answers a clear economic reality within the platform. With permissionless HIP-3 markets already capturing 26.7% of the platform's $64.7 billion rolling monthly volume, demand for tailored, isolated contract deployments is already demonstrated. HIP-3* standardizes this setup for regulated entities.

The primary structural implication is architectural segmentation. Regulated firms do not need dedicated, proprietary central limit order books to offer compliant derivative access. They can clear trades directly through public, decentralized blockchain infrastructure, as long as the permissioning checks live securely at the smart contract deployment boundary.

• US-based derivatives desks: Institutional traders gains a viable pathway to access onchain perpetuals without violating federal regulations or relying on offshore corporate vehicles.
• Decentralized exchange infrastructure operators: Platform architects must adapt to an environment where protocol success hinges on running dual-track models that support open access alongside permissioned institutional layers.
• CFTC-licensed intermediaries: Clearing firms and brokerages with established US licenses unlock a new business model acting as compliance gateways for decentralized execution engines.
• HYPE token holders: Protocol stakeholders see token dynamics increasingly influenced by onshore institutional volume and regulatory approval timelines, as demonstrated by the token's brief move past $80 to settle near $79.65 after the release.

• CFTC formal feedback: Watch for public statements, approval notices, or requests for comment from the CFTC regarding Bitnomial's clearing model on decentralized protocols, which will determine actual mainnet launch timing.
• Testnet operational validation: Track contract metrics and stress tests on the HIP-3* testnet deployment to confirm whether allowlist verification introduces transaction latency on the order book.
• Secondary institutional deployers: Monitor whether rival brokerages or licensed exchanges file to deploy independent HIP-3* markets to avoid ceding regulated onchain market share to Payward.