> 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/off-chain-data-on-chain-proof/off-chain-data-xyo-layer-one.md).

# Off-Chain Data XYO Layer One

XYOL1 provides multiple mechanisms that enable off-chain data handling while maintaining on-chain trust through cryptographic proofs.

### Layer One Features

#### [Bound Witnesses](https://docs.xyo.network/xyo-layer-one/xyo-layer-one-features/bound-witness.md)

Bound Witnesses allow two devices to mutually sign and record an interaction without sending the full event to the blockchain. The interaction is proven by shared, signed cryptographic evidence—**not by broadcasting full data**.

#### [Bearer Proofs](https://docs.xyo.network/xyo-layer-one/xyo-layer-one-features/bearer-proof.md)

Bearer Proofs are small, cryptographically secure references that prove a piece of data belongs to a known set—**without revealing or transmitting the full set**. This allows users to verify claims without sharing underlying records.

#### [Framing Cursors](https://docs.xyo.network/xyo-layer-one/xyo-layer-one-features/framing-cursor.md)

Framing Cursors enable efficient access to off-chain data by marking *where* to look within a larger structure. They let you provide minimal proof of inclusion across specific frames of the blockchain—again, **without full-chain scanning**.

#### [Bound Witness Trees](#dbound-witness-trees)

Instead of validating transactions one by one, Bound Witness Trees let XYO aggregate many events into a single hash. This hash is stored on-chain. If validation is needed later, the full tree can be reconstructed and proven off-chain—**only the hash lives on-chain**.

### Real-World Example

A supply chain logs a sensor reading for perishable goods (e.g., vaccine temperature). The full sensor data is too large and sensitive to store publicly.

#### **With XYO**

* The sensor logs the reading off-chain.
* A Bound Witness is generated to prove the reading occurred and was valid.
* A hash of that reading is recorded on-chain via a Bearer Proof or within a Bound Witness Tree.
* At any point, a verifier can validate the reading’s authenticity by comparing it against the on-chain proof—without ever seeing or revealing the full data.


---

# 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/off-chain-data-on-chain-proof/off-chain-data-xyo-layer-one.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.
