1. What is the new Hyperliquid allowlist?
Hyperliquid, a decentralized exchange for perpetual futures, said on October 26 that it is building an opt-in tool that lets the deployers of its markets limit who can trade on them. The feature is available only on the testnet so far. Payward, the parent company of the crypto exchange Kraken, intends to be the first firm regulated by the Commodity Futures Trading Commission (CFTC) to use it, and the plan still needs regulatory approval.
Hyperliquid described the feature in a post on X. Under the proposal, the exchange adds access settings to an existing framework, HIP-3, so that an operator can decide which wallets are allowed to take part in a given market. The centerpiece is an onchain allowlist controlled by the deployer or by sub-deployers the deployer appoints.
The announcement matters because decentralized exchanges are usually open to anyone with a wallet, while regulated US futures venues must know who their customers are. An allowlist is one way to bridge that gap, and Payward's plan is the first announced attempt to use it in a CFTC-regulated setting.
An allowlist is simply a list of approved participants. In an onchain version, the list is stored and enforced by a smart contract, so the rule is applied automatically each time a wallet attempts to trade. A wallet that is not on the list cannot take part in a restricted market, while wallets on it can trade as they would elsewhere. The deployer, or a sub-deployer it designates, decides who is added or removed.
Hyperliquid presents the tool as an addition rather than a change of direction. Operators who want open markets can keep them, and those who need to limit participation have a mechanism to do so. This optionality is central to how the exchange frames the feature, and it is why the announcement does not alter the existing markets.
2. How would Payward run markets on it?
Payward plans to keep every part of the chain within its own group. Bitnomial, which is registered with the CFTC as both an exchange and a clearinghouse, would launch and operate the markets and would clear and settle trades, if regulators approve. Client accounts would sit with NinjaTrader Clearing, a Payward entity registered with the CFTC as a futures commission merchant, or FCM.
Payward first announced its intention on September 16. In that plan, trading would be limited to accounts that NinjaTrader has onboarded and that appear on allowlists kept by both NinjaTrader and Bitnomial. Payward reported 6.6 million funded accounts as of June 30, which indicates the size of the customer base from which such traders could come.
Co-CEO Arjun Sethi said that Payward intends to be the first, holding the keys and carrying the regulatory obligations. The wording reflects the central point of the design: the regulated firm, not the exchange protocol, would be responsible for who trades and for compliance with the rules.
The structure is designed so that each regulated function sits with a registered entity. An exchange and clearinghouse handles the listing of contracts and the settlement of trades, while a futures commission merchant handles customer accounts. In US futures markets these roles are usually separate, and each carries its own obligations to the CFTC. Payward's plan places them all inside one corporate group.
Kraken is already a familiar name in crypto trading, and Payward's reported base of 6.6 million funded accounts suggests demand that could be directed toward such markets. The September 16 announcement set out the double allowlist: an account must be onboarded by NinjaTrader and appear on the lists maintained by both NinjaTrader and Bitnomial before it can trade.
3. What does HIP-3 do?
HIP-3 is the existing framework that allows outside builders to deploy their own perpetual futures markets on Hyperliquid. The new feature is labeled HIP-3*, and it adds settings on top of that framework. Hyperliquid says use is optional, that the change only adds to HIP-3, and that markets already running will not be affected.
Perpetual futures are derivatives contracts with no expiry date, which traders use to take leveraged positions on the price of an asset. Letting outside parties deploy such markets means that each deployer decides how its market operates. The allowlist gives those deployers a tool for restricting access when they need to, for example to meet legal requirements for customer screening.
Hyperliquid describes itself as a neutral infrastructure layer with the goal of supporting large parts of the financial system. Under the framework, each deployer keeps control of its own markets and is accountable for them. This division of responsibility is what lets the exchange stay neutral while still allowing a regulated operator to impose conditions.
Leverage is a defining feature of these contracts. A trader can control a position larger than the capital posted, which magnifies both gains and losses. That is one reason regulators pay close attention to who is allowed to trade derivatives, and why a mechanism for screening participants is relevant to any plan to bring such markets into a regulated setting.
The framework's design reflects a wider trend of exchanges opening their infrastructure to third parties. Instead of a single operator choosing every listing, outside builders can create markets that suit their own customers. The allowlist extends that idea to the question of who may trade, giving builders a second lever alongside the choice of what to list.
4. What stage is the project at?
The first version runs only on testnet, a trial environment where software is tested without real money at stake. Hyperliquid calls the specifications preliminary and says feedback could change them. Support for permissioned-market settings would arrive in a future network upgrade.
Neither Hyperliquid nor Payward has given a date for live trading or published contract details. Regulatory approval is also still pending, and the plan depends on it. Until those items are settled, the feature is best viewed as a trial, not a product that traders can use.
Jeff Yan, a co-founder of Hyperliquid, welcomed the news on October 27 in a post on X. He said Hyperliquid is honored that Payward is building on the platform to bring the next evolution of perpetual markets to the United States.
A testnet stage is a normal step before any protocol change reaches the main network. It allows developers and prospective users to try the feature, find problems and propose changes. Hyperliquid's statement that feedback could change the specifications fits this process and signals that the final design may differ from the preliminary version.
The dependence on a future network upgrade also matters. Permissioned settings will not become available on the main network until that upgrade is adopted, and no timeline has been announced. Payward's own approval process runs separately, so two schedules, one technical and one regulatory, must line up before live trading is possible.
It is also worth noting what has not been disclosed. Beyond the structure described above, neither company has published contract details, and neither has said when it expects a decision from regulators. Readers should therefore treat the plan as an announced intention with conditions attached, not as a settled arrangement.
5. Why does this matter for decentralized finance?
The significance of the announcement lies less in any single feature than in what it suggests about how decentralized and regulated finance may meet. A neutral protocol that offers optional access controls can be used by firms that have to follow strict rules, without making those rules apply to everyone else on the network.
The plan shows a possible path for a decentralized protocol to host markets that comply with US rules without changing the protocol for everyone. Because the allowlist is optional and set per market, open markets can continue alongside restricted ones. That is a design choice with practical weight, since it avoids forcing a single compliance model on all users.
For a regulated firm, the appeal is the ability to use an existing venue's technology and liquidity while keeping control of access. Payward would run the full process in-house, from onboarding through clearing, with the onchain layer providing the trading venue. Whether regulators accept that arrangement is the open question.
Observers will watch for three things next: the next network upgrade that would carry the permissioned settings, any regulatory decision on the Payward structure, and the publication of contract details. None has a date, so the timeline remains uncertain.
The arrangement also touches a recurring tension in decentralized finance. Protocols are built to be open and neutral, yet institutions that handle customer money must follow rules about identity and access. A design in which the protocol stays neutral and the regulated firm carries the obligations is one way to reconcile the two, and the quote from Payward's co-CEO about holding the keys and the obligations points directly at it.
There is also a question of accountability. Hyperliquid says each deployer keeps control of its own markets and is accountable for them, which places responsibility on the operator rather than on the exchange layer. For a regulator, that clarity about who is responsible is likely to be as important as the technology itself.
The coming months should show whether the idea moves from a testnet trial to a working market. The key facts so far are limited and clearly stated: an optional tool, a single announced regulated user, a pending approval and no launch date. Anything beyond those points would be conjecture, and the follow-up announcements will determine how far the plan goes.