> 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/smart-contract-risks.md).

# Smart Contract Risks

Smart contracts can contain bugs. No amount of testing eliminates this possibility entirely.

## The risk

A vulnerability in the market, factory, vault, or identity contracts could lead to lost or stolen funds.

## Mitigations

* **Independent audit** before meaningful TVL — mandatory, not optional.
* **Foundry test suite** — unit, fuzz, and invariant tests (128,000 randomized calls), currently green.
* **Reuse of proven code** — OpenZeppelin libraries rather than hand-rolled primitives.
* **Audited math libraries** — PRBMath/ABDK for the LMSR `exp`/`ln`, never native `exp()`.
* **Bug bounty** and **timelocked upgrades**.

## What you should know

* The contracts are **experimental software**. Use them accordingly.
* TVL is intentionally capped early while the system proves itself.

See Experimental Software.


---

# 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/smart-contract-risks.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.