> For the complete documentation index, see [llms.txt](https://docs.yamata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yamata.io/using-yamata/predictions-market/security-and-transparency.md). # Security & Transparency ### Non-Custodial Architecture * **You control your funds**: Commitments locked in smart contracts, not held by Yamata * **No intermediaries**: Direct interaction with blockchain * **Trustless resolution**: Algorithmic distribution, no manual intervention ### On-Chain Transparency Every action is publicly verifiable: * Market creation parameters * All commitments and timestamps * Resolution submissions and challenges * Payout calculations and distributions ### Zero Platform Risk * **No market-maker exposure**: Yamata has no financial stake in outcomes * **Auditable code**: Smart contracts open source and audited * **Permissionless**: No ability to freeze or seize funds ### Smart Contract Security * **Modular architecture**: Extensible framework with secure base * **Multiple inheritance**: Diamond pattern for clean separation of concerns * **Rate limiting**: Quota management prevents spam * **Validation framework**: Versioned metadata ensures parameter correctness --- # 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.yamata.io/using-yamata/predictions-market/security-and-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.