> 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/network-and-ecosystem/dashpay-network-overview.md).

# DashPay Network Overview

DashPay is not a single app or chain — it’s a modular **payment network** designed for ecosystems where participants include not just users, but also **devices, agents, APIs, merchants, and relayers**. The network operates through a mix of local computation, ephemeral proof exchange, and asynchronous blockchain settlement via the x402 standard.

This allows DashPay to support **trust-minimized payments** even in places or systems where traditional rails cannot reach.

***

#### **Key Participants**

**🧑‍💻 Users**

Individuals using DashPay wallets for private, peer-to-peer payments, tap-to-pay retail, or offline transfers. Users control their own keys, generate ZK proofs, and finalize transactions without exposing identity.

**🤖 Agents & Bots**

Autonomous scripts or AI agents that initiate or receive payments — for example, paying for API usage, compute time, or data access. DashPay supports request/response payments through HTTP x402 without needing wallet UIs.

**🏪 Merchants & Devices**

Shops, vending systems, terminals, or IoT endpoints that accept DashPay offline via ZK-NFC or QR. Payments are validated locally and queued for on-chain finality once connected.

**🌐 DashNodes**

Optional relayer nodes or light clients that sync offline payment proofs to the blockchain. They help bridge delayed transactions and enable cross-party reconciliation.

**🧠 Local Verifiers**

Each device in the network runs a local verifier and risk filter. These systems detect fraud, validate proof structure, and enforce rate limits — all without cloud dependency.

***

#### **Value Flow Overview**

1. **Request Initiated**

* A user, app, or agent sends a request for value — via NFC, QR, API, or HTTP x402.

2. **Payment Proof Exchanged**

* The payer responds with a ZK proof or signed token that proves balance or permission.

3. **Local Confirmation**

* The recipient device verifies the proof locally, accepts payment, and stores it as pending.

4. **On-Chain Reconciliation**

* When either party reconnects, the proof is submitted via x402 to the preferred blockchain, finalizing the transaction.

5. **Auditability & Sync**

* All reconciled payments are verifiable on-chain. Participants can audit their history without revealing counterparties.

***

#### **Modular and Chain-Agnostic**

The DashPay network is:

* **Composable** – works inside existing apps, agents, and devices
* **Chain-agnostic** – supports Base, Solana, Polygon, and other L1/L2 networks
* **Extensible** – modular logic for compliance, settlement routing, and integration

***

DashPay transforms payments from static, user-initiated actions into **network-native events** — verifiable, programmable, and optimized for autonomy. Whether it's a tap at checkout or a bot settling an API fee, the network is designed to confirm, reconcile, and scale silently in the background.


---

# 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:

```
GET https://dashpay.gitbook.io/docs/network-and-ecosystem/dashpay-network-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.