According to BlockBeats, Hyperliquid’s testnet has recently shown a new feature called "stars," which introduces an optional whitelist mechanism for trading addresses on HIP-3 DEX.
In the current testnet version, deployers can limit position opening and position increases to whitelisted addresses only. The whitelist size on testnet is capped at 10,000 addresses.
Addresses that are not authorized are not fully blocked from the system. They can still deposit into accounts and place reduce-only orders to close positions or cut existing exposure.
Community discussion centers on possible use cases
Community members said the feature could broaden the range of applications for HIP-3 DEX. Examples mentioned include tokenized stocks, real-world assets, institutional indexes and other regulated products, where trading may be opened only to users who have completed know-your-customer checks or otherwise meet access requirements.
The same structure could also be used to open a new market first to market makers, partners or community members for testing. In that view, it could lower the risk of spam trading, wash trading or malicious manipulation during a market’s early stage.
The decision to let non-whitelisted users continue reducing positions also means users would not be prevented from exiting holdings because of access restrictions.
An optional control layer rather than a change to the base layer
Community members also said the "stars" feature does not alter Hyperliquid’s permissionless base layer. Instead, it adds an optional access-control function that developers can turn on or off depending on their needs.
That structure could support use cases such as DAO-run markets, trading clubs, private funds or partner-only venues, while still using Hyperliquid’s matching engine and settlement layer.
Still limited to testnet
For now, the feature remains in the testnet stage. Hyperliquid has not announced its specific purpose, and its eventual applications may become clearer only after a mainnet rollout and the release of more developer documentation.

