Hyperliquid Testnet Live With Stars, HIP-3 Whitelist Support

4 mins mins

Hyperliquid’s testnet is live with a new Stars feature and HIP-3 DEX address whitelist support, signaling fresh builder tooling for the perpetuals protocol while several rollout specifics still await confirmation from official documentation.

Hyperliquid Testnet Live With Stars, HIP-3 Whitelist Support

The update surfaces through Hyperliquid’s developer resources and its in-app announcements channel, which together serve as the primary reference path for the testnet changes. The Hyperliquid announcements page is where the protocol publishes changes for testnet users and builders. For related coverage, see Japan May Ease Crypto's 2x Leverage Limit to Restore Liquidity.

At the core of the update are two items named in the rollout: a Stars feature and address whitelist support tied to HIP-3 DEX deployments. Both are positioned as testnet capabilities, and the wording available points to developer and DEX-operator tooling rather than a mainnet production change. For related coverage, see OKX to Launch AEON/USDT Spot Trading Pair: Listing Details and Market Focus.

What the Stars and HIP-3 Whitelist Support Add for Builders

HIP-3 is Hyperliquid’s framework for builder-deployed perpetuals, described in the HIP-3 documentation as a mechanism that lets deployers stand up their own perpetual markets. Address whitelist support in this context relates to controlling which addresses are permitted to interact with a deployed DEX.

Whitelist functionality typically gives a market operator a permissioning layer, useful for controlled experimentation or gating access during early deployment. The precise parameters and eligibility rules for this feature are not spelled out in the available evidence, so builders should confirm mechanics directly against the docs.

The developer-facing details of interacting with Hyperliquid programmatically are covered in the protocol’s API documentation, the reference point for teams building on the testnet. Testnet participants can obtain funds through the testnet faucet before deploying or trading.

Why a Testnet Feature Set Matters Before Mainnet

Testnet releases let builders validate new mechanics without risking production funds, which is why permissioning and deployment tooling tend to land there first. For a protocol whose growth is tied to builder-deployed markets under HIP-3, expanding the testnet surface area is a step toward broader market creation.

Whitelist support in particular may matter for partner onboarding and staged access, letting deployers experiment in a controlled setting. Any wider ecosystem impact remains conditional until the features move beyond testnet, and the current evidence does not confirm a production timeline.

Hyperliquid’s positioning within DeFi has drawn ongoing attention, from traders posting large perpetuals gains on the platform to the protocol’s engagement with regulators, including a push by Hyperliquid and Phantom urging the CFTC to update DeFi rules. Its founders have also spoken publicly about the industry, with a co-founder noting that crypto struggles to attract top talent.

What Remains Unclear Ahead of Broader Rollout

The available research is thin, and no verified technical parameters accompany the feature names. It is not confirmed whether the Stars feature and whitelist support are testnet-only or part of a staged path toward production.

Missing specifics include eligibility rules, deployment timelines, and any confirmed user, partner, or governance impact. These details require direct verification against Hyperliquid’s own documentation and announcements before they can be stated with certainty.

FAQ

What is the Hyperliquid testnet? It is a non-production environment where developers and users can test protocol features and deployments without real funds, with test funds available via the testnet faucet.

What does HIP-3 DEX address whitelist support enable? HIP-3 covers builder-deployed perpetuals, and 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 watch for next? Whether the features stay testnet-only or advance toward mainnet, plus any published parameters, eligibility criteria, or timelines in Hyperliquid’s official announcements.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.