> For the complete documentation index, see [llms.txt](https://docs.degate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degate.com/security-and-self-custody/bug-bounty.md). # Bug Bounty DeGate runs an active bug bounty: vulnerability reports go to . If you believe you have found a security issue in DeGate’s live products, we want to hear from you before anyone else does. The bounty complements the audit coverage described in [Audits](https://docs.degate.com/security-and-self-custody/audits). ## What we look for The bounty covers DeGate as users actually run it: * The web app ([app.degate.com](https://app.degate.com/)) * The iOS and Android apps The most useful reports show an issue reproduced against the current production release, with a clear description of what a real user or DeGate could lose. Rewards are assessed on demonstrated impact in the live product. ## How to report Email with: * A description of the issue and its impact * Steps to reproduce against the live product (proof of concept if possible) * The component affected (mobile app, web app, on-chain program) and, for on-chain programs, the program ID * An address or contact for follow-up and any reward Please practice responsible disclosure: give us reasonable time to investigate and fix before publishing details. Please do not test against other users’ funds or accounts.
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.degate.com/security-and-self-custody/bug-bounty.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.