> For the complete documentation index, see [llms.txt](https://docs.gridlock.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridlock.network/guardians/all-about-guardians/why-cant-a-guardian-steal-my-crypto.md). # Why can't a Guardian steal my crypto? Multi-Party Computation (MPC) is a key feature of Gridlock's mobile wallet that enhances security by preventing theft from any individual node in the network. MPC works by dividing the user's private keys into shares that are distributed across multiple parties. Each party holds only a portion of the private key and has no complete access to the user's assets. This means that even if one party's node is compromised, an attacker cannot gain full access to the user's private key or steal their crypto. To complete a transaction, a certain threshold of parties must collaborate and contribute their key shares. This threshold ensures that no single party can perform a transaction alone without the involvement of others. By distributing the private keys in this way, Gridlock's wallet eliminates the risk of a single point of failure, making it extremely difficult for any individual node to steal the user's crypto assets. This advanced MPC technology provides a high level of security and gives users peace of mind when managing their digital assets with Gridlock. --- # 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://docs.gridlock.network/guardians/all-about-guardians/why-cant-a-guardian-steal-my-crypto.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.