# Security If you would like to reach out to us regarding a potential vulnerability, please reach out to us at ## Security assumption Opus as a protocol hinges on the critical assumption that the admin for its smart contracts is honest. Other than the admin, access control should be granted to smart contracts of Opus only, and not to any other users. A compromised or malicious admin can cause catastrophic damage across the entire protocol. It is a conscious design decision that this role is not behind a time lock. Priority is given to the ability to rapidly update and iterate on existing modules and components without interruption. It also avoids downtime whenever there is a bug or security vulnerability that needs to be fixed. Trusting the admin to be honest is a prerequisite to trusting Opus' smart contracts. --- # 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.opus.money/current/technical-documentation/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.