Hyperliquid Names Payward First CFTC-Regulated HIP-3 Deployer
What HIP-3 Is and Why It Matters
Hyperliquid's HIP-3 upgrade is a proposed protocol-level change that allows designated deployers to restrict market access through onchain allowlists. In plain terms, a deployer can specify which wallet addresses are permitted to trade in a given market, potentially making it possible to enforce access controls, such as KYC verification, at the smart-contract layer rather than through a centralised gateway.
Permissioned DeFi: A new category for compliance teams
This is a meaningful structural shift. Most DeFi perpetual venues are permissionless by design, meaning anyone with a compatible wallet can trade. HIP-3 creates a middle category: a decentralised settlement and matching layer combined with a permissioned access layer controlled by a regulated entity. The Hyperliquid Policy Center has noted that regulated firms using HIP-3 could impose leverage limits and onchain access restrictions while still offering exchange-based products.
Whether the Payward deployment would incorporate built-in KYC checks remains unconfirmed. Hyperliquid has stated that deployers retain control and responsibility for their own markets, keeping the protocol itself as a neutral infrastructure layer. That distinction has direct consequences for how compliance obligations are allocated between the protocol and the deployer, a point auditors will need to examine carefully.
The functionality is currently live on testnet only. Payward's deployment is explicitly subject to regulatory approval, so no regulated HIP-3 market is operational yet.
The Regulatory Structure Behind the Announcement
Hyperliquid's announcement on 26 October 2026 named specific CFTC-registered entities within the Payward group to carry out distinct roles in the proposed structure.
Bitnomial as deployer and clearing organisation
Bitnomial, Payward's CFTC-regulated designated contract market (DCM) and derivatives clearing organisation (DCO), is the named HIP-3 deployer. A DCM licence allows an exchange to list futures and swaps for trading; a DCO licence covers the clearing and settlement of those contracts. Bitnomial holding both means a single regulated entity would handle deployment, clearing, and settlement of any HIP-3 market it operates.
NinjaTrader Clearing for client accounts
If the deployment proceeds, NinjaTrader Clearing, Payward's CFTC-registered futures commission merchant (FCM), would carry client accounts. An FCM is the intermediary that accepts client funds, executes trades on their behalf, and is responsible for margin collection under CFTC rules. This means individual traders' positions would sit inside a regulated FCM structure, not directly on a bare DeFi wallet, creating a clear custodial and reporting chain.
Payward filed formally on 16 September 2026, stating that Bitnomial would handle deployment, clearing, and settlement, subject to regulatory approval. Bloomberg had earlier reported Payward was exploring a structure to bring Hyperliquid-linked perpetual futures to US traders through Bitnomial.
AML and KYC Implications for Firms
The open question that compliance professionals should track closely is how the permissioning actually works in practice. Onchain allowlists can restrict which addresses interact with a market, but an address is not automatically equivalent to a verified individual. A robust KYC implementation would require a process that links verified identity to an approved wallet address before that address is added to the allowlist.
What the allowlist model means for AML programs
If Bitnomial, as the DCM, administers the allowlist, it would presumably conduct customer due diligence and add approved wallet addresses through a controlled onboarding flow. Under CFTC rules, a DCM is required to maintain compliance programs, and its associated FCM, NinjaTrader Clearing in this case, would be subject to Bank Secrecy Act obligations including AML program requirements, customer identification procedures, and suspicious activity reporting.
For accounting firms advising clients who trade on a Payward-deployed HIP-3 market, this structure would likely mean counterparty documentation is substantially cleaner than on a permissionless DeFi venue. Every counterparty, at least on the regulated side, would have passed through an FCM onboarding process. That has knock-on effects for transaction-level documentation in crypto bookkeeping software: positions could be tied to identifiable legal persons rather than pseudonymous addresses.
It is also worth noting the broader regulatory environment for DeFi derivatives in the US. The CFTC has long asserted jurisdiction over leveraged commodity derivatives, and trading perpetual futures without a proper registration has been a significant enforcement risk. A CFTC-regulated HIP-3 deployer model could, if approved and structured correctly, represent a compliant pathway that other regulated entities might replicate, creating a template for permissioned DeFi at scale. Our earlier coverage of what the Senate probe into Tether payments means for AML compliance illustrates how closely regulators are watching the intersection of regulated and unregulated digital asset flows.
Accounting and Audit Considerations
For CFOs and audit teams, a CFTC-regulated perpetual futures product built on a DeFi protocol creates a hybrid position that does not slot cleanly into existing classification frameworks.
Derivatives accounting under US GAAP
Under US GAAP, a perpetual futures contract is a derivative instrument and would generally fall under ASC 815. Entities holding such positions for hedging purposes would need to assess whether hedge accounting qualifications are met; those holding them for speculative or trading purposes would mark positions to fair value through the income statement each period. The novelty here is the settlement mechanism: if settlement occurs onchain through Hyperliquid's matching engine and Bitnomial's DCO infrastructure, firms will need to confirm how the clearing leg is reflected, whether margin posted is classified as a receivable or a separate asset, and how unrealised gains and losses are computed at the reporting date.
Digital asset accounting software and position tracking
A regulated clearing structure means trade confirmations, margin statements, and settlement records should, in principle, be available from NinjaTrader Clearing in a format similar to traditional futures brokerage statements. For teams currently using digital asset accounting software to reconcile DeFi positions from raw blockchain data, this could simplify reconciliation significantly. Instead of constructing position data from on-chain events, firms may be able to rely on FCM-generated records as the primary source, with blockchain data as the verification layer. That said, teams should not assume the records will arrive in a familiar format from day one; confirming the data structure with Bitnomial or NinjaTrader Clearing before the first reporting period is a prudent step.
Tax treatment of regulated perpetual futures
US tax treatment of futures contracts regulated by the CFTC under Section 1256 of the Internal Revenue Code is notably favourable: gains and losses on Section 1256 contracts are marked to market at year-end and taxed at a blended 60/40 rate, meaning 60% treated as long-term capital gain and 40% as short-term, regardless of holding period. Whether a Payward-deployed HIP-3 perpetual qualifies as a Section 1256 regulated futures contract will depend on the specific terms of the contract and CFTC classification. This is not guaranteed, but the involvement of a CFTC-registered DCM and DCO is a prerequisite for that classification, so firms should engage tax counsel to assess eligibility once the product structure is finalised.
For context on how novel derivatives products intersect with US tax and accounting frameworks, our piece on how prediction market accounting works for US filers covers a comparable set of classification questions.
What Firms Should Do Now
The deployment remains subject to regulatory approval and is not yet live outside testnet. That window is the right time to act, not after the product launches.
Immediate steps for accounting and compliance teams
First, map your client base or your own entity's exposure to Hyperliquid perpetuals already. If clients are trading on the current permissionless venue, understand how those positions are being recorded and what documentation you hold for counterparties. When the regulated HIP-3 market goes live, positions on the two venues will need to be tracked separately, with different tax treatment potentially applying to each.
Second, review your crypto bookkeeping software capabilities against the anticipated data format from a CFTC-regulated clearing structure. Traditional futures brokerage integrations and DeFi wallet imports are handled differently in most platforms; you will want to know whether your tooling can handle both for the same client and the same asset class.
Third, brief relevant partners and staff on Section 1256 treatment and its prerequisites. Not every senior accountant familiar with crypto will have deep futures tax experience; a short internal briefing now prevents a misclassification later.
Fourth, watch the CFTC's public docket. Any approval of Bitnomial's deployment structure will generate public filings, and those filings will contain the specific contract terms needed to finalise accounting and tax analysis. Setting up a docket alert costs nothing and ensures you are not relying on press coverage for material details.
Frequently Asked Questions
What is a HIP-3 deployer on Hyperliquid?
HIP-3 is a proposed Hyperliquid protocol upgrade that allows an approved entity, the deployer, to create a market with onchain access controls. The deployer can specify which wallet addresses may trade, enabling permissioned participation on an otherwise decentralised venue. Payward is named as the intended first deployer operating under a CFTC regulatory framework.
Does this mean Hyperliquid is now CFTC-regulated?
No. Hyperliquid itself describes its role as a neutral infrastructure layer. The CFTC-regulated entities, Bitnomial as DCM and DCO and NinjaTrader Clearing as FCM, would operate the specific market deployed under HIP-3. The underlying protocol remains separate from the regulated structure sitting on top of it.
How would client positions be held if NinjaTrader Clearing acts as FCM?
An FCM is required under CFTC rules to segregate client funds from its own proprietary assets. Client accounts held at NinjaTrader Clearing would fall under those segregation requirements, giving traders a regulated custodial arrangement rather than the self-custody model typical of permissionless DeFi venues.
Could CFTC-regulated perpetual futures on Hyperliquid qualify for Section 1256 treatment?
Possibly, but it is not automatic. Section 1256 treatment applies to regulated futures contracts traded on a qualified board or exchange, which generally requires CFTC designation as a DCM. Bitnomial holds that designation. The specific contract terms would still need to be assessed by tax counsel against the Section 1256 definition once the product structure is finalised and approved.
What should a CFO do before the market goes live?
Start by assessing existing exposure to Hyperliquid perpetuals and reviewing your crypto bookkeeping software's ability to ingest FCM-generated statements alongside on-chain data. Engage tax counsel on Section 1256 eligibility and monitor the CFTC's public docket for filings related to Bitnomial's deployment application. Acting before the product launches avoids a scramble at the first reporting date.
Source: The Block
]]>