> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/6.-resources-documentation-and-terms/faq/transaction-management/why-do-multi-signature-wallets-require-all-parties-to-be-online-simultaneously.md). # Why Do Multi-Signature Wallets Require All Parties to Be Online Simultaneously? Other wallets implement multi-sig through a separate signing approach. After one party completes their signature, the platform stores that party's key share in the cloud and then waits for the other party to sign. However, this approach is equivalent to the platform temporarily holding the complete private key, which poses a significant security risk. To safeguard user assets, Cregis adopts a more rigorous security design to avoid such practices. Cregis's multi-sig feature is based on MPC (Multi-Party Computation) technology, where the user's private key never exists in its complete form. During the signing process, each party's key share interacts in real time through cryptographic protocols to complete the signature, without any party needing to store their share in the cloud. This ensures the absolute security of the private key while eliminating the potential risks associated with centralized storage. Therefore, Cregis's multi-sig requires all parties to be online simultaneously in order to complete the signature through real-time interaction, preventing any party's key share from being stored in the cloud and thereby ensuring the private key remains secure at all times. --- # 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://support.cregis.com/6.-resources-documentation-and-terms/faq/transaction-management/why-do-multi-signature-wallets-require-all-parties-to-be-online-simultaneously.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.