> For the complete documentation index, see [llms.txt](https://dashpay.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dashpay.gitbook.io/docs/dashpay-documentation/what-powers-dashpay.md). # What Powers DashPay DashPay is built from the ground up to support **private, offline-capable, and machine-native payments**. Its architecture combines cryptographic verification, ephemeral communication, and asynchronous settlement to create a system that works at the edge — without depending on persistent internet access or on-chain immediacy. Below are the foundational components that make this possible: *** #### **1. Zero-Knowledge Ephemeral Proofs** At the heart of DashPay is a mechanism for generating single-use, non-traceable proofs of payment. These proofs confirm that a user has the right balance or authority — without revealing their wallet address, identity, or transaction history. This allows for **private, verifiable transfers** without account linking or on-chain exposure. *** #### **2. ZK-NFC Tap Wallets** DashPay wallets are mobile-first and hardware-friendly, enabling **tap-to-pay** functionality using NFC and zero-knowledge logic. Transactions can be executed between two nearby devices, with no internet and no public broadcast — ideal for retail, field, or peer-to-peer environments. *** #### **3. The x402 Payment Layer** DashPay uses a modified HTTP 402 standard — once reserved but never implemented — to power a machine-native payment flow. Any agent or app can trigger a payment request via HTTP. Once the user responds with a cryptographic proof or stablecoin transaction, the system grants access, verifies intent, and logs the interaction. Finality is handled asynchronously when connectivity returns. *** #### **4. Local AI Risk Engine** Every DashPay-compatible device runs a local intelligence layer that analyzes transaction patterns in real time. This system flags anomalies, prevents known attack patterns (like replay or double-spend attempts), and adapts to emerging risks — all **without cloud processing** or server logs. *** #### **5. Offline-First Architecture** The entire stack is designed to operate in disconnected environments. From vending machines to smartphones in rural zones, DashPay can log transactions, store encrypted queues, and **synchronize later without trust**. On-chain finality happens when either party reconnects — and reconciliation is cryptographically guaranteed. *** DashPay isn’t just software — it’s a system of components that work together to move value **when, where, and how it’s actually needed**. Whether you're a user, developer, merchant, or machine, DashPay ensures that trust and privacy don't depend on network availability — only on math. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dashpay.gitbook.io/docs/dashpay-documentation/what-powers-dashpay.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.