> For the complete documentation index, see [llms.txt](https://docs.elixir.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elixir.xyz/technical-architecture/fraud-proofs.md).

# Fraud Proofs

Security is at the core of Elixir's network. On the technical process flow, the auditor and controller infrastructure ensures that the data broadcasted to exchanges are honest and accurate.

The auditor infrastructure monitors inputs / outputs within the network, while the controller infrastructure resolves conflicts that could arise as a result of inconsistencies in outputs. This helps guarantee accuracy within the network and blocks any potentially malicious actions from validators who may attempt to output data that could prove harmful to the strategies and users.

### Auditors

Auditors work to keep the rest of the network honest. The auditor monitors the inputs and outputs from each of the various actors in the network, and in the case of a discrepancy (either reported or observed), an auditor submits a proof of malicious activity to the ETH slashing smart contract in the controller in exchange for a bounty. The bounty will be extracted from the validator's stake and credited to the auditor. 

Finally, the auditors are responsible for ensuring validator uptimes for purposes of staking rewards.

### Controller (smart contract)

The controller smart contract is responsible for managing staking, delegating, rewards, jailing, and slashing. In the case of a dispute, the controller checks for 2/3rds consensus within the active validator set, and can slash the malicious validator. In the case of excessive downtime, the controller enables jailing the offending validator.


---

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

```
GET https://docs.elixir.xyz/technical-architecture/fraud-proofs.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.