# Standard Operating Procedure for Security As protocol operators, we regularly receive security or bug reports that result in minor to major security concerns. As a rule of thumb, the team prefers to be on the safe side and advise liquidity providers to remove liquidity immediately upon a bug report that requires more than 24 hours to investigate. The team's main priority is keeping liquidity safe. There are upcoming features in development that will make this process easier but for now liquidity providers may sometimes be asked via our social channels, such as X (formerly Twitter) or Discord, to remove liquidity in the event of a bug report that requires more thorough investigation to ensure that various aspects of the protocol are not peripherally affected. --- # 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://xave-finance.gitbook.io/general/contract-audits/standard-operating-procedure-for-security.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.