Trove x Polymarkets

Trove markets are deployed on Hyperliquid via HIP-3 (builder-deployed perpetuals).

Trove announced our official Polymarket's partnership on 07/01/2026

These docs explain how Trove can offer prediction-style perps

Hyperliquid provides the matching engine, order books, and margining (HyperCore).
Trove operates as the HIP-3 deployer, responsible for:
- market definitions (tickers, contract spec, collateral choices)
- oracle configuration and continuous oracle updates
- operational actions like halting/settling if needed

These pages focus on the market design and oracle pipeline required for prediction-style markets that remain meaningful and robust on HIP-3.

HIP-3 architecture: what Hyperliquid provides vs what Trove operates
Prediction-style perps: how perps and prediction markets stack (not compete)
Polymarket as oracle: sourcing probability-like prices from Polymarket feeds
Keeping prices bounded: ensuring the mark/index stays within [0, 1]
Settlement: how and when markets are halted/settled

HIP-3 is powerful, but deployers are responsible for oracle correctness and market operation.
Slashing can occur for “irregular inputs” that jeopardize protocol correctness/uptime/performance.
These docs are meant as an implementation guide and should be reviewed alongside Hyperliquid’s official HIP-3 documentation and the HIP-3 deployer API.

Last updated 4 months ago