# Protection Fund Bugs and errors in software are inevitable, as seen in the history of blockchain from Bitcoin’s two unintentional hard forks to The DAO incident during Ethereum’s early days. Planning ahead for such scenarios is a wise approach to mitigating risks and protecting against potential vulnerabilities. The Morpheus [Tokenomics](/tokenomics.md) allocates 4% of all MOR emissions to the **Protection Fund**, which can be used in the following cases: * Discovery and responsible disclosure of vulnerabilities in [Morpheus Smart Contracts](/smart-contracts.md) through the [Bug Bounty Program](/security-audits/morpheus-bug-bounty-program.md). * Payments for [cybersecurity audits](/security-audits.md) of Morpheus Smart Contracts. * Compensation for user losses caused by attacks or bugs in Morpheus software. * Other initiatives aimed at strengthening the ecosystem’s security. The Protection Fund is managed by the community-controlled [Multisignature Accoun](/smart-contracts/multisig.md)t, with claims made quarterly. A draft process for payments approval and release is available on [GitHub](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md) and is still under discussion. Additionally, there is a community-proposed concept for [Protection Fund Diversification](https://github.com/MorpheusAIs/MRC/blob/main/PENDING/MRC23.md)**.** \ \ You're welcome to join the discussion on [Discord.](https://discord.com/channels/1151741790408429580/1215401416659832842) --- # 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://gitbook.mor.org/security-audits/protection-fund.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.