# CONET Consensus Protocol

### **CoNET Consensus Protocol**

CoNET employs a **hybrid consensus mechanism** that evolves over its development stages, combining **Proof of Work (PoW), Proof of Staking (PoS), and Proof of upTime (PoT)** to ensure **scalability, security, and decentralization**.

***

### **Initiation Stage: Proof-of-Time (PoT) Consensus**

In its early phase, CoNET focuses on ensuring **network participation and reliability** through **Proof of upTime (PoT)**.<br>

&#x20;**How It Works:**

* Participants register as **relay nodes** and connect to the CoNET network, proving their devices remain online.
* Every **10 seconds**, the network calculates the total number of online nodes, allocating rewards based on uptime weight.
* Relay nodes require devices with **unique wallet addresses** (no duplicate nodes per device).

&#x20;**Purpose:**

* Encourages widespread participation to strengthen the network.
* Ensures active and stable nodes to build a **robust decentralized infrastructure**.

***

### **Development Period: Hybrid Model (PoT + PoW)**

As CoNET grows, **Proof of Work (PoW)** is introduced alongside PoT to **incentivize computational contributions** and expand network capabilities.<br>

**How It Works:**

* **Relay Nodes (PoT):** Continue earning rewards based on uptime.
* **SaaS Nodes (PoW):** Users register nodes that provide computational power, bandwidth, and storage.
* Multiple SaaS nodes can **operate on the same wallet**, allowing flexibility in contribution.
* Miners earn rewards not only from the CoNET pool but also from **real usage** by dApps and network participants.

**Purpose:**

* Encourages computational power sharing for **decentralized applications (dApps)**.
* Bridges the transition from uptime-based participation to **resource-sharing incentives**.

***

### **Stability Period: PoS, PoT & PoW Integration**

In the mature stage, CoNET operates on a fully integrated **PoS + PoT + PoW** model, ensuring **sustainability, efficiency, and decentralized governance**.<br>

&#x20;**How It Works:**

* **Proof of Staking (PoS):** Users stake **$CONET or $ETH** to operate **Validator, Full, or Partial Nodes**, ensuring **economic security & long-term commitment**.
* **Proof of upTime (PoT):** Nodes that maintain high uptime **earn additional incentives**, rewarding stability and participation.
* **Proof of Work (PoW):** Beyond transaction validation, PoW ensures:
  * Nodes stay **online and connected** to maintain network resilience.
  * **Verification of social tasks** and decentralized applications.
  * **Computational power for dApps**, supporting a **privacy-first, decentralized infrastructure**.

&#x20;**Market-Driven Rewards:**

* As CoNET matures, rewards prioritize **real network usage** over our pool allocations.
* A **fair-trade model** is established, where miners bid for their services and users select the most cost-effective providers.

***

### **Why CoNET’s Hybrid Model is Unique**

&#x20;**Combines economic incentives (PoS), participation rewards (PoT), and computational contribution (PoW).**\
&#x20;**Optimized for a decentralized internet, powered by Layer Minus Protocol—eliminating IP tracking and enhancing privacy.**\
&#x20;**Enables fair, scalable, and self-sustaining rewards for long-term growth.**

CoNET’s consensus model is designed to evolve, ensuring **network security, efficiency, and user-driven governance** as adoption scales globally.&#x20;


---

# 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://doceng.conet.network/tokenomics/conet-consensus-protocol.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.
