Hyperliquid’s testnet is live with a new Stars feature and address whitelist support for HIP-3 DEX deployments, adding builder-oriented tooling for the perpetuals protocol while several rollout details remain unconfirmed in official technical materials.

The update appears through Hyperliquid’s developer resources and its in-app announcements channel, which together serve as the main reference points for testnet changes. Hyperliquid publishes updates for testnet users and builders on its announcements page, while technical implementation details are maintained in the protocol’s documentation.

The two named additions in the rollout are the Stars feature and address whitelist support tied to HIP-3 DEX deployments. Both are presented as testnet capabilities. The available wording points to tooling for developers and DEX operators rather than a confirmed mainnet production change.

Stars and HIP-3 Whitelist Support Target Builder Tooling

HIP-3 is Hyperliquid’s framework for builder-deployed perpetuals. The protocol’s HIP-3 documentation describes it as a mechanism that allows deployers to stand up their own perpetual markets.

Perpetual markets are a core venue type in crypto derivatives because they allow trading of futures-like contracts without a fixed expiry date. That makes market configuration, access controls, and testing processes especially important for teams deploying new markets, since operational issues can affect traders, liquidity providers, and market operators.

In that context, DEX address whitelist support relates to controlling which addresses are permitted to interact with a deployed DEX. Whitelist functionality typically gives a market operator a permissioning layer, which can be used for controlled testing, restricted participation, or staged access during early deployment.

The available evidence does not spell out the exact parameters, eligibility criteria, or operating rules for the whitelist feature. Builders and DEX operators therefore need to verify the mechanics directly against Hyperliquid’s documentation and official announcements before relying on the feature in a deployment plan.

Developer-facing information for interacting with Hyperliquid programmatically is covered in the protocol’s API documentation, which serves as a reference point for teams building on the testnet. Testnet participants can also obtain funds through the testnet faucet before deploying or trading in the non-production environment.

Testnet Rollouts Allow Controlled Validation

Testnet releases allow developers and users to validate new mechanics without using production funds. For that reason, deployment tooling and permissioning features commonly appear in a testnet setting before any broader release is confirmed.

For Hyperliquid, whose HIP-3 framework is tied to builder-deployed markets, expanding the testnet feature set adds more surface area for market creation and operational testing. Whitelist support may be relevant for partner onboarding and staged access because it gives deployers a way to experiment with controlled participation.

The distinction between testnet and mainnet is central to the update. Testnet activity can help teams evaluate integrations, user flows, and deployment assumptions, but it does not by itself confirm that a feature is ready for production use or that the same rules will apply if it later appears on mainnet.

Any broader ecosystem impact remains conditional unless the features move beyond testnet. The current evidence does not confirm a production timeline, and it does not establish whether Stars or HIP-3 DEX address whitelist support will be limited to testnet or included in a staged path toward mainnet.

Hyperliquid has continued to attract attention within DeFi. Previous coverage has focused on traders posting large perpetuals gains on the platform, as well as the protocol’s engagement with regulators, including a push by Hyperliquid and Phantom urging the CFTC to update DeFi rules. Hyperliquid’s founders have also commented publicly on the broader crypto industry, with a co-founder saying that crypto struggles to attract top entrepreneurial talent.

Key Details Still Await Confirmation

Several technical and operational details remain unclear from the available information. No verified technical parameters have been published alongside the feature names in the source material, and there is no confirmed information on eligibility rules, deployment timelines, user impact, partner impact, or governance implications.

It is also not confirmed whether the Stars feature and HIP-3 whitelist support are intended only for testnet use or whether they are part of a broader staged rollout. Those details require direct confirmation from Hyperliquid’s official documentation, in-app announcements, or other primary protocol communications.

FAQ

What is the Hyperliquid testnet?
The Hyperliquid testnet is a non-production environment where developers and users can test protocol features and deployments without using real funds. Test funds are available through the testnet faucet.

What does HIP-3 DEX address whitelist support enable?
HIP-3 covers builder-deployed perpetuals, and DEX address whitelist support relates to controlling which addresses may interact with a deployed DEX. The exact permissioning rules should be confirmed in the HIP-3 documentation.

What should builders monitor next?
Builders should watch Hyperliquid’s official announcements and documentation for confirmation on whether the features remain testnet-only or advance toward mainnet, as well as any published parameters, eligibility criteria, or timelines.