> For the complete documentation index, see [llms.txt](https://docs.midas.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midas.app/security/standard-incident-response-protocol.md). # Standard Incident Response Protocol #### **Objective** The objective of Midas’ Standard Incident Response Protocol is to protect tokenholder interests, ensure market integrity and mitigate risk during times of market disruption. This protocol establishes a structured framework for responding to potential security threats, third-party exploits, or market anomalies that could impact mToken price stability. #### **Activation Triggers** The protocol is activated upon the detection of a security incident by internal monitoring systems or authorised third-party security providers. Activation may occur under the following conditions: 1. Identification of vulnerabilities in third-party protocols. 2. Detection of unusual onchain activity suggesting a potential exploit. 3. Indications of potential contagion effects that could threaten assets underlying mTokens. #### **Preventative Safeguarding Measures** Once triggered, the protocol implements a temporary suspension of specific platform functionalities to prevent further exposure. This phase is characterised by: * **Subscription and Redemption Pause:** Investing in and redeeming of affected mTokens is temporarily disabled. * **Precautionary Stance:** A suspension does not necessarily indicate a compromise of Midas’ infrastructure or exposure of a product, but rather an intentional move to verify safety before continuing operations. * **Public Disclosures:** Status updates are prominently displayed on the Midas website (). #### **Investigation and Resolution** During an active investigation, the team and strategy managers execute a coordinated response plan. An immediate investigation is launched to determine the scope of the alert and the degree of exposure, while assessing integrity of mToken pricing to ensure no deviation from underlying value has occurred. Efforts are prioritised to minimise the duration of the temporary measures. #### **Criteria for Service Restoration** Functionality is restored progressively only after the successful verification of the following benchmarks: 1. **Asset Security:** Confirmation that the underlying assets are fully secured. 2. **Oracle Reliability:** Verification that price oracles are providing accurate and reliable data feeds. 3. **Smart Contract Integrity:** Technical validation that all platform smart contracts are functioning according to specifications. #### **Information Channels** Real-time updates and notifications regarding the resumption of normal operations are provided through the following channels: * **Official Twitter Feed:** The primary source for incident timestamps and resolution announcements. * **Midas Website:** Banners with status updates on individual product pages: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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.midas.app/security/standard-incident-response-protocol.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.