Hyperliquid Tests Wallet Allowlists for Operator-Controlled Markets

Hyperliquid is testing an update to its perpetual markets framework that will allow operators to restrict access to their own venues. The new feature, called HIP-3*, will let deployers decide which wallets can trade on their market without imposing the same access policy across Hyperliquid.

The current API reference for Hyperliquid's framework says a new venue can be designated as HIP-3* when it is created, enabling an onchain allowlist and proxied user actions. The feature is optional and strictly additive, with existing markets unchanged.

According to the documentation, a deployer can act for a user in five defined ways: add or remove allowlist approval, cancel specified resting orders, cancel all of the user's resting orders and time-weighted average price orders on the venue, place reduce-only orders, and move collateral to another account on the same venue.

Hyperliquid said that the tools are intended to help independent deployers operate under requirements applicable to them, leaving legal and operational choices with each deployer. The design could give firms with customer or jurisdiction restrictions a technical way to build gated perpetual markets while other deployers continue using ordinary HIP-3.