# 2PC-MPC Technology

### **Empowering Nativerse with 2PC-MPC Technology**

\
Nativerse utilizes Ika.xyz’s cutting-edge 2PC-MPC (Two-Party Computation Multi-Party Computation) technology to enhance our Zero Trust architecture. This protocol enables Nativerse to uphold the Zero Trust principle across blockchain interactions, ensuring that all transactions are secure, decentralized, and verifiable.

### **Understanding 2PC-MPC**

<figure><img src="/files/ONFebPjyDlBj2CLuonpW" alt=""><figcaption></figcaption></figure>

\
2PC-MPC protocol is a breakthrough cryptographic method, allowing both the user and the network to jointly generate cryptographic signatures. This workflow enforces collaborative security, where each action within Nativerse requires both user input and network validation, achieving a truly non-custodial system. The process involves **thousands of decentralized nodes**, further reducing the risk of collusion or single points of failure.

#### **How It Works in Practice**

1. **User and Network Collaboration**: For any transaction, both the user and Nativerse (via Ika's decentralized node network) participate to generate a valid cryptographic signature like [ECDSA](https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm). This requires continuous verification, eliminating the need for trust in any one participant. And Castle and Moat systems.
2. **Decentralized Verification Across Nodes**: 2PC-MPC network of nodes independently verifies user signature request, thus creating a multi-layered security system that no single entity can control or manipulate. This decentralized model is essential for secure, Zero Trust operations.

### Examples in Action

In Nativerse, we create a unique 2PC-MPC wallet for each user, enabling them to perform secure transactions, such as staking with creating a special UTXO called [EOTS](https://docs.babylonchain.io/docs/introduction/btc-staking), directly from their personal Segwit BTC wallet. Using 2PC-MPC technology, this wallet maintains Zero Trust principles by requiring cryptographic signature participation from both the user and the 2PC-MPC network for every transaction, eliminating reliance on centralized custodians and traditional, trust-dependent bridge mechanisms.

#### **Instant Unstake Process**

\
When a user wants to perform an instant unstake, they initiate a simple transfer of their 2PC-MPC wallet's secret key share to Nativerse. With this key transfer, Nativerse takes over the responsibility of waiting and managing the remaining unstake process (unbounding and withdrawal finalization periods) on behalf of the user. Immediately upon key transfer, the user doesn’t need to wait for the unstake period to complete. Instead, they receive their BTC directly from Nativerse’s Satoshi Reserve Pool, ensuring fast access to their funds without compromising the integrity or security of the staking process.

This userflow provides a seamless user experience for staking and instant unstaking, all while maintaining the highest levels of decentralized security through our Zero Trust architecture. The process highlights Nativerse's commitment to delivering a secure, efficient, and user-friendly platform powered by decentralized, trustless technology.

### **Building a Secure and Simple Staking Proccess**

\
Using  2PC-MPC technology, Nativerse provides a resilient, secure environment for Bitcoin staking. This technology supports decentralized custody, easily DeFi integrations, and non-custodial wallet functions, ensuring that interactions are safe and verifiable by every step. By embracing Ika’s advancements, Nativerse is at the forefront of a Zero Trust Web3, ensuring robust security without centralized compromise.


---

# Agent Instructions: 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:

```
GET https://nativerse.gitbook.io/docs/security/markdown.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.