# How to ensure fairness in predictions?

### **We adopt a triple mechanism:**

* <mark style="color:orange;">**Multiple decentralized oracle:**</mark> Event results are automatically verified by on chain data sources;
* <mark style="color:orange;">**Community supervision:**</mark> Users can initiate voting arbitration for disputed events (comingsoon) ;
* <mark style="color:orange;">**Blacklist mechanism:**</mark> addresses that maliciously create false events will be permanently banned.

***

### Who Should Use ForeGate?

* <mark style="color:orange;">**Traders & Analysts**</mark> – Use prediction markets as an alternative investment tool.
* <mark style="color:orange;">**Crypto & DeFi Enthusiasts**</mark> – Hedge volatility and capitalize on market trends.
* <mark style="color:orange;">**Sports & Esports Fans**</mark> – Engage in game outcomes and test your knowledge.
* <mark style="color:orange;">**Tech & Business Observers**</mark> – Forecast emerging trends and industry shifts.
* <mark style="color:orange;">**Content Creators & Community Builders**</mark> <mark style="color:orange;"></mark><mark style="color:orange;">–</mark> Launch engaging markets and monetize your insights.


---

# Agent Instructions: 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:

```
GET https://foregate.gitbook.io/foregate-docs/readme/what-is-foregate/how-to-ensure-fairness-in-predictions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.