> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/getting-started/qubetics-dvpn/why-provider-and-node-registration-deposits-go-to-the-community-pool.md).

# Why Provider and Node Registration Deposits Go to the Community Pool

To ensure the **security, sustainability, and reliability** of the Qubetics network, both **Provider registration** and **Node registration** require a one-time token allocation that is transferred to the **Community Pool**.

These allocations are **not staking deposits** and **do not earn staking rewards**. Instead, they serve as an **economic commitment mechanism** and a **long-term sustainability fund** for the network.

### Purpose of Registration Allocations

#### 1. Sybil & Spam Resistance

If registration were free or had no economic cost:

* Malicious actors could register large numbers of Providers or Nodes
* Attackers could:
  * Flood the network with low-quality or fake nodes
  * Manipulate discovery, routing, or subscription flows
  * Increase operational overhead for the protocol

Requiring a **non-refundable allocation** creates a **real economic cost**, discouraging abuse and ensuring that only serious participants register.

#### 2. Economic Commitment From Operators

Running a Provider or Node is a **long-term responsibility**:

* Providers manage subscription plans and user allocations
* Node operators are expected to maintain up-time and service quality

The allocation acts as a **commitment signal**, aligning operators with the health and reputation of the network.

#### 3. Network Sustainability & Protocol Funding

Funds transferred to the **Community Pool** are used to support the long-term operation of the Qubetics network, including:

* Protocol development and maintenance
* dVPN infrastructure improvements
* Security audits and upgrades
* Ecosystem tooling (dashboards, monitoring, SDKs)
* Community governance initiatives

This creates a **self-sustaining economic loop** where network usage directly funds network growth.

### Why the Allocation Is Not Staked

* Registration allocations are **not intended to be yield-generating**
* Earnings for Providers and Node Operators come from:
  * Subscription revenue
  * Node uptime and service delivery
* This separation ensures:
  * No “pay-to-earn” or passive reward abuse
  * Rewards are tied strictly to **real network utility**

### Why the Allocation Is Transferred (Not Locked)

Unlike a refundable bond, the allocation is transferred to the Community Pool to:

* Prevent short-term or speculative registrations
* Eliminate churn from actors registering and exiting repeatedly
* Provide predictable funding for protocol operations

This design prioritizes **network quality over raw participation numbers**


---

# 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://qubetics.gitbook.io/qubetics-docs/getting-started/qubetics-dvpn/why-provider-and-node-registration-deposits-go-to-the-community-pool.md?ask=<question>&goal=<endgoal>
```

`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.