# Data Beyond Monetary Transactions

<figure><img src="/files/ZOE4EwqcZo4ubmrDvAPb" alt=""><figcaption></figcaption></figure>

The BSV Ledger is **not limited to monetary transactions**; it also accommodates a data component that can be included in each transaction. For instance, a simple transaction where Bob pays Alice 3 bitcoins might require only **1 kilobyte (KB)** of data in the ledger. However, the BSV Ledger's flexibility allows for more complex transactions as well.

Consider the following examples:

* A transaction where **Bob pays Alice** 0.00001 BSV might utilize **1.1 KB** of data.
* A transaction involving a thousand recipients could require approximately **3 KB** of data.

The critical takeaway is that there is **no fixed limit to the amount of data a transaction can include**; the only constraint is the **economic feasibility determined by the nodes** processing the transaction. This flexibility transforms the BSV Ledger into a global data repository, enabling a **WORM (Write Once, Read Many)** database where **any amount of data can be recorded** at any time.


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-basics-protocol-and-design/the-bsv-ledger-bitcoin-protocol-and-design/data-beyond-monetary-transactions.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.