> 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-sequencer-infras.md).
# Data Sequencer Modules
A DePIN Sequencer can function either as a centralized service or as a decentralized network. Its primary role is to **sort data packets from smart devices** and pack them in a Data Availability Network in a format that can be processed by the off-chain computing layer (W3bstream).
A DePIN sequencer is usually responsible for device authentication, data message validation, sorting, filtering, and other tasks depending on project requirements.
While researchers have not yet reached a consensus on the architecture and functions of a DePIN Sequencer, the need for high customizability and programmability is evident. Many emerging decentralized Sequencer networks focus on Ethereum scalability but lack the programmability required by DePIN projects.
## Supported Sequencers
While IoTeX does not provide any Data Sequencer DIM, W3bstream will support popular Data Availability (DA) infrastructures. We anticipate that third-party projects will develop DIMs to serve as DePIN Sequencers, integrating seamlessly with W3bstream.
{% hint style="info" %}
**Reference Implementation**
A W3bstream-compatible DA Layer should aggregate one ore multiple device messages into a [W3bstream Task](/depin/iotex-depin-modules/w3bstream/build-with-w3bstream/get-started/w3bstream-tasks.md) and store these tasks on a supported DA infra.
W3bstream provides a [reference implementation](https://github.com/machinefi/sprout/tree/develop/cmd/sequencer) for a DePIN Sequencer for W3bstream that features:
* message aggregation
* ioID authentication
* DID-based secure device communication
* Postgres as the destination DA infra.
{% 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-sequencer-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.
