> 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-trading-architecture.md).

# Kalshi: Trading architecture

<figure><img src="/files/0tJcuGu99eJ6d35FSSxN" alt=""><figcaption></figcaption></figure>

### Oracle design for Kalshi markets

For these listings, the external “Validator” leg is anchored to Kalshi’s mid-price (venue-normalized). The full oracle follows your tri-blend:

```
Oracle = (Mark + Validator + EMA) / 3
```

{% content-ref url="/pages/uIeNNcTP4nxInEYb2iLz" %}
[Oracle design](/oracle/oracle-design.md)
{% endcontent-ref %}

* Validator: Kalshi price (cleaned for staleness; mid or last within guardrails)
* Mark: Trove last traded price (our internal market)
* EMA: Smoother on Trove internals (HyperPS)
* Dynamic weights (Beta): Guardrails allow higher Validator influence while Trove depth is young

If Kalshi is stale or paused: Validator weight reduces automatically; EMA/Mark weights rise within published limits. Circuit breakers and deviation bands apply.

***

### Funding & convergence

Funding aligns Trove’s Mark to the Oracle (which reflects Kalshi):

```
Premium index P: (Mark−Oracle)/Oracle
```

{% content-ref url="/pages/fjmDGQQBT2jgMaCqPhXo" %}
[Funding rates](/oracle/funding-rates.md)
{% endcontent-ref %}

**Arbitrage intuition**

* If Trove < Kalshi (discount): longs on Trove receive funding; classic long Trove / short Kalshi basis trade
* If Trove > Kalshi (premium): shorts on Trove receive funding; short Trove / long Kalshi hedge

As expiry approaches, both prices should converge toward {0, 100}; funding accelerates this.


---

# 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-trading-architecture.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.