# Bug Bounty ![](https://2642926184-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaBnhYO5U0xRgxJs7vp%2F-MeOFxpKPBmXXQXc0cXZ%2F-MeOGxUeTBJY3Gansgvg%2FIMG_5730.PNG?alt=media\&token=b4bf65fd-bcda-44b6-a3c0-c022e6901e38) Welcome to Port Finance’s Bug Bounty Program. We want Port Finance to be as secure as it can be, so we're calling on our community to help us find any bugs and vulnerabilities. Submit a bug to **** and earn rewards of up to $100,000 USD. Please see below our program details and rules for reporting a bug! ## Bug Bounty Program Details Rewards for Bug Bounties will be assessed based on an internal rated scale * Critical: Up to $100,000 * High: Up to $10,000 * Medium: Up to $1,000 * Low: Up to $250 ## Bug Bounty Rules * Public disclosure of a vulnerability would make it ineligible for a reward * Duplicated issues are not eligible for reward*,* only the first submission will be eligible * Rewards will be distributed at the full discretion of the Port Finance team based on the criteria * Discovered vulnerability of the bug must be reported only to the Port Finance team via email to **** * For UI related issues and feature request please report using Github Issues [here](https://github.com/port-finance/bug-bounty) for best response time and prize distribution ## Suggested Bug Bounty Report Template *Name:* *Discord ID:* *SPL Wallet Address:* *Description:* *Vulnerability:* *Components that are affected:* *Any other details:* *(Attach any relevant screenshots or documentation)*
--- # Agent Instructions: 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: ``` GET https://docs.port.finance/security/bug-bounty.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.