# Security #### Audit Plans and Methodology Security in DeFi begins with audited contracts. Amara inherits a strong foundation by forking from **GMX V2**, a system that has already been extensively reviewed by multiple third-party security firms. By starting from a proven base, Amara reduces the surface area for vulnerabilities and avoids many of the risks common to untested code. In addition to the inherited audits from GMX, Amara has taken further steps to validate its unique components. The **Dione Oracle contracts**, which secure price feeds for synthetic carbon credits, were independently audited. This review covered both the core oracle infrastructure and the consumer-facing contracts that deliver Chainlink-style price data to trading modules. The focus of this audit was on: * Accuracy of price aggregation and validation logic * Protection against stale or manipulated submissions * Upgradeable contract safety using OpenZeppelin standards * Compatibility with future feed integrations Amara’s methodology is to combine **proven, audited base layers** with **specialized audits for new modules**. By layering reviews in this way, the protocol ensures both the robustness of inherited code and the reliability of its unique innovations. Future audits will continue as Amara expands. New features, such as the Green Basket Index or expanded synthetic markets, will be reviewed before deployment. This ensures that each stage of protocol growth is backed by the same level of scrutiny that underpins its launch. --- # 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.amara.exchange/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.