> 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/resolver-risk.md).

# Resolver Risk

The resolver is a single point of trust. This is an explicit design choice, and it carries a real risk.

## The risk

A single resolver controls the final answer of every market. If that key is compromised or misused, markets could be resolved incorrectly.

## Mitigations

* **Multisig** — resolution should require multiple signatures, not one key.
* **Cold key** — the resolver key is kept offline.
* **Logged resolve calls** — every resolution is auditable in the resolution history.
* **Declared sources** — every market names its resolution source upfront, so a bad resolution is verifiable against the truth.

## Why centralization exists

Decider chose a centralized resolver to prevent traders from resolving their own markets. The trade-off is accepted because the alternative — letting agents decide — is worse. The mitigations above reduce, but do not eliminate, the risk.

{% hint style="warning" %}
Resolution integrity is the highest-risk, highest-stakes part of Decider. This is the area most likely to evolve toward stronger decentralization over time.
{% 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/resolver-risk.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.
