> 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/launch-and-build/roadmap-and-milestones.md).

# Roadmap & Milestones

DashPay’s development is structured across three core phases, each designed to deliver modular, testable components that move closer to decentralized, real-world value transfer. The roadmap prioritizes **offline-first capability**, **hardware integration**, and **machine-native payment infrastructure**, while enabling seamless onboarding for developers, merchants, and autonomous agents.

***

#### **Phase 1 — Foundation & Proof of Concept**

**Status: Complete / Ongoing**

Focus: Core architecture, cryptographic tooling, offline flows

* Design and implement the x402 request/response settlement engine
* Launch mobile-first ZK-NFC Tap Wallet prototype (Android)
* Develop ephemeral ZK payment proof structure and device signing logic
* Test offline-to-online sync queue using local proof storage
* Deploy first DashPay smart contracts on Base and testnet environments
* Release DashPay Whitepaper v1 and early technical documentation

***

#### **Phase 2 — Beta Network & Field Pilots**

**Status: In Progress**

Focus: Developer tools, hardware integration, real-world testing

* Release DashPay Beta Wallet for limited user groups
* Integrate AI Risk Engine for on-device fraud detection and rate-limiting
* Launch pilot programs with small merchants, vending systems, and embedded POS terminals
* Publish open-source hardware SDKs and NFC terminal reference designs
* Expand SDKs for developers and agent-based integrations (bots, APIs, IoT)
* Run full security audits on ZK flows and offline proof handling

***

#### **Phase 3 — Mainnet & Decentralized Scaling**

**Planned: Q1–Q2 2026**

Focus: Public release, governance, and interoperability

* Launch DashPay Mainnet and public x402 settlement relay
* Enable multi-chain support (Base, Solana, BSC, Polygon, etc.)
* Introduce DashNode light clients to assist with offline proof sync
* Open staking model and community-led governance for x402 parameters
* Partner with manufacturers to embed DashPay into POS and IoT systems
* Begin onboarding global merchants and open DashPay to cross-border agents

***

#### **Post-Mainnet Vision**

**Beyond 2026**

* Expand support for cross-chain reconciliation and dynamic fee routing
* Launch DashPay Dev Grants for infrastructure, analytics, and ecosystem dApps
* Release compliance-optional modules for enterprise and region-specific use
* Grow the network into underserved areas: rural economies, disaster zones, and machine-to-machine finance

***

DashPay is not just a wallet — it’s an infrastructure layer designed to bring **autonomous, privacy-first payments** to places and systems traditional finance and DeFi cannot reach. Every phase in this roadmap brings us closer to a world where **transactions happen anywhere, between anything — instantly, securely, and without exposure.**


---

# 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/launch-and-build/roadmap-and-milestones.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.