> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/about-xyo/core-paradigms-of-xyo.md).

# Core Paradigms of XYO

XYO is built around a set of guiding paradigms that make its tech distinct:

* **Off-Chain Data, On-Chain Proof**: Securely hash and verify data without exposing the content.
* **Data Rollups for Scale**: Group transactions or data inputs to reduce cost and increase speed.
* **Decentralized Witnessing**: Devices observe and confirm multiple data points, rolled up for efficient verification.
* **Sovereign Participation**: Individuals and organizations maintain control over the data they produce and validate.
* **Decentralization Through Efficiency:** By shrinking node requirements XYO allows more people—not just corporations—to run nodes.

These concepts make it possible to create specific XYO solutions such as:

* **Proof of Location:** Prevent spoofed and fraudulent location data.
* **Proof of Origin:** Prevent or detect fraud through data origin and production affirmation.
* **Chain of Chains:** Merge individual Proof of Origin chains into a shared, decentralized global state.
* **Ground-Truth Validation:** Cryptographically validate user actions in the physical world.

as well as allowing industries to:

* **Track and monetize** real-world data
* Create **scalable Web3 apps** with fast, low-cost transactions
* Operate transparently and efficiently **at global scale**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xyo.network/about-xyo/core-paradigms-of-xyo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
