> For the complete documentation index, see [llms.txt](https://seerdex.gitbook.io/seerdex-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seerdex.gitbook.io/seerdex-whitepaper/security.md).

# Security

Security is a foundational priority for Seerdex. The protocol incorporates multiple layers of protection.

**Decentralized, multi-oracle resolution** reduces the risk of any single point of failure or manipulation during settlement.

**Economic safeguards** are built into the design to discourage manipulation, particularly in low-liquidity markets.

**AI validation** further reduces risk by preventing the creation of malicious or ambiguous markets before they reach the blockchain.

**Staking requirements** for market creators introduce accountability and align incentives toward maintaining high-quality listings.

Together, these measures protect everyday users and give the protocol the resilience needed to operate at scale. All core smart contracts will undergo comprehensive independent audits prior to mainnet launch, with reports published publicly.


---

# 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://seerdex.gitbook.io/seerdex-whitepaper/security.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.