> 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/developer-resources.md).
# Developer Resources
DashPay is designed to be **modular, open, and developer-friendly**. Whether youβre building wallets, terminals, bots, or autonomous agents, DashPay provides the tooling, documentation, and libraries you need to integrate privacy-preserving, offline-ready payments into your systems.
Below is a curated list of developer-facing resources to help you get started:
***
#### **π¦ SDKs & Client Libraries**
* **DashPay SDK (JavaScript)** β Core client functions for proof generation, x402 handling, and mobile wallet integration
* **DashPay Device SDK (C/Embedded)** β Lightweight firmware tools for NFC terminals and embedded devices
* **ZK-NFC Wallet Kit** β Sample code for mobile tap-to-pay functionality with local proof handling
* **Risk Engine Module (WASM)** β Drop-in verifier and anomaly scanner for local AI fraud detection
> π Coming soon: GitHub repo release for SDKs, code samples, and integration templates
***
#### **π Documentation & Guides**
* **Integration Manual** β Step-by-step setup for merchant devices, vending systems, and POS apps
* **x402 Developer Guide** β How to issue and handle 402 payment challenges in services and agents
* **API Reference** β Full API for DashPay relayers, reconciliation nodes, and device sync
* **ZK Proof Spec** β Technical breakdown of DashPayβs ephemeral zero-knowledge proof format
* **Security & Risk Doc** β Threat models, anti-replay design, and on-device protections
***
#### **π§ͺ Testnets & Playground**
* **DashPay Testnet Portal** β Faucet access, smart contract explorer, and testproof validator
* **Agent Simulator** β Run local bots that perform x402 requests and proof-based responses
* **Hardware Emulator** β Simulate offline NFC terminals using a CLI or virtual wallet
> Use the playground to test interactions before going live on mainnet.
***
#### **π€ Community & Support**
* **Developer Forum** β Ask questions, propose improvements, and share tools
* **Bug Bounty Program** β Report vulnerabilities and earn rewards
* **Discord / Matrix Dev Chat** β Real-time support from the DashPay core and ecosystem teams
* **Hackathons & Grants** β Opportunities to build on DashPay and receive ecosystem funding
***
#### **π Core Repositories & Packages**
*(coming soon)*
* `@dashpay/sdk` β Client library (npm)
* `dashpay-terminal-firmware` β Reference NFC firmware
* `dashpay-agent-js` β For autonomous service bots and API integrations
* `dashpay-utils` β Hashing, ZK encoding, and transaction tools
***
DashPay is more than a system β itβs a toolkit for the next generation of decentralized, humanless, and offline-native value movement. If youβre building the future of payments, **this is where it starts.**
---
# 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/developer-resources.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.