# Economic Model and Types of Overlays

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

While the transaction fees associated with on-chain data storage may appear minimal, the reality is that **hosting costs for serving content are still present and must be accounted for**.

Overlay services address this challenge by **enabling users to contract storage providers**, allowing for the payment of hosting data for a specified duration. The **blockchain records a token** that captures the **contract details**, including the **duration for which the data will be available at that host**.

This model represents a significant shift in how data storage is priced. Instead of incurring a monthly fee to a cloud provider, users can purchase storage on a **per-file basis**, offering unprecedented granularity and flexibility. Data storage overlays provide a mechanism for managing content distribution, enhancing existing solutions with hash-based lookup and immutable timestamps.

#### Types of Overlays:

* **Private Overlays**: Designed for specific individuals or businesses seeking complete control over their data and transaction processing.
* **Public Overlays**: Accessible to developers lacking infrastructure, such as ARC, which handles any valid transaction.
* **Ring-Fenced Overlays**: Tailored for financial institutions with jurisdictional restrictions, ensuring compliance while leveraging blockchain benefits.
* **Open Protocol Overlays**: Intended for experimental applications by entrepreneurial developers exploring new use cases.


---

# 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-network-topology/essentials-of-overlay-services/economic-model-and-types-of-overlays.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.