Hyperliquid Announcement HIP-3*: Opening the Door for Compliance-Oriented Institutions, Introducing an Optional Whitelisting Mechanism

BlockBeats News, September 3rd, Hyperliquid released an API announcement, introducing an optional deployer configuration feature for HIP-3 in a future network upgrade, collectively referred to as HIP-3*. The core of this addition is to allow deployers or their sub-deployers to manage an on-chain whitelist, granting access to specific markets, thus creating a "permissioned market." This feature is strictly an incremental addition to HIP-3, entirely optional, with the decision to use it left to the deployer, and existing markets remain unaffected. The initial version of HIP-3* is currently live on the testnet, with the testnet specifications being preliminary and subject to adjustments based on community feedback.

Hyperliquid emphasizes that it has always been a neutral infrastructure layer, aiming to support the large-scale deployment of the financial system. HIP-3* aims to provide additional functionality to deployers, allowing them to operate their deployments in compliance with their applicable regulatory requirements. Consistent with HIP-3, deployers of HIP-3* are independent operators utilizing Hyperliquid as the on-chain infrastructure layer for their proprietary markets while retaining control and responsibility over their deployments. This design enables Hyperliquid to maintain its permissionless core while opening the door to institution-grade participants requiring a compliance framework.