> 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/zk-nfc-tap-wallets.md).

# ZK-NFC Tap Wallets

DashPay introduces a new payment primitive: **ZK-NFC Tap Wallets**, a mobile-first and hardware-compatible wallet system designed to enable secure, private, and instant value transfer — without internet, addresses, or accounts.

Built around **zero-knowledge ephemeral proofs** and short-range communication protocols like NFC or Bluetooth LE, these wallets allow two parties to **exchange cryptographic proofs locally**, verifying a transaction without exposing sensitive information or requiring on-chain confirmation in real time.

***

#### **How It Works**

1. **Tap to Initiate**\
   A user taps their DashPay wallet (phone or terminal) near another device (merchant, peer, or agent).
2. **Proof Is Generated**\
   The payer’s wallet creates an **ephemeral zero-knowledge proof** verifying they have sufficient balance, authorization, and a valid transaction intent — without revealing their wallet address or token holdings.
3. **Local Validation**\
   The receiver’s wallet or terminal verifies the proof offline, confirms its validity, and records it as a **pending payment**, including timestamp and cryptographic metadata.
4. **Deferred Finality**\
   Once either party regains connectivity, the proof is submitted through DashPay’s **x402 layer** and reconciled on-chain using the appropriate settlement network (e.g. Base, Solana, BNB).

***

#### **Why It Matters**

Traditional crypto wallets require:

* Online access to sign and broadcast transactions
* Wallet addresses that can be tracked and linked
* UIs that expose metadata or rely on custodians

ZK-NFC Tap Wallets eliminate all of that:

* **No address exposure** — Proofs are unlinkable and self-contained
* **No network dependency** — Payments finalize asynchronously
* **No visible metadata** — Nothing leaks in transit or at the point of sale
* **No QR scanning needed** — UX is as seamless as tap-to-pay systems

***

#### **Built for the Field**

ZK-NFC Tap Wallets are ideal for:

* **Retail environments** — Street merchants, cafés, mobile vendors
* **Peer-to-peer trade** — Local exchanges without third parties
* **IoT and devices** — Smart meters, EV chargers, offline vending
* **Disaster zones & rural regions** — No Wi-Fi? No problem. Just tap.

***

#### **Security & Trust**

* All proofs are one-time-use, bound to a nonce and TTL (time-to-live)
* Device keys are stored in secure enclaves (where supported)
* Replay or tampering attempts are flagged by the local **AI risk engine**
* Loss of device does not compromise funds if recovery seed is stored safely

***

ZK-NFC Tap Wallets make **true offline crypto payments possible** — not with QR codes, not with hot wallets, but with lightweight, verifiable proof-of-payment systems that feel like magic but are backed by math.

They are **invisible to observers**, **immediate for users**, and **secure by design**.


---

# 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/network-and-ecosystem/zk-nfc-tap-wallets.md?ask=<question>&goal=<endgoal>
```

`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.