> 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/w3bstream-depin-verification.md). # The DePIN Verification Problem Decentralized Physical Infrastructure Networks (DePIN) face unique challenges in verifying and processing physical device data while ensuring trust. On-device verification methods, such as using trusted execution environments in conjunction with blockchain-based identity management, can help solve data provenance verification. However, trusted processing of data is often overlooked by DePIN builders due to the lack of dedicated off-chain verifiable compute protocols suitable for DePINs. > *As a result, the core logic of DePIN projects, specifically the logic that triggers on-chain token economies, is not verifiable by anyone and thus not trusted.* ## **W3bstream: Off-Chain Verification for DePIN** W3bstream is an off-chain verifiable compute protocol designed by IoTeX to address the verification challenges in DePIN. Based on multi-prover technology, W3bstream ensures flexible and scalable verification of off-chain computations, mitigating risks like self-dealing, lazy providers, and malicious responses. Combined with [ioID, IoTeX's unique identity system for DePINs](broken://pages/GCnah9r4BHZ9ZuGRPMx0), W3bstream forms a robust infrastructure that ensures trust and integrity within DePIN ecosystems, enabling trusted and secure management of decentralized physical infrastructures. {% hint style="info" %} **Further readings** [→ Read more about the DePIN Verification Problem in this blog](https://a16zcrypto.com/posts/article/introducing-the-nakamoto-challenge-addressing-the-toughest-problems-in-crypto/#section--2) [→ Pebble Tracker, a Web3-ready devices using TEEs](broken://pages/bmz3ZGNGzqkJ91LEod2k) [→ ioID Identity management with for DePIN projects, Devices, an users ](/depin/builders/reference-docs/ioctl-client/ioid-identities.md) {% 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/iotex-depin-modules/w3bstream/w3bstream-depin-verification.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.