> 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/the-tech/multi-party-computation.md). # Multi-Party Computation Multi-party computation (MPC) is a cryptographic technology that allows multiple groups to run a program together. Instead of one computer doing the processing, numerous distributed computers work together in a private and protected way. Gridlock ensures security by preventing any one entity from controlling all of the keys required to sign a transaction. They collectively have the whole key, but each only has a small piece, and the transaction must collect enough of them to work. That way, even if one of your devices gets hacked, you are safe because the attacker will have to hack a lot of other nodes in the network to get your secured assets. Gridlock uses MPC in conjunction with Threshold Signatures technology to protect transactions. Threshold Singatures enables the wallet to sign a transaction using a subset of key shares, so even if some of the shares are lost or stolen, the wallet stays safe and operational. --- # 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/the-tech/multi-party-computation.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.