> For the complete documentation index, see [llms.txt](https://rektofun.gitbook.io/rektofun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rektofun.gitbook.io/rektofun/introduction/how-events-are-resolved.md).
# How Events Are Resolved?
### **1. Price-Based Challenges**
* Fully **automated and on-chain verified**
* Uses external price data (via Binance API)
* No human intervention required
* Ensures fast, transparent, and trustless settlement
### 2. Real-World Event Challenges
* Only **Rekto Masters NFT** holders are eligible to participate in challenge validation and outcome resolution.
* PvP challenges require a minimum of 75 validator votes before an outcome can be finalized.
* Multi-mode pool challenges require at least 150 validator votes to reach resolution.
* Validators are required to stake a small security deposit in **$REKTO token** before participating in the validation process, ensuring accountability and fair participation.
* Validators who consistently vote against the final verified outcome are penalized, creating strong incentives for honest and accurate resolutions.
* After a challenge is resolved, participants are given a 3 hour dispute window to challenge the result. To raise a dispute, users must also stake funds. Malicious or incorrect disputes are penalized, and repeated dishonest behavior can lead to slashing and removal from the validation ecosystem.
---
# 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://rektofun.gitbook.io/rektofun/introduction/how-events-are-resolved.md?ask=&goal=
```
`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.