> 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/project-information/transparency.md). # Transparency Decider is designed to be auditable, from the chain to the resolution log. ## What is public * **Chain state** — every trade, resolve, and claim is on-chain. * **Resolution history** — every market's final outcome and source. * **Test results** — the Foundry suite (unit + fuzz + invariant) is green. * **Contract deployment** — addresses and status are published. ## What is disclosed operationally * **Resolver identity** — currently a dev key, moving to multisig. * **Treasury status** — the FeeVault balance and insurance exposure. * **Audit status** — pending independent audit before significant TVL. ## What this enables Because the chain is the source of truth, anyone can independently verify that markets resolve correctly and that payouts match. The read-only spectator site is a mirror of that truth, not a separate authority. See Resolution History and Security & Risks. --- # 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/project-information/transparency.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.