> 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/iotex-depin-modules/w3bstream/overview-of-w3bstream.md).

# Overview of W3bstream

In a [modular DePIN infrastructure](/depin/dims-overview.md), W3bstream is an implementation of the off-chain computing layer featuring multi-prover technology. As a decentralized heterogeneous prover pool, W3bstream can perform project-specific business logic on the data stored in the Data Availability (DA) layer and generate **validity proofs** (e.g., zero-knowledge proofs, attestation reports, etc.) of the computations executed. W3bstream works as a stateless computing component in a modular DePIN infrastructure and follows the high-level workflow as illustrated below:

<figure><img src="https://content.gitbook.com/content/ZuVxK3TulcVIDbzRzV16/blobs/F2cIVWp57xa7PpVQH6kM/image.png" alt=""><figcaption><p>Workflow of an Off-Chain computing Layer of the Modular DePIN Infrastructure </p></figcaption></figure>

1. A coordinator node in the off-chain computing layer retrieves data from the data availability layer based on the configuration of a DePIN project;
2. The coordinator node feeds data to an idle prover node or a selected set of idle prover nodes in the off-chain computing layer;
3. The prover node(s) performs computation specified by the DePIN project and generates the computation result and corresponding validity proof;
4. The computation result and validity proof are returned to the coordinator node;
5. The coordinator node sends the computation result and validity proof to a smart contract for further processing.


---

# 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/iotex-depin-modules/w3bstream/overview-of-w3bstream.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.