> For the complete documentation index, see [llms.txt](https://doracleofficial.gitbook.io/doracle-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doracleofficial.gitbook.io/doracle-whitepaper/bug-bounty.md). # Bug Bounty To ensure the security and stability of Doracle, we establish a Bug Bounty program to encourage security researchers and ethical hackers to discover and report vulnerabilities and security issues in the Doracle system. The Bug Bounty program will cover security vulnerabilities in the Doracle system and its related components. This includes but is not limited to smart contract vulnerabilities, network attacks, data source contamination, data tampering, and other related issues. Different reward levels will be set based on the severity and impact of the discovered vulnerabilities. The higher the severity and impact, the higher the reward will be. Security researchers and ethical hackers can submit vulnerability reports through designated channels. We will ensure the confidentiality of the reporter's identity and information and promptly handle the reports. Once a vulnerability report is validated, rewards will be given in the form of DRC tokens from DAO Treasury. The number of tokens awarded will be assessed based on the severity and impact of the vulnerability. --- # 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://doracleofficial.gitbook.io/doracle-whitepaper/bug-bounty.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.