Hyperliquid Announces HIP-3*: Optional Whitelist Mechanism for Institutional Participants

HuoXing Finance reports that on September 3, Hyperliquid released an API announcement introducing an optional deployer configuration feature for HIP-3 in its upcoming network upgrade, collectively termed HIP-3*. At its core, this new functionality enables deployers or their sub-deployers to manage on-chain whitelists and set access permissions for specific markets, thereby creating “permissioned markets.” This feature is strictly an incremental addition to HIP-3, fully optional, and its usage is entirely at the deployer’s discretion—existing markets remain unaffected. The initial version of HIP-3* is now live on the testnet, with specifications subject to adjustment based on community feedback. Hyperliquid emphasizes that it remains a neutral infrastructure layer aimed at enabling large-scale deployment of financial systems. HIP-3* is designed to provide deployers with additional capabilities to operate their deployments in compliance with applicable regulatory requirements. Consistent with HIP-3, HIP-3* deployers are independent operators who use Hyperliquid as their on-chain infrastructure layer for their own markets while retaining full control and responsibility over their deployments. This design allows Hyperliquid to maintain its permissionless core while opening access to institutional participants requiring a compliance framework.