> 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-kalshi/kalshi-market-criteria.md).

# Kalshi: Market criteria

### Market criteria

* Market type: Binary (Yes/No) only — no multi-choice markets in Beta
* Tenor: 6+ months to expiry at time of listing
* Selection: Only top-attention / top-volume Kalshi markets (curated list; see dashboard)

{% hint style="info" %}
These markets inherit Trove’s standard risk controls (OI caps, leverage bands, circuit breakers) and funding mechanics.
{% endhint %}

<figure><img src="/files/wCWWrWOXH5tSnka5SMGO" alt=""><figcaption><p>Resolves on Feb, 2027. View the Kalshi market <a href="https://kalshi.com/markets/controlh/house-winner/controlh-2026">here</a></p></figcaption></figure>

### Contract model

| **Field**            | **Definition**                                                             |
| -------------------- | -------------------------------------------------------------------------- |
| **Instrument**       | Linear, USD-quoted **binary perp** (0–100 pricing, where 100 ≈ “YES wins”) |
| **Quote**            | USDC (cash-settled)                                                        |
| **Payout intuition** | Profit scales with change in implied probability (price points)            |
| **Leverage**         | Up to **5×** (subject to market-specific bands)                            |

> A price of $**62.0** on Trove corresponds to a **62% implied probability** of the “YES” outcome.


---

# 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/trove-x-kalshi/kalshi-market-criteria.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.