# Nativerse Staking Standard Program

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

## Step by step userflow:

**1. User Initiates Staking:**

* A user interacts with their **dWallet** (a decentralized wallet) to start the staking process.

**2. 2PC-MPC Protocol Execution:**

* The staking process is secured using a **Two-Party Computation Multi-Party Computation (2PC-MPC)** protocol.
* The two parties involved are:
  * **User's dWallet.**
  * **IKA Network Nodes** (decentralized nodes ensuring protocol security).

**3. Locking BTC:**

* The user's **BTC** is locked using an **EOTS-Timelock function**.
* This function ensures that the funds are securely locked for the staking duration.

**4. Broadcast to Bitcoin Network:**

* The staking transaction is broadcasted to the **Bitcoin Network**, confirming that the BTC is staked.

**5. Validation by Babylon:**

* The **Babylon** service monitors the Bitcoin Network and confirms that the BTC has been successfully locked for staking.

**6. Minting Liquid Staking Tokens (LSTs):**

* The proof is used to mint **Liquid Staking Tokens (LSTs)** on supported networks, which include:
  * **EVM (Ethereum Virtual Machine)** networks.
  * **Bitcoin Layer 2 solutions**.
  * **MoveVM** (a blockchain framework).

**7. Standard LST Token Properties:**

* The minted tokens adhere to the **NATIVERSE Token Standard**, offering:
  * **1:1 pegging** to the staked BTC.
  * **Rewards-based**&#x20;
  * **Yield-bearing**&#x20;

**8. Token Usage:**

* These minted LSTs can now be used across various DeFi applications and networks while the user's BTC remains securely staked.


---

# 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/architecture/nativerse-staking-standard-program.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.