# Introduction

Stonest is a decentralized storage protocol that provides permanent, encrypted, and censorship-resistant data storage powered by a global network of independent node operators. The native token incentivizes network participation and enables a permissionless storage marketplace.

#### The Vision

In a world where data is the most valuable resource, control over data storage means control over information itself. Centralized cloud providers — Amazon Web Services, Google Cloud, Microsoft Azure — hold custody of the world's data, creating single points of failure, censorship vectors, and privacy risks.

Stonest reimagines storage from the ground up. By distributing encrypted data across thousands of independent nodes worldwide, Stonest eliminates single points of failure and returns data sovereignty to its owners.

#### Mission

To build the permanent storage layer for the decentralized web — a bedrock of encrypted, distributed, and economically incentivized data infrastructure that outlasts any single entity.

#### Key Principles

* **Permanence**: Data persists as long as the network lives. No deletions, no expiry.
* **Privacy**: Zero-knowledge encryption ensures nobody — not even node operators — can read your data.
* **Decentralization**: No single entity controls the network. Storage is distributed across 12,400+ nodes in 140+ countries.
* **Economic Alignment**: Node operators earn rewards for reliably storing data, creating a self-sustaining incentive layer.


---

# 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://stonest.gitbook.io/stonest-docs/introduction.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.