> For the complete documentation index, see [llms.txt](https://docs.prophetmarket.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prophetmarket.ai/reference/on-chain-first.md).

# On chain first

*Why the interface sometimes waits, and what to do when it does.*

Prophet's core rule is that the blockchain is the source of truth. Nothing appears in the application until it has been confirmed on chain. Your click submits a transaction to Polygon, Prophet's event listener sees the confirmed event, and only then does the interface update.

**The sequence**

```
your click  →  transaction submitted to Polygon
            →  Polygon confirms
            →  event listener observes it
            →  interface updates
```

## What this feels like in use

| Observation                                                     | Cause                                                                                                             |
| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| A short delay between clicking and seeing the result            | Polygon confirming the transaction. Usually minutes.                                                              |
| Everything slower than usual                                    | Polygon congestion. Prophet slows proportionally and cannot bypass it.                                            |
| A trade that simply does not fill                               | An on chain condition failed at settlement time, for example an insufficient balance at the moment of settlement. |
| A balance that looks right but a trade that will not go through | The interface is still catching up to on chain reality.                                                           |

{% hint style="success" %}
**If a trade will not go through, wait and refresh**

When the displayed balance looks sufficient but an order is rejected, the interface has not yet reconciled with the chain. Give it a moment and refresh, and the balance you see will match what the chain actually holds.
{% endhint %}

## Why accept the delay

The alternative is an interface that reports a state the chain has not yet agreed to, which means showing balances and fills that can later be contradicted. Prophet accepts a slower interface in exchange for one that never tells you something the chain does not already support.

The same principle is why the twelve hour review window after resolution cannot be shortened. It is enforced by a contract on Polygon, not by Prophet's servers, and Prophet has no privileged ability to override it.


---

# 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://docs.prophetmarket.ai/reference/on-chain-first.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.