Hyperliquid officially announces HIP-3*: opens the door for compliant institutional-grade participants, offering an optional whitelist mechanism.

Hyperliquid has issued an API announcement stating that it will introduce an optional deployer configuration feature for HIP-3 in an upcoming network upgrade, collectively named HIP-3*. The core functionality allows deployers or their sub-deployers to manage on-chain whitelists and set access permissions for specific markets, enabling the creation of "permissioned markets". This feature is strictly an incremental addition to HIP-3, fully optional, with deployers deciding independently whether to adopt it—no impact on existing markets. The initial version of HIP-3* is now live on testnet; the testnet is a preliminary build and will be adjusted based on community feedback. Hyperliquid emphasized that it remains a neutral infrastructure layer, with the goal of supporting large-scale deployment of financial systems. HIP-3* is designed to provide deployers with additional functionality to operate their deployments while complying with their respective applicable regulatory requirements. Consistent with HIP-3, HIP-3* deployers are independent operators that use Hyperliquid as the on-chain infrastructure layer for their own markets, retaining full control and responsibility over their deployments. This design allows Hyperliquid to maintain its permissionless core while opening access to institutional participants that require a compliance framework.