# Hyperliquid testnet and faucet: setup without real capital > Use the Hyperliquid testnet app, faucet, HTTP API and WebSocket endpoints, and keep test keys, addresses and configuration separate from mainnet. Canonical HTML: [Hyperliquid testnet and faucet: setup without real capital](https://hyperliquidreferralcodes.com/hyperliquid-testnet-faucet) Markdown URL: [Hyperliquid testnet and faucet: setup without real capital as Markdown](https://hyperliquidreferralcodes.com/markdown/hyperliquid-testnet-faucet.md) Reviewed: 11 Aug 2026 (2026-08-11). Bottom line: The official testnet faucet currently requires the same address to have deposited on mainnet, then provides 1,000 mock USDC. Testnet assets have no monetary value. ## Current faucet requirement To use the official faucet, the same wallet address must first have deposited on mainnet. The faucet at app.hyperliquid-testnet.xyz/drip currently distributes 1,000 mock USDC for testing. The requirement does not make testnet funds real or redeemable. Never pay someone for faucet assets and never send real capital to a testnet address. ## Email login can use different addresses The official documentation warns that email onboarding can generate different wallet addresses on mainnet and testnet. Different wallet addresses break the same-address faucet requirement unless the mainnet email wallet is exported and connected separately. Exporting reveals a private key. Use a secure device and never paste the key into a website. Consider using a dedicated development wallet instead of reusing an account with meaningful funds. ## Use the exact testnet endpoints The testnet app is https://app.hyperliquid-testnet.xyz. The faucet is at /drip on the same app domain. The testnet HTTP API is https://api.hyperliquid-testnet.xyz, and the testnet WebSocket endpoint is wss://api.hyperliquid-testnet.xyz/ws. Keep mainnet and testnet endpoints, chain IDs, keys and asset identifiers in explicit configuration. The application must stop when an environment value is missing. It must not select mainnet as a default. Use visible network labels in logs and interfaces. Test order placement, cancellation, reconnects, reduce-only behavior and error handling before enabling any real-money signing path. Code: ~~~~text App https://app.hyperliquid-testnet.xyz Faucet https://app.hyperliquid-testnet.xyz/drip HTTP API https://api.hyperliquid-testnet.xyz WebSocket wss://api.hyperliquid-testnet.xyz/ws ~~~~ ## What testnet cannot prove Testnet can validate signatures, request shapes and state transitions. It cannot reproduce mainnet liquidity, slippage, congestion, fills, funding regimes or economic incentives. After testnet, run a minimal mainnet lifecycle with small size and strict limits. A successful mock fill is not evidence that a production strategy is profitable or safe. Record which assumptions were validated on testnet and which still require a capped mainnet check. The record separates a correct signature test from execution, liquidity and profitability evidence. ## Frequently asked questions ### How much mock USDC does the Hyperliquid testnet faucet provide? The official testnet onboarding page currently documents a 1,000 mock-USDC drip. The assets have no monetary value and the faucet rule can change. ### Why can the faucet reject an email-login account? Email onboarding can produce different wallet addresses on mainnet and testnet, while the faucet requires the same address to have deposited on mainnet. The official documentation describes exporting and connecting the mainnet email wallet as a workaround. ## Official sources - [Hyperliquid Docs: Testnet faucet](https://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/testnet-faucet): Official source used for the product claims on this page. - [Hyperliquid Docs: API](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api): Official source used for the product claims on this page. - [Hyperliquid Docs: WebSocket](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/websocket): Official source used for the product claims on this page. - [Hyperliquid official Python SDK](https://github.com/hyperliquid-dex/hyperliquid-python-sdk): Official source used for the product claims on this page. - [Hyperliquid Docs: Export an email wallet](https://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/export-your-email-wallet): Official source used for the product claims on this page. ## Related pages - [Hyperliquid API, WebSocket and Python SDK guide](https://hyperliquidreferralcodes.com/api-websocket-python): Related guide. - [Hyperliquid wallet and login guide: email, Web3 and mobile](https://hyperliquidreferralcodes.com/hyperliquid-wallet-login): Related guide. - [HyperEVM wallet setup: RPC, chain ID, gas and transfers](https://hyperliquidreferralcodes.com/hyperevm-wallet-rpc): Related guide. ## Publication details - Publisher: Hyperliquid Field Guide. - Status: Independent and unaffiliated with Hyperliquid Labs and the Hyperliquid Foundation. - Reviewed: 11 Aug 2026 (2026-08-11). - Affiliate disclosure: The site operator may earn protocol referral rewards when eligible users trade with code AWD. Hyperliquid controls eligibility, attribution and rewards. - Contact: research@hyperliquidreferralcodes.com. - Product terms: Check the linked official documentation and the official Hyperliquid app before you act.