Hyperliquid said future network upgrades will let HIP-3 deployment teams optionally configure permissioned markets, with the new deployment-side features grouped under HIP-3*. The core of the update is an on-chain allowlist managed by the deployer or its sub-deployers.
According to Foresight News, the feature is an incremental extension to HIP-3 and is entirely optional for deployers, while existing markets remain unchanged.
The first version of HIP-3* is already live on testnet, and the testnet specifications are preliminary and may change based on feedback. Hyperliquid said it positions itself as a neutral infrastructure layer intended to support much of the financial system.
HIP-3* is designed to give deployers additional functions so they can operate deployments in line with their own compliance requirements. Like HIP-3, HIP-3* deployers are independent operators that use Hyperliquid only as the on-chain infrastructure layer for their own markets, while retaining control and responsibility for their deployments.