Headline: Kraken-branded deployer appears to be testing a permissioned HIP-3 DEX on Hyperliquid — but confirmation is missing A Hyperliquid testnet deployment using the name “Kraken HIP-3 test DEX” has been observed activating permissioned features that could let an operator run a compliant, permissioned perpetual market on Hyperliquid — though neither Kraken nor Hyperliquid has confirmed any involvement. What was observed - On Aug. 19 a testnet deployer calling itself “Kraken HIP-3 test DEX” enabled Star gating (a permission system) and added 10 wallets to an approved-user list, Blockworks analyst Shaunda Devens reported Aug. 22. - The deployer tested three of five compliance controls visible on Hyperliquid’s testnet. A validator was also registered under the name “Kraken Exchange Validator.” - The controls exercised let a deployer take direct actions on user accounts or positions: cancel open orders, close positions via reduce-only orders, and move collateral. Why this matters These are the kinds of account-level interventions common on centralized exchanges — identity checks, the ability to block or freeze access, react to sanctions or legal orders, reduce exposure, and remove funds when rules require intervention. Applied to a HIP-3 market, they would let a deployer run a “permissioned” on-chain market: trading and settlement remain on Hyperliquid’s chain, but access and account rules could be restricted to approved, screened wallets. Important caveat: name ≠ proof Hyperliquid’s testnet is permissionless, so any user can deploy a market or register a validator using another entity’s name. The public evidence shows a Kraken-branded deployment used the new controls, but it does not prove Kraken created or authorized it. At the time of reporting, neither Kraken nor Hyperliquid had publicly confirmed a partnership or test. How HIP-3 works (quick primer) - HIP-3 (Hyperliquid Improvement Proposal 3) lets independent builders launch perpetual futures markets using HyperCore, Hyperliquid’s trading engine, which provides order books, matching, margin and liquidation logic. - HIP-3 has been live on mainnet since Oct. 13, 2025. To operate a market, a builder must stake 500,000 HYPE as a financial bond; validators can slash this stake for oracle manipulation or rule violations. The stake requirement continues for 30 days after markets are closed. - Deployers set assets, oracles, collateral, margin, leverage and funding settings. They also keep 50% of market fees. - As of a July 3 report, HIP-3 open interest exceeded $1.43 billion, with equities and commodities contracts among the platform’s top markets by volume. What permissioned features change If Star gating and related tools ship to mainnet, deployers could limit trading on their markets to whitelisted wallets. That would enable combining public on-chain settlement with identity checks, geographic restrictions, or other account-level controls — potentially attractive to regulated firms that want on-chain infrastructure but must meet compliance requirements. Regulatory and operational limits - A permissioned HIP-3 market would not by itself satisfy U.S. legal requirements for offering derivatives to U.S. retail traders. Commodity derivatives for U.S. retail typically must be offered through CFTC-registered designated contract markets, clearing orgs and intermediaries. - Wallet screening and order controls can help enforce geographic restrictions, but they do not replace registration or other regulatory obligations. - Operationally, HIP-3 deployers control oracles and market rules, so they bear responsibility for risk management. Recent incidents underline this: on July 28 a HIP-3 contract tracking SK Hynix shares fell roughly 17.9% intraday after a single anomalous trade fed into the contract’s oracle, briefly sending the on-chain contract price sharply down before it recovered. That contract was operated by Trade.xyz, which retained oracle and settlement responsibility. Why Kraken link would be significant (if true) Kraken and parent Payward have spent 2026 expanding securities, tokenized assets and on-chain trading services. Highlights: - Aug. 18 launch of U.S. stock trading for eligible customers across the European Economic Area, covering 7,000+ U.S.-listed stocks, 700+ xStocks and 600+ crypto assets under one account. - Payward Europe Digital Solutions (a Cyprus firm) provides the conventional stock service under MiFID II. - xStocks tokenized products reportedly generated over $38 billion in trading volume since June 2025. - Earlier rollouts include xChange (on-chain execution for tokenized equities), and plans — via a July deal with GTN — to add Hong Kong listings and expand into other markets subject to licensing. Devens tied the Kraken name and Payward’s recent on-chain securities push as reasons this test could be connected to the exchange, but stresses that remains an inference based on timing and branding, not confirmation. Bottom line The testnet activity demonstrates Hyperliquid is building tools that could let regulated or licensed operators run permissioned HIP-3 markets mixing on-chain settlement with off-chain compliance. Whether those features will be adopted on mainnet, and whether a bona fide Kraken deployment is behind the observed test, remain open questions. For now it’s an intriguing signal that mainstream trading firms are exploring how to marry regulatory controls with decentralized trading infrastructure — but also a reminder that deployers retain critical responsibilities for oracles, market design and regulatory compliance. Read more AI-generated news on: undefined/news