# Bug bounty ### Overview Folks Finance considers the security of its users as its highest priority. Alongside audits successfully completed with [Trail of Bits](https://www.trailofbits.com/), [Certik](https://www.certik.com/), [Runtime Verification](https://runtimeverification.com/), [Coinspect](https://www.coinspect.com/), and [Vantage Point](https://www.vantagepoint.sg/), the bug bounty program is a fundamental addition. Therefore, Folks Finance launches a **$100,000** **Bug Bounty program** on [Immunefi](https://immunefi.com/bounty/folksfinance/) to increase the protocol's robustness. ### Rewards by Threat Level > Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. > > Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. > > High and Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of **USD 25 000** for Critical and **USD 5 000** for High. > > All vulnerabilities marked in the following Github repository [https://github.com/Folks-Finance/audits](https://github.com/Folks-Finance/audits?utm_source=immunefi) are ineligible for a reward > > **KYC** shall be completed for bug bounty hunters submitting a vulnerability report and requesting a reward for Critical and High Smart Contracts vulnerabilities. The basic information needed is full name, residential address, and passport details (DOB, issuing country and passport number). Based on the basic information submitted, Folks Finance team may request further information at its sole discretion for compliance with applicable Laws. > > Additionally, all levels of bug bounty hunters submitting a vulnerability report and requesting a reward need to submit certification that (i) they are not acting, directly or indirectly, for or on behalf of any person, group entity, or nation named by any Executive Order or the United States Treasury Department as a terrorist, “Specially Designated National and Blocked Person,” or other banned or blocked person, entity, nation, or transaction pursuant to any law, order, rule or regulation that is enforced or administered by the Office of Foreign Assets Control; and (ii) they are not engaging in, instigating or facilitating this transaction, directly or indirectly, on behalf of any such person, group, entity, or nation. They also need to submit an attestation that all information provided is true, correct, up-to-date and not misleading. The collection of this information will be done by the Folks Finance team. > > Payouts are handled by the **Folks Finance** team directly and are denominated in USD. However, payouts are done in **USDCa.** For more information visit the dedicated page on [Immunefi.](https://immunefi.com/bounty/folksfinance/) --- # 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.folks.finance/developer/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.