# Bug Bounty Yield Yak has set aside a Bug Bounty budget of **100 YAK** for responsible disclosure of bugs. ## Reporting Issues If you find a problem or vulnerability with any Yield Yak contract, please share the information with a developer (as soon as possible). [Telegram](https://t.me/yieldyak) provides direct access to developers. Users tagged with "Yak Guide" can also provide access to developers. Alternatively, use [Twitter](https://twitter.com/yieldyak_). Bug bounties will be awarded for being the first to report a severe security issue (e.g. one which results in the change of code or configuration), with a reasonable amount of time given for resolving the issue. The exact amount of a bug bounty will vary, based on different factors, including whether or not user funds are at risk and a subjective measure of the risk. While we introduce a budget, there is no guarantee that the budget will be fully distributed or realized by any individual report or reporter. --- # 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.yieldyak.com/for-developers/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.