> For the complete documentation index, see [llms.txt](https://naviprotocol.gitbook.io/navi-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program.md). # Bug Bounty Program NAVI Protocol is committed to maintaining a safe and reliable platform. We run an ongoing Bug Bounty Program in collaboration with [Hackenproof](https://hackenproof.com/companies/navi-protocol), inviting security researchers to responsibly disclose potential vulnerabilities.\ All submissions are reviewed and triaged by Hackenproof, with rewards based on severity and impact. ### Rewards * Up to $300,000 for critical smart contract vulnerabilities * Up to $10,000 for web and frontend vulnerabilities Exact reward amounts, severity definitions, and scope details are determined by Hackenproof and the team. ### Scope The program covers: * NAVI Protocol smart contracts * NAVI web application and related interfaces ### Reporting All vulnerability reports must be submitted via Hackenproof. Reports submitted through other channels will not be eligible for rewards. --- # 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://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program.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.