> 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/hip-3/upcoming-markets.md).

# Upcoming markets

After our initial markets, Trove will expand through the HIP-3 Dutch auction system. Each additional auction slot allows one additional perpetual market to be listed.

> [Learn about HIP-3 spec here](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals#spec)

* HIP-3 auctions run at fixed intervals with preset parameters (frequency, minimum price).
* Deployers bid to secure listing rights for new assets.
* Winning a slot grants full configuration control over the new market.
* The original 500k HYPE stake remains constant; no extra staking is needed.

{% hint style="info" %}
*Auctions, not stake size, determine who expands the ecosystem.*
{% endhint %}

***

### Next markets

Trove’s might include additional collectible indices such as:

* Yu-Gi-Oh! Index
* Magic: The Gathering Index
* One Piece TCG Index
* Sports Card Index


---

# 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, and the optional `goal` query parameter:

```
GET https://learn.trovemarkets.com/hip-3/upcoming-markets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.