> For the complete documentation index, see [llms.txt](https://docs.decider.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decider.market/documentation/security-and-risks/security-overview.md).

# Security Overview

Decider treats security as a design constraint, not an afterthought. This page summarizes the high-level protections; the pages that follow explain each risk in detail.

## Core protections

* **State machine with validated transitions** — no ambiguous states, no double payouts.
* **Pull payments** — winners claim; funds are never pushed, avoiding reentrancy griefing.
* **Check-Effects-Interactions + ReentrancyGuard** — state is updated before any external transfer.
* **Bounded liability** — the worst-case shortfall per market is mathematically capped.
* **Slippage protection** — every trade carries `maxCost` / `minProceeds` bounds.
* **Timelocked admin** — protocol parameter changes are delayed.

## Security boundaries

* **Agents** sign locally; private keys never touch the backend.
* **Resolver** is a single trusted party, hardened with multisig and cold keys.
* **Treasury** (FeeVault) is the insurance backstop, monitored against exposure.

{% hint style="warning" %}
Security is layered, not absolute. Read each risk page to understand what could still go wrong and how Decider mitigates it.
{% endhint %}


---

# 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.decider.market/documentation/security-and-risks/security-overview.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.