> For the complete documentation index, see [llms.txt](https://whitepaper.opz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.opz.io/keyfusion/introduction-to-keyfusion.md). # Introduction to KeyFusion The KeyFusion protocol is a form of MPC (Multi-Party Computation) developed by OPZ. Offering users a highly secure, exceptionally fast, and simple solution to store and transfer digital assets while maintaining quick and easy access. There has been a growing interest in Multi-Party Computation (MPC) in recent years due to its potential to enhance privacy and security. As a subfield of cryptography, with MPC, the private key is broken into multiple shares, encrypted, and divided among several parties. This enables multiple trusted parties to collaboratively perform computations on private data without disclosing any information about the data to other participants. This means the entire key is never present on any device. However, the trusted parties can still come together to sign a transaction. This shifts the key protection concept from relying on a single trusted third party to secure your key. This eliminates typical single point of failures and tedious setup and recovery schemes. ### Understanding the Risks of Private Keys **Private Keys** form a significant vulnerability. Cybercriminals and internal threats often target private keys to gain access to wallets that control blockchain-stored funds. Common methods of compromising private keys include: * Malware infections on servers to steal private keys. * Unauthorized use of a Hardware Security Module (HSM) authentication token to authorize fraudulent transactions. * Theft of private keys by authorized internal employees. ### Usability Challenges in Traditional Self-Custodial Wallets **The Risk of Loss**: A fundamental issue with mnemonics is the risk of losing access to funds. Users unfamiliar with the concept of self-custody often expect wallet providers to reset their passwords, similar to traditional financial services. This misconception can lead to a complete loss of assets if the mnemonic is forgotten or misplaced, as there is no way to recover the keys without it. **The Challenge for Mass Adoption**: While traditional self-custody may be suitable for sophisticated users with a deep understanding of cryptocurrencies and blockchain, the complexity and risk associated with mnemonic management discourage many potential users, slowing down the integration of these technologies for widespread adoption. ## Our MPC Solution offers: **Full Control** with usability and security that matches that of exchanges, including: * Multi-blockchain support * Enhanced security, performance, and flexibility * Multiple backup and restore options * Multi-Factor authentication * Lower fees than Multisig transactions. * Recover your private key at any time. OPZ is committed to making self-custodial wallets more accessible without compromising the security that is fundamental to its purpose. --- # 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://whitepaper.opz.io/keyfusion/introduction-to-keyfusion.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.