> For the complete documentation index, see [llms.txt](https://learn.trovemarkets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.trovemarkets.com/trove-x-polymarkets.md).

# Trove x Polymarkets

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

{% embed url="<https://x.com/TroveMarkets/status/2008998374536827230?s=20>" %}

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.

***

### What this docs pack covers

* **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

***

### Important notes

* 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.trovemarkets.com/trove-x-polymarkets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
