Hyperliquid has announced HIP-3*, an optional deployer configuration feature that introduces a whitelist mechanism for creating permissioned markets. The announcement was made via an API notice on September 3, 2026. The core function allows deployers or sub-deployers to manage on-chain whitelists, setting access permissions for specific markets. HIP-3* is strictly an incremental addition to the existing HIP-3 and is completely optional; deployers can choose to enable it, and existing markets remain unaffected. The initial version of HIP-3* is now live on the testnet, with the specification being a preliminary version that 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. The feature provides deployers with additional functionality to operate in compliance with applicable regulatory requirements. Consistent with HIP-3, the deployers are independent operators that use Hyperliquid as the on-chain infrastructure layer for their own markets, while retaining control and responsibility. This design allows Hyperliquid to maintain its permissionless core while opening an entry point for institutional participants requiring a compliant framework.
Hyperliquid Launches HIP-3*: Optional Whitelist Mechanism for Institutional Participants
Hyperliquid, which describes itself as a neutral infrastructure layer, announced on September 3, 2026, an API update introducing HIP-3*, an optional configuration feature for deployers. The feature allows deployers or sub-deployers to manage on-chain whitelists, setting access permissions for specific markets to create permissioned markets.
HIP-3* is strictly an incremental addition to the existing HIP-3 and is completely optional; deployers decide whether to use it, and existing markets remain unaffected. The initial version of HIP-3* is now live on the testnet, with the testnet specification being a preliminary version that 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* provides deployers with additional functionality to operate their deployments in compliance with applicable regulatory requirements. Consistent with HIP-3, the deployers under HIP-3* are independent operators that use Hyperliquid as the on-chain infrastructure layer for their own markets, while retaining control and responsibility for their deployments. This design allows Hyperliquid to maintain its permissionless core while opening an entry point for institutional participants that require a compliant framework.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
