Hyperliquid Testnet Guide: Faucet, API and Paper Trading

How does the Hyperliquid testnet faucet work?

The official testnet faucet currently provides 1,000 mock USDC for HyperCore trading. Hyperliquid requires the same address to have deposited on mainnet before it can claim. The requirement checks address eligibility; it does not transfer the mainnet deposit into testnet or turn mock USDC into a redeemable asset.

Do you need to deposit real money to use the faucet?

Under the current official rule, the address must have deposited on mainnet. That means a completely new address cannot claim simply by visiting the testnet faucet. A prior deposit is an eligibility condition, not a fee charged by the faucet. Never deposit more than you understand or can afford merely to unlock a test environment.

If the address has already deposited but the claim fails, first compare the full connected address on mainnet and testnet. Wallet extensions can switch accounts silently, and email login creates an additional address complication. Check eligibility and domain before seeking support through official channels.

Why can email login cause a testnet wallet mismatch?

Hyperliquid's official faucet documentation says Privy generates different wallet addresses for mainnet and testnet email logins. The testnet email address may therefore fail the same-address requirement even when the mainnet email account has deposited.

The documented workaround is to export the email wallet from mainnet, import that private key into a compatible wallet extension and connect the resulting same address to testnet. Exporting a private key is security-sensitive: do it only through the verified mainnet settings, never paste the key into a website, and make sure the device and wallet extension are trusted.

How do you paper trade on Hyperliquid testnet?

What should you practise before moving to mainnet?

• Connecting and reconnecting the intended wallet and subaccount.
• Reading order-book depth, spread, mark price and liquidation price.
• Placing market, limit, reduce-only and TP/SL orders.
• Recognising resting, filled, partially filled, rejected and cancelled states.
• Changing between cross and isolated margin without confusing their risk boundaries.
• Closing a position and cancelling leftover orders during a fast move.
• Checking fees and funding separately from price profit or loss.
• Recovering state after a refresh, wallet disconnect or WebSocket reconnect.

What is different between Hyperliquid testnet and mainnet?

Good testnet results prove that a workflow ran under testnet conditions. They do not prove profitability, mainnet execution quality or resilience during production congestion. Before moving an automated process to mainnet, repeat metadata checks, use a new mainnet API wallet, lower the initial size and verify every safety limit against live mainnet state.

How do you use the Hyperliquid testnet API?

Hyperliquid uses the same general REST request structure on testnet with a different base URL. Read-only info requests go to https://api.hyperliquid-testnet.xyz/info. Signed actions go to the /exchange route on that base. Real-time subscriptions use wss://api.hyperliquid-testnet.xyz/ws.

curl -X POST https://api.hyperliquid-testnet.xyz/info \
  -H "Content-Type: application/json" \
  -d '{"type":"allMids"}'

A successful response confirms that the read path works, but it says nothing about signing. Signed actions must use testnet-specific configuration. User-signed payloads that contain hyperliquidChain should use Testnet rather than Mainnet, and the client must resolve asset metadata from testnet instead of copying mainnet IDs.

How do you configure the Python SDK for testnet?

The official Python SDK exposes TESTNET_API_URL. Start with its read-only Info client, then use the repository's examples for agent approval, orders and cancels. Keep the test account address separate from the API-wallet signing key, and never commit either network's private key to a repository.

from hyperliquid.info import Info
from hyperliquid.utils import constants

info = Info(constants.TESTNET_API_URL, skip_ws=True)
state = info.user_state("0xYOUR_TESTNET_ACCOUNT_ADDRESS")
print(state)

When an API wallet signs, account queries still use the master or actual subaccount address. Querying the agent address is a common reason for an empty account response. Use a dedicated testnet agent and do not reuse it as a mainnet key merely because the code path looks similar.

What should an API test plan cover?

• Fetch metadata and map symbols to the current testnet asset identifiers.
• Read balances, positions and open orders using the correct account address.
• Submit a resting limit order and parse the returned order ID.
• Cancel the order and confirm the final status rather than assuming success.
• Test partial fills, invalid precision, insufficient margin and reduce-only rejection.
• Reconnect WebSocket feeds and rebuild state from snapshots after a disconnect.
• Stop the process safely when market data is stale or expected fields are missing.
• Reconcile positions and orders before the process exits or restarts.

Is the HyperEVM testnet faucet the same as the trading faucet?

No. The /drip faucet supplies mock USDC for trading on HyperCore. HyperEVM transactions require testnet HYPE for gas. Hyperliquid's builder-tools documentation lists third-party faucets such as Chainstack and QuickNode for testnet HYPE. Their limits and availability are controlled by those providers and can change.

The official HyperEVM testnet RPC is https://rpc.hyperliquid-testnet.xyz/evm and its chain ID is 998. Adding that network to a wallet does not create a HyperCore trading balance, and claiming mock USDC does not necessarily provide HyperEVM gas. Treat them as connected but distinct test workflows.

Why is Hyperliquid testnet not working?

Is Hyperliquid testnet risk-free?

Mock trading removes direct market loss from the test balance, but wallet and operational risks remain. A malicious site can still request a harmful signature, and an exposed private key can compromise the same address on other networks. Testnet is not a reason to lower wallet-security standards.

• Use verified Hyperliquid domains and bookmark them.
• Never provide a seed phrase or private key to a faucet or support account.
• Keep API secrets outside source code, browser bundles and logs.
• Use separate API wallets for testnet and mainnet automation.
• Read every wallet prompt even when only mock assets are involved.
• Revoke agents and remove test permissions when an experiment ends.

The bottom line

Hyperliquid testnet is best used to validate a process: connect the correct address, claim mock USDC, place and cancel orders, test exits, inspect fills and recover cleanly from errors. It is less useful as evidence that a strategy will earn money or receive the same execution on mainnet.

Keep the environments explicit. The trading app, REST API, WebSocket and HyperEVM RPC all have testnet-specific addresses. Fetch testnet metadata, use testnet-only API wallets and re-verify every assumption before moving even a small version of the workflow to mainnet.