MPC Cryptographic Protocols: What They Are, Why They Matter, and How They Work

November 18, 2026 · 10 min read
MPC Cryptographic Protocols: What They Are and How They Work

In finance, situations often arise where multiple parties need to work together toward a common goal, yet none is willing to disclose confidential information or relinquish control over their assets. For years, finding a balance between security and collaboration was a challenge. MPC cryptographic protocols offer an approach that eliminates the need for such a compromise. 

What Is Multi-Party Computation (MPC)?

Multi-Party Computation (MPC) refers to a family of cryptographic protocols that allow multiple parties to process data jointly without disclosing it to one another or sharing it with a single trusted intermediary. This definition is outlined in the documentation published by the U.S. National Institute of Standards and Technology (NIST).

MPC relies on cryptographic techniques that provide mathematical guarantees of confidentiality during computation. Depending on the protocol, these may include secret sharing, encryption, cryptographic proofs of correctness, and other methods. Together, these techniques enable parties to exchange the information needed for joint computations without exposing confidential data.

One of the most significant applications of this approach in finance is threshold cryptography, which allows multiple parties to perform cryptographic operations jointly without reconstructing the complete private key.

History of MPC

The theoretical foundations of MPC began taking shape in the late 1970s, as advances in computing presented cryptographers with a new challenge: enabling multiple parties to process confidential information jointly without disclosing it to one another or relying on a trusted intermediary. Over the following decades, the technology evolved from a mathematical concept into a practical tool for protecting sensitive information.

Key milestones in the development of Multi-Party Computation include:

  • 1979. Israeli cryptographer Adi Shamir introduced Shamir’s Secret Sharing, a scheme that allows confidential information to be divided among multiple participants. It became one of the foundational building blocks of secure multi-party computation.
  • 1982. American computer scientist Andrew Yao formulated the famous Millionaires’ Problem: how 2 people could determine which of them was wealthier without revealing their respective fortunes. His proposed solution laid the groundwork for the theory of secure two-party computation.
  • 1986. Yao further developed his approach, while researchers Oded Goldreich, Silvio Micali, and Avi Wigderson extended the concept to an arbitrary number of participants.
  • 1988. Michael Ben-Or, Shafi Goldwasser, and Avi Wigderson published research on secure multi-party computation protocols capable of withstanding malicious participants. Independently, David Chaum, Claude Crépeau, and Ivan Damgård developed protocols with mathematically proven confidentiality guarantees that didn’t depend on assumptions about the computational difficulty of breaking the underlying cryptography.
  • 2008. Denmark saw one of the first large-scale practical applications of MPC. The technology was used in an auction for sugar beet production contracts. The system was developed by a research team that included Ivan Damgård and Peter Bogetoft.
  • 2012. Ivan Damgård, Valerio Pastro, Nigel Smart, and Sarah Zakarias introduced a protocol that later became widely known as SPDZ. It marked an important step toward improving the efficiency of secure computations, including in environments with malicious participants.
  • 2020. Chelsea Komlo and Ian Goldberg introduced the FROST protocol, which allows multiple participants to jointly generate a single Schnorr signature without combining their private key shares, while reducing the number of communication rounds required.

Today, threshold cryptography remains a significant area of MPC application, particularly in protecting digital assets. FROST-based solutions are used in the development of cryptocurrency custody infrastructure. An important milestone came in 2024 with the publication of RFC 9591, a specification detailing how FROST works and the requirements for its secure implementation.

Research in this field continues. In 2026, researchers introduced FaFROST, an experimental protocol designed to improve the security of threshold signatures and identify participants who deliberately disrupt the signing process. Another study published that year demonstrated that data transmission requirements could be substantially reduced when jointly generating multiple digital signatures under certain system configurations. 

How Secure Multi-Party Computation Works

Consider several companies that need to calculate their combined revenue without disclosing their individual financial figures to one another. The participants agree in advance on which data to use and who will receive the final result. MPC allows them to perform the calculation without sharing their underlying financial records.

However, even the final result can reveal confidential information. For example, if only 2 companies participate in the calculation, each can determine the other’s revenue by subtracting its own figure from the total. That’s why designing an MPC-based system involves considering the algorithm, permitted queries, number of participants, and who can access the results.

One common technique used in MPC is secret sharing. The original value is divided into mathematically related shares distributed among different computing nodes. As explained in a report by NIST, the protected information can’t be reconstructed unless the required threshold of shares is reached. The nodes perform computations on their respective shares and exchange messages according to the protocol, revealing only the agreed-upon result. 

Why MPC Is Used in Cryptocurrency Wallets

Cryptocurrency transfers typically require a digital signature, which is generated using a private key in traditional systems. An attacker who obtains this key can sign transactions on the owner’s behalf. The principles behind digital signatures in cryptocurrency transactions are explained in detail in the Bitcoin Developer Guide.

MPC wallets typically use threshold cryptography to sign transactions, requiring a predefined number of participants to generate a signature. The operation of an MPC wallet with distributed key generation can be broken down into 3 steps:

  1. The nodes jointly generate private key shares and the corresponding public key. No single participant has access to the complete private key during this process.
  2. When a transfer is requested, the required number of nodes participate in the signing process. For example, a 2-of-3 threshold allows any 2 of the 3 key-share holders to authorize a transaction.
  3. The nodes jointly generate the signature without reconstructing the complete private key.

This mechanism should be distinguished from simply splitting a key into shares for backup purposes. In the latter case, the shares are combined to reconstruct the secret before it can be used. Threshold signing doesn’t require this step. However, not all implementations support distributed key generation. Some systems initially rely on a trusted party to generate the key.

Threshold signatures also differ from traditional Bitcoin multisignature schemes, where participants use separate keys and the network verifies the required number of individual signatures. In an MPC-based threshold scheme, key-share holders interact off-chain, and the resulting signature is verified as a standard digital signature produced with a single key.

Applications of MPC in Finance

When managing corporate cryptocurrency reserves, threshold schemes allow control to be distributed among multiple authorized parties. However, the number of employees approving a transaction doesn’t necessarily match the number of nodes holding key shares, as internal approval procedures and cryptographic mechanisms operate at different levels.

One example of this infrastructure is Google Cloud Multi-party Compute. According to the official documentation, the service combines threshold signature generation with user access controls and transaction policies. A separate Google Cloud guide covers the use of this technology for institutional Bitcoin custody.

As of November 2026, Google Cloud Multi-party Compute is available in preview, with general availability planned for early 2027.

In banking analytics, MPC helps identify connections between transactions that individual banks can’t detect on their own. One example is the Multi Party Computation for Anti Money Laundering (MPC4AML) project, in which Dutch research organization TNO, together with ABN AMRO and Rabobank, explored how banks could jointly analyze data to combat money laundering without disclosing confidential information. The technology enabled banks to identify connections between customers at different institutions with varying risk scores without revealing those scores to other participants. Initial positive results came from an experiment using synthetic data that simulated real banking transactions. 

Other Applications of MPC

Secure computation is also relevant in areas beyond banking:

  • Healthcare. Medical institutions can jointly analyze treatment outcomes without sharing individual patient records. In a study published in 2024, institutions in Munich and Rome used MPC to analyze data from 48 cancer patients and generate aggregate statistics.
  • Auctions. MPC enables sealed-bid auctions in which the winner can be determined without revealing other participants’ bids. In 2013, researchers introduced an experimental online auction system that used cryptographic protocols to keep losing bids confidential, even from the auction organizer.
  • Machine Learning. SecureML, a research system introduced in 2017, enabled 2 servers to jointly train models, including neural networks, using protected data shares. Data owners could contribute information for training without exposing the original records to either server. 

What Determines MPC Reliability?

The reliability of MPC in practice depends on both the cryptographic algorithms and how they’re implemented. Several key factors should be considered when evaluating these solutions:

  1. Threat Model. Every MPC protocol has a threat model that defines how many participants an attacker can compromise and what types of malicious behavior the protocol is designed to withstand. Some schemes assume participants follow the protocol but attempt to obtain additional information. Others also provide protection against deliberate violations of the rules. Therefore, the MPC designation alone doesn’t indicate the security level of a particular product.
  2. Infrastructure Independence. If all key shares can be accessed through a single administrator account, distributing them across multiple servers provides significantly less protection than the cryptographic scheme is designed to offer. It’s therefore important to consider both the physical separation of computing nodes and how access to them is managed.
  3. Performance. Additional computations and message exchanges require time and resources. Processing speed depends on the protocol, the nature of the task, and the quality of communication between participants. These limitations are particularly important in financial systems, where transaction processing delays can have significant consequences.
  4. Transaction Validation. A threshold signature verifies a transaction’s cryptographic authenticity but doesn’t establish its economic legitimacy. If participants sign a transfer containing substituted payment details, a mathematically valid signature won’t prevent the loss of funds. Verifying recipients, transaction limits, and payment authorization remains the responsibility of the application and authorized personnel.
  5. Operational Continuity. Protecting a key from compromise and maintaining uninterrupted operations are separate requirements. Losing too many key shares can make signing impossible. Before implementing MPC, organizations must establish procedures for backups, access recovery, and handling a service provider’s termination of operations. For financial institutions, these procedures are just as important as the cryptographic security of the protocol itself.

MPC doesn’t eliminate every risk associated with processing confidential data and managing digital assets, but it fundamentally changes how those risks can be addressed. The technology enables critical control functions to be distributed securely instead of being concentrated in the hands of a single party. This is particularly valuable in digital asset management, where the compromise of a single private key can result in an irreversible loss of funds.

Table of Contents: