Hyperliquid, this time the move is quite interesting—HIP-3* allows the deployer to set up their own “permissioned market,” with the core being an on-chain allowlist.
In plain terms: if a deployer wants to filter users according to compliance requirements, they can configure this feature; if they don’t want to use it, the existing market remains unchanged. It’s purely an incremental optional addition, not something mandatory. The first version has already been deployed to the testnet, and the specifications will be adjusted based on feedback.
Hyperliquid repeatedly stresses that it is only a neutral underlying infrastructure, while the deployer is the independent operating entity—control and responsibility are entirely in the other party’s hands. This “providing capabilities but not taking custody” posture is, for institutions looking to enter the on-chain derivatives space, a signal—greater compliance and flexibility.
It’s worth keeping a close eye on the rollout schedule after HIP-3* goes live. #Hyperliquid #DeFi
In plain terms: if a deployer wants to filter users according to compliance requirements, they can configure this feature; if they don’t want to use it, the existing market remains unchanged. It’s purely an incremental optional addition, not something mandatory. The first version has already been deployed to the testnet, and the specifications will be adjusted based on feedback.
Hyperliquid repeatedly stresses that it is only a neutral underlying infrastructure, while the deployer is the independent operating entity—control and responsibility are entirely in the other party’s hands. This “providing capabilities but not taking custody” posture is, for institutions looking to enter the on-chain derivatives space, a signal—greater compliance and flexibility.
It’s worth keeping a close eye on the rollout schedule after HIP-3* goes live. #Hyperliquid #DeFi