> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/multisig.md). # Multisignature account As Morpheus develops in a fully decentralized and open-source manner, there is a need to deploy, manage, and upgrade Smart Contracts until all functions are fully automated in the future. A multisignature account is essential for ensuring transparency and security, especially since Morpheus contracts hold tens massive amount of ETH. ### Set Up Process and Key Holders Based on recommendations from cybersecurity experts and auditors, a [Gnosis SAFE](https://app.safe.global/) multisignature Smart Contract has been deployed on the [Ethereum](https://etherscan.io/address/0x1FE04BC15Cf2c5A2d41a0b3a96725596676eBa1E), [Base](https://basescan.org/address/0xf3ef00168dd40eae68a7e670d56c7b8724e0c183) and [Arbitrum](https://arbiscan.io/address/0x151c2b49CdEC10B150B2763dF3d1C00D70C90956) chains. This setup requires 5 out of 9 key holders to sign transactions: * All key holders are trusted community members. * Each key holder has extensive experience in cybersecurity and between 6 to 12 years in the crypto space. * The key holders are geographically and jurisdictionally diverse. * None of the key holders belong to the same company. * For personal security reasons, the identities of the key holders will remain confidential. ### Multisignature Evolution It’s important to note that the key holders have minimal control over the Smart Contracts. Most of the contract functions cannot be modified by the admin (which is controlled by the multisig). As the Smart Contracts evolve and mature, it is expected that the admin key may eventually become unnecessary and burned. However, this decision must be carefully considered, as it would make future upgrades by the community more difficult. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/multisig.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.