> 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/operation.md). # Operation This chapter manipulate the structural risks arising from the operational authority of prediction markets and management system that supports them. No matter how technologically perfect a smart contract, if the authority of the administrator controlling it is excessive or the internal settlement logic is not robust, trust cannot be maintinan in system. This is because security at the operational level simultaneously includes the issue of transparency regarding ‘who controls the system’ and the issue of stability regarding ‘whether the system operates without errors.’ If operation authority is not transparently distributed or flaws in the state management logic are left unattended, the market faces critical risk such as arbitrary manipulation, unexpected denial of service, and asset freezing. Thus, this chapter presents essential security principles that must be in place during the operational phase, focusing on privilege management to prevent abuse of administrator authority and management logic integrity to ensure stable system operation. --- # 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/operation.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.