> For the complete documentation index, see [llms.txt](https://spherex-4.gitbook.io/spherex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spherex-4.gitbook.io/spherex/program/bug-bounty.md). # Bug Bounty Security is a core value at SphereX, and we highly value the contributions of security researchers and developers. To recognize and reward white-hat hackers and security experts, we’ve launched the **Bug Bounty Program**, aimed at identifying vulnerabilities, bugs, or potential security risks on the platform. Through this program, researchers can submit vulnerability reports related to SphereX and receive tiered rewards based on the severity and potential impact of the issue. The program covers a wide range of areas, including SphereX’s smart contracts, frontend applications, APIs, and other platform-related technical components. This initiative is key to enhancing the platform’s security and reliability, ensuring a safer and more trustworthy decentralized financial experience for users. SphereX’s Bug Bounty Program encourages responsible disclosure, providing the security community an opportunity to showcase their skills and contribute to the platform’s security. All submitted reports will be rigorously reviewed to ensure that vulnerabilities are promptly addressed and resolved. --- # 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://spherex-4.gitbook.io/spherex/program/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.