I’ve been watching the derivatives space long enough to know that real progress rarely arrives with fireworks. Sometimes it shows up as a carefully worded post on a Monday afternoon. That’s exactly what happened when Hyperliquid laid out how Payward intends to become the first deployer of regulated US HIP-3 markets. The goal is straightforward yet ambitious: bring onchain perpetual futures to American clients through a structure that actually respects CFTC rules. Subject to approval, of course. And in this industry, those three words carry a lot of weight.
What Payward Actually Wants To Build
Payward is not inventing a brand-new product from thin air. The company already owns Bitnomial and operates NinjaTrader Clearing. Those pieces matter. Bitnomial would create, own, and administer the proposed markets. It would also handle contract clearing and settlement. NinjaTrader Clearing, the CFTC-registered futures commission merchant, would carry the customer accounts once everything clears regulatory hurdles.
The setup is deliberately layered. Customers must complete onboarding with NinjaTrader and land on both NinjaTrader’s and Bitnomial’s allowlists. Only then does a futures account with the registered broker unlock access to the new contracts. It’s not the open free-for-all many crypto natives prefer, but it is the kind of controlled environment regulators tend to accept.
Hyperliquid itself remains the infrastructure layer. The public blockchain still matches and records trades through its onchain order book. Contract specifications, however, live under Bitnomial Exchange’s rules. Regulatory responsibility stays with the named exchange, clearinghouse, and brokerage entities. That separation of roles is intentional. Hyperliquid provides the rails. The regulated entities operate the trains.
Why HIP-3* Changes The Permissioning Game
Hyperliquid labeled the optional permissioning functionality HIP-3*. The asterisk is not decorative. It signals that this is an extension rather than a replacement. Existing HIP-3 markets continue exactly as before. Deployers who want the new tools can activate them. Those who prefer open access simply ignore the feature.
Activation works through an onchain allowlist managed by the deployer or appointed sub-deployers. An early version already sits on testnet. The specifications remain preliminary and will evolve after feedback. Full support arrives with a future network upgrade. In practice this means a deployer can restrict participation without asking the core team to intervene every time a new participant needs approval.
I’ve found that optional tools often prove more powerful than mandatory ones. They let operators adapt to their own regulatory reality without forcing the entire ecosystem into the same box. Hyperliquid’s stated purpose matches that logic: allow deployers to operate markets consistently with the requirements that apply to them. The protocol stays neutral. Operators carry the compliance load.
Hyperliquid is a neutral infrastructure layer with the goal of supporting large parts of the financial system.
That sentence captures the philosophy. The chain does not decide who can trade. The deployer does, when the deployer chooses to exercise that control.
How The Account Structure Actually Works
Picture the customer journey. First comes onboarding with NinjaTrader. Then the same customer must appear on Bitnomial’s allowlist. Only after both conditions are satisfied does the futures account grant access. The design prevents casual leakage of regulated products into unregulated wallets. It also creates a clear audit trail.
Trades still settle on Hyperliquid’s public chain. The order book remains transparent. Yet the legal relationship between customer, broker, and exchange stays firmly inside the traditional regulatory perimeter. That hybrid model is what makes the proposal interesting. Onchain execution meets off-chain accountability.
Payward first floated the broader idea in mid-September. Hyperliquid was named as the first protocol the company planned to use for US onchain perpetual futures. The October update simply filled in the technical and operational details. Nothing in the later post contradicts the earlier vision. It simply makes the plumbing visible.
Bitnomial’s Role And The Acquisition Context
Payward completed its acquisition of Bitnomial earlier in the year. The deal brought exchange, clearing, and brokerage capabilities under one roof while leaving Bitnomial’s existing licenses and third-party clearing arrangements intact. That preservation of regulatory structure was deliberate. Starting from a clean but licensed foundation reduces the time and risk of building everything from scratch.
At the time of closing, Payward described a phased product rollout. Spot margin on its existing platform would come first. Perpetuals and options would follow. The company also sketched a business-to-business offering that would let banks, brokerages, fintechs, and payment providers offer regulated derivatives through integration. The Hyperliquid deployment fits neatly inside that longer roadmap.
Bitnomial Exchange received its designated contract market status years ago. The designation required compliance with the Commodity Exchange Act and the specific representations made in the application. Those obligations do not disappear simply because the matching engine now lives on a blockchain. They travel with the license.
Staking Requirements And Market Lifecycle
HIP-3 documentation has always assigned market definitions, contract specifications, oracle prices, and leverage limits to the deployer. Builder-deployed perpetuals use HyperCore’s margining system and order books, yet each deployed exchange maintains independent settings. A 500,000 HYPE mainnet staking requirement applies, and the stake must remain locked for at least 183 days after deployment.
The October post did not create separate staking terms for Payward’s proposed markets. The general rule therefore appears to govern. Once a deployer decides to close a market, the process is straightforward. Trading in the asset is halted. Open orders are canceled. Positions settle at the current mark price. After every asset under that deployment has been settled, the required stake can be unstaked. The mechanism is clean and leaves little room for lingering exposure.
Perhaps the most interesting aspect is that independent operators retain control and responsibility for their markets while still using Hyperliquid’s blockchain infrastructure. The chain does not become the exchange. It becomes the settlement and matching layer underneath regulated entities that already answer to the CFTC.
What Permissioned Markets Look Like In Practice
Earlier testing of permissioned markets was described in early September. Deployers could maintain participant lists and appoint sub-deployers to manage access. The core development team stayed out of those day-to-day decisions. That design choice matters. It keeps Hyperliquid from becoming a gatekeeper while still giving regulated operators the tools they need.
In the Payward case the allowlist is dual. Both the clearing firm and the exchange must approve the customer. The extra friction is the price of regulatory comfort. Some traders will dislike it. Others will welcome the clarity that comes with a fully licensed product. Both reactions are rational.
- Customers complete NinjaTrader onboarding first
- They must also appear on Bitnomial’s allowlist
- Only then does the futures account unlock trading
- Trades match and record on Hyperliquid’s order book
- Clearing and settlement remain under Bitnomial’s responsibility
That sequence is not glamorous. It is, however, the kind of process that survives regulatory scrutiny. In my experience the products that last are the ones that accept a little friction early rather than fighting the same battles repeatedly later.
Broader Implications For Onchain Derivatives
If the arrangement receives approval, it becomes a live example of regulated entities using public blockchain infrastructure without forcing the chain itself to become a registered exchange. That distinction is subtle and important. Other protocols have tried various hybrid models. Few have combined a mature designated contract market, a registered FCM, and a high-performance onchain order book in quite this way.
The optional nature of HIP-3* also protects the existing ecosystem. Permissionless markets continue. Permissioned markets can coexist. Deployers choose the model that matches their legal obligations. That flexibility reduces the chance of a forced migration or a hard fork over regulatory questions.
There is also a quiet signal about institutional readiness. Banks and traditional brokers have long cited the lack of clear regulatory pathways as a reason to stay on the sidelines. A structure that keeps the regulated entities fully accountable while using transparent onchain matching could lower that barrier. It will not eliminate every concern, but it removes one of the louder objections.
Compute Perpetuals And Policy Signals
Around the same period the Hyperliquid Policy Center submitted comments to the CFTC supporting futures and perpetual contracts tied to GPU rental prices and AI inference costs. The argument was practical. Data-center operators, lenders, and AI developers face ongoing exposure to computing prices. Both dated futures and perpetual contracts have a role depending on the nature of the exposure being hedged.
Proposed safeguards included leverage limits, caps on funding rates, and transparent pricing benchmarks. Dated futures were favored for scheduled expenses such as planned training runs. The submission is separate from the Payward markets, yet it shows the same broader posture: engage the regulator with concrete product ideas rather than abstract philosophical arguments.
Whether those compute contracts ever list is still unknown. The fact that the conversation is happening in formal comment letters rather than only on social media is itself a form of progress.
Risks And Open Questions
Approval is not guaranteed. The CFTC will examine the full package: contract design, customer protection measures, systemic risk considerations, and the interaction between the onchain matching engine and the traditional clearing structure. Any material change to the preliminary specifications on testnet could trigger additional review.
Liquidity is another practical question. Restricted access through dual allowlists will naturally limit the initial participant set. Market makers and larger traders will need clear incentives to provide depth inside a gated environment. How that chicken-and-egg problem resolves will influence whether the markets feel useful or merely symbolic.
There is also the matter of user experience. Moving between a traditional futures account and an onchain execution layer introduces friction that pure crypto natives are not used to. The smoother that bridge becomes, the more competitive the offering will be against both traditional futures platforms and unregulated perpetual venues.
I’ve noticed that regulatory products sometimes suffer from being designed primarily for the regulator rather than the end user. The teams involved here have incentive to avoid that trap. Whether they succeed will become visible only after launch.
Looking At The Competitive Landscape
Other venues have experimented with various forms of permissioned or hybrid derivatives. Some rely on licensed entities that sit entirely off-chain and simply use crypto as collateral. Others try to register the protocol itself. Hyperliquid’s approach keeps the protocol neutral and places the compliance burden on the deployers who choose to use the optional tools. That division of labor may prove more scalable than forcing every market into the same regulatory box.
For US-based traders the practical difference is simple. Access to perpetual futures that settle on a transparent public chain while still operating under a designated contract market and a registered FCM is rare. If the product works, it becomes a reference point. If it struggles, the lessons will still inform the next attempt.
Payward’s earlier experience with licensed platforms in other jurisdictions provides some institutional memory. The company is not approaching the US market as a complete newcomer. That background reduces, but does not eliminate, execution risk.
Technical Readiness On Testnet
The initial release of the permissioning functionality is already available for testing. Specs can still change. Feedback from potential deployers and from the broader community will shape the final form. That iterative approach is healthier than shipping a rigid design and discovering problems only after mainnet deployment.
Support for the optional deployer configuration arrives through a future network upgrade. Timing has not been locked publicly. In practice the upgrade schedule will need to align with the regulatory calendar. Launching the technical capability months before legal clearance, or vice versa, creates unnecessary coordination risk.
Independent operators retain full control over their own markets. They define the contracts, set the parameters, and manage the participant lists. Hyperliquid supplies the matching and settlement infrastructure. That clear separation of duties is one of the cleaner designs I’ve seen in this category.
What Success Would Actually Look Like
Success is not simply regulatory approval. Real success is sustained volume from participants who value the combination of onchain transparency and regulatory clarity. It is market makers willing to quote tight spreads inside the allowlisted environment. It is institutional desks that finally feel comfortable using perpetual-style products without stepping outside their compliance frameworks.
Secondary success would be replication. If the model works, other licensed entities may approach Hyperliquid or similar infrastructure providers with parallel proposals. A single successful deployment can lower the perceived risk for the next five.
Failure modes are equally clear. Prolonged regulatory delay, thin liquidity, or a cumbersome user experience could turn the markets into a technical curiosity rather than a useful trading venue. Those outcomes are avoidable, but only with continued attention after the announcement glow fades.
A Measured Path Forward
The October outline from Hyperliquid does not guarantee anything. It simply makes the architecture visible and confirms that the optional permissioning tools are being built with regulated use cases in mind. Payward’s plan to deploy through Bitnomial and NinjaTrader Clearing is concrete enough to evaluate and still flexible enough to adjust as feedback arrives.
For traders the near-term action is simple: watch the testnet, follow the regulatory process, and prepare for an onboarding path that looks more like a traditional futures account than a self-custodial wallet connection. For builders the message is equally clear. Neutral infrastructure that supports both open and permissioned models has a larger addressable market than infrastructure that forces a single ideology.
I’ve watched enough cycles to know that the products which quietly solve real compliance constraints often outlast the ones that chase pure decentralization theater. This proposal is still early. The details will evolve. Yet the direction of travel feels pragmatic rather than ideological, and that alone makes it worth following closely.
Whether the first regulated US HIP-3 markets launch exactly as described or require further refinement, the conversation has moved from abstract possibility to concrete operational design. That shift is meaningful. The rest will be decided by regulators, market participants, and the quality of execution that follows.
In the end the most interesting question is not whether onchain and regulated can coexist. It is whether the resulting product will be good enough that traders prefer it over the alternatives already available. Everything else is scaffolding.
