> For the complete documentation index, see [llms.txt](https://docs.aura.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aura.finance/aura/governance/multisig-composition.md). # Multisig Composition Multisigs will be used for the initial bootstrapping of the project and for governing key parameters. In order to bolster decentralisation Aura will utilise a number of multisig wallets (Gnosis Safe) for specific entities. The structure will consist of the following multisigs: ### Protocol Multisig Initially consisting of 7 signers (4/7 majority needed). The proposed delegation of the signature keys are as follows: * 3 x Aura contributors * 2 x Balancer Ballers * 2 x Reputable/known DeFi community members ### Treasury Dao Keeping with the intention of Aura being a community owned protocol, its funds will be no different. All treasury keys will be delegated to respected community members across the Defi space with no prior or current affiliation with Aura. The treasury will initially consist of 7 signers with a 4 sig majority required: * 2 x Aura affiliates * 5 x Reputable/known DeFi community members ### Multi-sig Evolution [AIP-8 Multisig best practices Framework](https://forum.aura.finance/t/aip-8-multi-sig-best-practices-framework/142) was approved by governance and is now used to ensure the multi-sig remains active. While at the time of this writing, the current breakdown of signers remains accurate, it may change in the future based on regular governance assessing multisig livliness such as [AIP-16](https://forum.aura.finance/t/aip-16-multisig-performances-updates/220/7). --- # 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, and the optional `goal` query parameter: ``` GET https://docs.aura.finance/aura/governance/multisig-composition.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.