You can launch a HIP-4 binary price market through Purrdict on Hyperliquid Testnet. The current flow requires Standard mode, at least 100 staked HYPE, a one-time outcome-deployer activation, and a validator-approved template. Purrdict prepares and validates the action; your wallet signs it.
What you need before launching
The Launchpad checks eligibility before showing the deployment form. The protocol—not a Purrdict allowlist—determines whether an account can activate and deploy.
You also need a 2–4 character lowercase venue name. The name is global and permanent. Treat it like a protocol namespace, not a disposable display name.
How to create a HIP-4 market
- Prepare the wallet. Use Hyperliquid Testnet, switch the account to Standard mode, and stake at least 100 HYPE to a validator.
- Activate a venue. Choose a globally unique 2–4 letter lowercase venue name. Activation is a one-time signed action and the name is permanent.
- Choose the template. Select an eligible production perp as the underlying and configure the target price and UTC expiry accepted by the current binary-price template.
- Review the action. The Launchpad shows the exact deployment fields, validates limits and tick-compatible values, and asks the connected wallet to sign.
- Launch and monitor. After Hyperliquid accepts the action, the outcome appears under the deployer's venue and becomes available to compatible testnet interfaces.
The activation payload is an activateOutcomeDeployer action. Deployment then uses Hyperliquid's template-based outcome registration path. The Launchpad keeps those details visible so builders can verify what the wallet is being asked to sign.
What markets can you launch?
The current Purrdict flow creates binary price outcomes: questions such as whether an eligible underlying will finish above a target at a specified UTC expiry. The underlying must come from the healthy production-perp set exposed by Hyperliquid, and the action must satisfy template and uniqueness checks.
This is intentionally narrower than a blank “ask anything” form. Templates make market data parseable, keep settlement inputs consistent, and reduce the chance that a deployer signs a malformed action. Hyperliquid can add or change validator-approved templates independently of Purrdict.
Observed rules include a maximum of 10 active outcomes per deployer and 50 deployments per day. These are protocol-side limits and may change; the Launchpad reads current eligibility instead of promising permanent quotas.
Your wallet signs. Your venue launches.
Purrdict does not ask you to paste a private key. It does not hold a server-side deployer key on your behalf. The browser prepares the exact keyword/value pairs required by the selected template, shows the important parameters, and sends the action to the connected wallet for approval.
Once accepted, the market is associated with the deployer's venue in Hyperliquid outcome metadata. Other compatible interfaces can discover it. Purrdict is a launch interface, not the owner of every market launched through it.
Launching is not the end of the job
A market needs clear parameters, liquidity, monitoring, and correct settlement. Permissionless deployment gives the deployer power, but it does not guarantee traders, a fair order book, or a good market.
- Choose unambiguous parameters. Underlying, target, and expiry must express one testable result.
- Plan liquidity. A new order book with no maker is technically live but practically unusable.
- Monitor active-outcome limits. Expired or unresolved markets can consume venue capacity.
- Understand settlement. Standard HIP-4 winning fills record a settlement price of 1 and losing fills record 0; current settlement fills credit USDC automatically. Legacy testnet fixtures may still expose USDH, so the deployer must read the live template fields and follow its resolution path exactly.
- Communicate testnet status. Test funds have no monetary value and testnet behavior is not a mainnet promise.
Verification methodology
Hyperliquid does not currently publish one standalone permissionless HIP-4 launch specification. Purrdict verifies the flow against public info responses, signed testnet actions, accepted and rejected deployments, L1 records, and the Launchpad's live eligibility checks. Protocol-side limits may change independently of this page.
- Hyperliquid Asset IDs — official outcome asset representations used by trading integrations.
- Hyperliquid Info endpoint — official public market and account-data interface.
- hip4.fun launch reference — independently maintained summary of the observed testnet requirements and constraints.
Prediction market launch FAQ
Can anyone create a prediction market on Hyperliquid?
The current permissionless path is available on Hyperliquid Testnet to eligible outcome deployers using validator-approved templates. It is not an unrestricted arbitrary-question form, and mainnet permissions may differ.
Why is 100 HYPE required?
The current activation rule requires the account to stake 100 HYPE and use Standard mode before it can activate as an outcome deployer.
Can I change my venue name later?
No. The short lowercase venue name is globally unique and permanent after successful activation.
Does Purrdict receive my private key?
No. The Launchpad prepares the action, but the connected wallet signs it. Purrdict does not provide a private-key field or use a server-side signer for deployment.
Is the HIP-4 Launchpad on mainnet?
No. Purrdict's permissionless Launchpad is currently a Hyperliquid Testnet feature. Curated HIP-4 outcome markets are live on mainnet.