Hyperliquid tests allowlists that let operators restrict access to their own markets

In a Sept. 3 developer update, Hyperliquid API Announcements said the onchain derivatives exchange was adding optional wallet allowlists to builder-run perpetual markets. The testnet-only extension, called HIP-3*, would let a market deployer decide which wallets may trade on its venue without imposing the same access policy across Hyperliquid.HIP-3 is Hyperliquid's framework for perpetual markets deployed by independent builders. The current API reference says a new venue can be designated HIP-3* when it is created, enabling an onchain allowlist and proxied user actions. Hyperliquid described the feature as optional and strictly additive, with existing markets unchanged. The specification is preliminary, available only on testnet and has no announced mainnet date.How HIP-3* wallet allowlists workA HIP-3* 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.Each power is limited by the venue boundary. The documented bulk-cancellation tool leaves o...