> For the complete documentation index, see [llms.txt](https://funarchy.gitbook.io/funarchy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funarchy.gitbook.io/funarchy/security-for-prediction-market/configuration.md).
# Configuration
configuration
This page addresses the structural threats that arise during the process of defining events and setting parameters, which form the foundation of prediction markets. The market topic, RuleBook, time settings, and State are the core elements that determine the ‘rules of the game’ under which the smart contract will execute.
> If rules are ambiguous or parameters are incorrectly set during the initial configuration phase, the market cannot function properly no matter how technically secure the code is. This directly leads to serious security incidents such as frozen funds or improper settlements.
Therefore, we must establish not only clear definition requirements for designing a “decision-capable” market but also parameter verification strategies to safely control the market's lifecycle.
This page presents security principles for the design phase, focusing on eliminating ambiguities in the rulebook regarding market topics and managing operational stages safely.
### Market Design & Creation Flow
---
# 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://funarchy.gitbook.io/funarchy/security-for-prediction-market/configuration.md?ask=&goal=
```
`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.
