> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/depin/integrate-your-module/data-availability-infras.md).
# Data Availability Modules
The Data Availability Layer (DAL) is the input layer for W3bstream. It can be either a centralized service or a decentralized network that stores blocks of data for a specified period as determined by a DePIN project. Once this period expires, the data may be immediately deleted or transferred to a dedicated Long-Term Storage Layer. Depending on the project's configuration, the DAL also periodically commits data sets (e.g., a hash) to the IoTeX Blockchain to ensure data integrity.
## Supported DA Infra
While IoTeX does not provide any Data Availability DIM, W3bstream will support popular Data Availability (DA) infrastructures. We anticipate that third-party projects will develop DIMs to serve as DA layers, integrating seamlessly with W3bstream.
{% hint style="info" %}
**Reference Implementation**
A W3bstream-compatible DA Layer should implement a [simple interface](https://github.com/machinefi/sprout/blob/develop/datasource/datasource.go).
W3bstream provides a [reference implementation](https://github.com/machinefi/sprout/tree/develop/datasource) for a Postgres DB.
{% endhint %}
---
# 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.iotex.io/depin/integrate-your-module/data-availability-infras.md?ask=&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.
