> For the complete documentation index, see [llms.txt](https://docs.zkpass.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zkpass.org/overview/use-cases/depin-and-machine-economy.md).

# DePIN and Machine Economy

Decentralized Physical Infrastructure Networks (DePIN) rely on devices and machines to generate data that is used for payments, reputation, and coordination. Without trustworthy verification, these systems are exposed to falsified reports, double-counting, and manipulation.

zkPass enables device-generated data to be cryptographically verifiable. By embedding zkTLS at the device gateway or cloud API, machine interactions can produce zero-knowledge proofs of usage, availability, or performance.

**Limitations of current DePIN systems**

* Dependence on centralized APIs or unverifiable self-reports from devices.
* Fraud in usage metrics such as fake bandwidth, storage, or energy contributions.
* Difficulty in establishing reliable machine-to-machine settlements.

**zkPass approach**

* TLS-based attestation of device data, transformed into zero-knowledge proofs.
* Local proof generation at edge gateways or device APIs, preventing manipulation.
* Interoperable proofs consumable by blockchains, DAOs, and marketplaces.

**Applications**

* Verifiable proofs of energy consumption and delivery in decentralized power grids.
* Authentic bandwidth or storage usage proofs in decentralized cloud networks.
* Verified EV charging sessions, enabling fair rewards in charging infrastructure networks.
* IoT-enabled supply chain sensors providing cryptographic proofs of environmental conditions.

**Strategic impact**\
By anchoring machine data in verifiable cryptographic proofs, zkPass acts as the trust layer for the machine economy. This ensures that incentives, settlements, and governance in DePIN systems are based on authentic inputs rather than unverifiable claims.


---

# 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.zkpass.org/overview/use-cases/depin-and-machine-economy.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.