> For the complete documentation index, see [llms.txt](https://docs.bounce.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bounce.tech/technical/risks-and-security.md). # Risks & Security Bounce has been designed and built with security in mind. The core team continues to test both new and existing components of the protocol on an ongoing basis as the protocol continues to evolve. However, please keep in mind that DeFi comes with its own inherent risks and that Bounce integrates with various other protocols. While the core team tries to provide sufficient documentation on all Bounce components, please reach out on [Discord](https://discord.com/invite/T8DvHhCrGV) if there are any questions regarding risks on Bounce. ### Audits For details on the audits Bounce Tech has conducted, please view the audits page on the Bounce Tech website: ### Report Bugs or Vulnerabilities If you have found a potentially bug or vulnerability, please reach out to us on Telegram at `chase_manning` or `chucklingchuck` . And if you can't get in touch there, try us on [Discord](https://discord.com/invite/T8DvHhCrGV). --- # 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.bounce.tech/technical/risks-and-security.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.