### Terms and Conditions
- [x] I agree to the [Grant Agreement](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_f81ef4e4b5f040038350270590eb2e42.pdf) terms if funded
- [x] I agree to [Provide KYC information](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD
- [x] I agree to disclose conflicts of interest
- [x] I agree to adhere to the [Code of Conduct](https://forum.zcashcommunity.com/t/zcg-code-of-conduct/41787) and [Communication Guidelines](https://forum.zcashcommunity.com/t/zcg-communication-guidelines/44284)
- [x] I understand all milestone deliverables will be validated and accepted by their intended users or their representatives, who will confirm that the deliverables meet the required quality, functionality, and usability for each user story.
- [x] I agree that for any new open-source software, I will create a `CONTRIBUTING.md` file that reflects the high standards of Zcash development, using the [`librustzcash` style guides](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference.
- [x] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any [merge](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), [branch](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), [pull request](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and [commit](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the `librustzcash` repository.
- [x] I agree to post request details on the [Community Forum](https://forum.zcashcommunity.com/c/grants/33)
- [x] I understand it is my responsibility to post a link to this issue on the [Zcash Community Forums](https://forum.zcashcommunity.com/c/grants/33) after this application has been submitted so the community can give input. I understand this is required in order for ZCG to discuss and vote on this grant application.
### Application Owners (@Octocat, @Octocat1)
ONEONUORA , JayWebtech, anonfedora
### Organization Name
Ebube Ebuka Onuora
### How did you learn about Zcash Community Grants
Twitter, Community
### Requested Grant Amount (USD)
$120,000
### Category
Non-Wallet Applications
### Project Lead
```project-lead.yaml
Name: Ebube Ebuka Onuora
Role: Founder & CEO
Background: Full-stack software developer with expertise in React.js, Node.js, Express, MongoDB, and Web3 technologies. AI specialist and blockchain enthusiast experienced in smart contracts, decentralised applications, and privacy-preserving blockchain integrations. Successfully built full-stack applications including Fortichain (A decentralized smart contract auditing platform) and InheritX (decentralised crypto inheritance platform). Proficient in Zcash, Ethereum, Bitcoin and multi-token integrations.
Responsibilities:
1.Oversee the design and development of the Zaps MVP
2.Manage milestone delivery, budget allocation, and project timeline
3.Ensure Zcash protocol integration and privacy-first implementation
4.Coordinate security audits, compliance, and QA
5.Lead open-source SDK development and documentation
```
### Additional Team Members
```team-members.yaml
- Name: Jethro Adamu
Role: Chief Operating Officer (COO) & Co-Founder
Background: Experienced operations and business strategy professional with expertise in fintech, product management, and scaling digital platforms. Skilled in business development, process optimization, and team leadership. Has successfully overseen operations for technology-driven startups, ensuring smooth execution and adoption of innovative solutions.
Responsibilities:
1.Oversee day-to-day operations and project execution
2.Manage merchant onboarding, partnerships, and stakeholder relations
3.Coordinate cross-functional teams between product, engineering, and business units
4.Ensure milestone delivery, operational efficiency, and compliance
5.Support strategic growth and scaling initiatives
- Name: Eleazer Musa
Role: Chief Technology Officer (CTO) & CO-Founder
Background: Experienced blockchain and software engineer with deep expertise in cryptography, decentralised applications, and scalable Web3 architectures. Skilled in Zcash protocol integration, smart contract development, and multi-chain wallet systems. Has successfully led technical teams on projects involving privacy-focused blockchain solutions and fintech applications.
Responsibilities:
1.Lead all technical architecture decisions for Zaps
2.Oversee backend, mobile wallet, and merchant dashboard development
3.Ensure shielded Zcash (z-address) transaction integration and performance optimization
4.Manage technical security audits and compliance
5.Coordinate developer contributions and maintain open-source SDKs
```
### Project Summary
Zaps is a Zcash-powered contactless payment app that enables users to make tap-to-pay shielded ZEC transactions, while merchants receive instant USD settlement, bringing private, borderless cryptocurrency payments into real-world commerce
### Project Description
Zaps is a Zcash-powered, contactless payment application designed to bring real-world utility, privacy, and adoption to ZEC. The app enables users to make tap-to-pay transactions using shielded Zcash (z-addresses), while merchants receive instant settlement in USD, removing volatility and adoption barriers. By integrating NFC-based payments, shielded transaction technology, and automatic ZEC-to-USD off-ramping, Zaps simplifies cryptocurrency payments for both users and merchants without requiring knowledge of crypto or custodial wallets.
Zaps also provides open-source SDKs and APIs for developers and merchants, ensuring scalable integration into point-of-sale systems, e-commerce platforms, and other payment rails. Its architecture is designed to maximize privacy, security, and regulatory compliance, using Sapling-based shielded transactions and optional selective disclosure.
**Project Goals**
# Expand Real-World Zcash Adoption
- Make ZEC usable for everyday commerce through tap-to-pay payments.
- Provide merchants with USD settlement, lowering barriers to acceptance.
# Enhance User Privacy
- Default to shielded ZEC transactions, protecting sender, receiver, and transaction amounts.
- Optional selective disclosure for regulatory compliance.
# Provide a Merchant-Friendly Solution
- Simplify crypto payments with automatic USD conversion.
- Offer a merchant dashboard for transaction tracking and settlements.
# Contribute to the Zcash Ecosystem
- Open-source mobile SDKs and APIs for developers and merchants.
- Promote shielded transaction growth, increasing overall Zcash network privacy.
# Enable Global Scalability
- NFC and QR code support for cross-platform, international adoption.
- Modular off-ramp architecture for multi-region USD settlement.
# Demonstrate Security and Compliance
- Implement wallet security audits, backend review, and KYB/KYC procedures for merchants.
- Ensure safe, private, and regulatory-aligned operation of shielded payments.
Zaps positions Zcash as a practical, privacy-preserving payment solution, increasing shielded transaction volume, driving merchant adoption, and offering a usable real-world application for privacy-conscious users globally. It bridges the gap between crypto enthusiasts and everyday commerce, creating a sustainable adoption pathway for ZEC.
### Proposed Problem
Despite Zcash’s strong privacy features, real-world adoption remains limited because there are few practical payment solutions that allow users to spend ZEC easily. Merchants are often hesitant to accept ZEC due to price volatility, regulatory concerns, and complex crypto onboarding. Existing solutions require users to hold multiple tokens or use traditional cards, undermining privacy and creating friction. There is a clear need for a simple, contactless ZEC payment solution that preserves privacy for users while ensuring merchants can receive stable fiat settlement.
### Proposed Solution
Zaps solves the adoption and usability problem by providing a contactless, Zcash-powered payment app that allows users to make tap-to-pay shielded ZEC transactions with ease. Merchants receive instant USD settlement into their local bank accounts, removing volatility concerns and simplifying crypto acceptance. By integrating NFC payments, shielded transactions, and a merchant dashboard, Zaps preserves user privacy while enabling real-world commerce. Open-source SDKs and APIs further allow developers and merchants to easily integrate ZEC payments into POS systems and e-commerce platforms, accelerating global adoption.
### Solution Format
Zaps will be delivered as a production-ready software solution, consisting of:
1.Mobile Application (iOS & Android) – allows users to make tap-to-pay ZEC transactions with shielded (z-address) and transparent (t-address) wallets.
2.Merchant Web Dashboard – enables merchants to receive ZEC payments and automatically settle in USD into their local bank accounts and track transactions
3.Open-Source SDK & APIs – for developers and merchants to integrate ZEC payments into POS systems, e-commerce platforms, and other applications.
4.Infrastructure Components – Zcash lightwalletd integration, backend APIs, and monitoring/DevOps required for secure and reliable operation.
5. Documentation – guides for developers, merchants, and users to ensure smooth adoption and integration.
The solution is fully functional, privacy-preserving, and designed for real-world commerce, with USD settlement as a core feature.
### Dependencies
1.Technical Dependencies:
- Zcash SDK / Lightwalletd: required for wallet integration, shielded transactions, and network synchronization.
- Backend Infrastructure: servers, APIs, monitoring, and DevOps tools to support payment processing and merchant dashboards.
- Mobile Platforms: iOS and Android development environments (Xcode, Android Studio) and NFC/QR payment libraries.
- Payment Off-Ramp Services: integration with licensed financial partners for USD settlement into merchant bank accounts.
2. Resource Dependencies:
- Development Team: engineers skilled in blockchain, Web3, mobile app development, and backend systems.
- Security & Compliance Experts: to audit the wallet, backend, and settlement processes.
- Designers: for UX/UI of mobile apps and merchant dashboards.
3. Collaborations / Partnerships:
- Zcash Community & Developers: to ensure protocol compatibility, testing, and contributions to open-source SDKs.
- Merchant Partners: for pilot testing and real-world adoption.
- Financial Institutions / Payment Processors: to enable USD settlement for merchants.
Summary: Zaps successful delivery relies on a combination of technical tools, skilled personnel, and strategic partnerships, ensuring both privacy-preserving transactions and real-world merchant adoption.
### Technical Approach
Zaps will leverage Zcash as the primary payment rail, using Sapling shielded transactions for privacy-preserving payments. The mobile apps (iOS and Android) will integrate Zcash SDKs and Lightwalletd to enable both z-address (shielded) and t-address (transparent) transactions. NFC and QR-based payment methods will allow tap-to-pay functionality across devices, while the backend system handles transaction verification, ledger maintenance, and merchant USD settlement.
The system architecture is modular, including:
- Mobile Wallet Layer: user wallet, transaction signing, and NFC/QR payment interface
- Backend Layer: APIs for payment processing, transaction monitoring, and USD settlement
- Merchant Dashboard: web interface for transaction tracking, reporting, and payout management
- Open-Source SDKs & APIs: enable third-party developers to integrate ZEC payments into POS systems and e-commerce platforms
**Development Tools & Methodology:**
- Frontend: React Native for cross-platform mobile apps, React.js for merchant dashboard
- Backend: Node.js + Express.js, MongoDB for ledger and user/merchant data
- Blockchain Integration: Zcash SDKs, Lightwalletd, and Shielded transaction libraries
- Security: End-to-end encryption, wallet audits, and secure key management
- DevOps: Cloud hosting, CI/CD pipelines, and monitoring for reliable operation
This approach ensures privacy, scalability, and real-world usability, while keeping the system open-source and easily adoptable by merchants and developers globally.
### Upstream Merge Opportunities
N/A
### Hardware/Software Costs (USD)
$17,000
### Hardware/Software Justification
These hardware and software costs are essential to develop, test, and deliver the Zaps MVP. They enable cross-platform mobile app development, secure Zcash wallet integration, backend transaction processing, and merchant dashboard functionality, while supporting automation, monitoring, and security audits. Without these tools, the project cannot achieve its milestones or ensure reliable, privacy-preserving payments.
### Service Costs (USD)
$24,000
### Service Costs Justification
These service costs are necessary to ensure the Zaps MVP is secure, reliable, and compliant. They cover security audits, ZEC-to-USD settlement integration, and hosting/operational services required for development, testing, and live transactions. Without these services, the project cannot safely or effectively deliver a privacy-preserving, real-world Zcash payment solution.
### Compensation Costs (USD)
$79,000
### Compensation Costs Justification
The compensation costs cover the key team members essential to building and delivering the Zaps MVP:
- Founder & CEO (Ebube Ebuka Onuora) – $15,000: Oversees milestone delivery, technical integration, and project management, ensuring the MVP meets all functional and privacy requirements.
- CTO & CO-Founder (Eleazer Musa) – $15,000: Responsible for all technical architecture, Zcash wallet integration, backend and mobile development, and security compliance.
- COO & Co-Founder (Jethro Adamu) – $10,000: Manages day-to-day operations, merchant onboarding, partnerships, and coordination between teams.
- Development & QA Team – $39,000: Builds the mobile applications, backend APIs, merchant dashboard, and conducts testing to ensure stability and usability.
Compensation rates are competitive for blockchain and Web3 development, reflecting the specialized skills required for Zcash integration, shielded transactions, and secure, privacy-focused fintech solutions. All costs are time-bound to the grant period and directly tied to milestone delivery, ensuring efficient use of funds for MVP completion.
### Total Budget (USD)
$120,000
### Previous Funding
No
### Previous Funding Details
N/A
### Other Funding Sources
No
### Other Funding Sources Details
N/A
### Implementation Risks
Implementation Risks:
1.Technical Integration Risk: Integrating Zcash shielded transactions, tap-to-pay NFC, and multi-token support is complex. Bugs or delays in wallet SDKs, Lightwalletd, or mobile APIs could slow development.
2.Security & Privacy Risk: Handling shielded ZEC transactions and merchant settlements requires strict security. Vulnerabilities in wallets, backend APIs, or payment off-ramps could compromise user privacy or funds.
3.Regulatory & Compliance Risk: USD settlement for merchants involves compliance with financial regulations across different regions. Delays in approvals or regulatory requirements may affect rollout.
4.Operational Risk: Limited developer resources, dependency on third-party services for USD settlement, or hosting outages could impact milestone delivery.
5.Adoption Risk: Convincing merchants and users to adopt ZEC payments, even with USD settlement, may take longer than expected due to awareness, technical onboarding, or market resistance.
**Mitigation Strategies:**
- Conduct rigorous security audits and testing before release.
- Collaborate with compliant financial partners for merchant settlement.
- Build a scalable, modular architecture to allow incremental feature rollout.
- Provide clear documentation, merchant support, and SDKs to reduce onboarding friction.
### Potential Side Effects
1. Regulatory Scrutiny: Even with privacy-preserving Zcash transactions, increased adoption could attract regulatory attention, requiring ongoing compliance efforts.
2. User Misuse: Users might attempt to use ZEC payments for illicit purposes, creating reputational or legal risks for the platform.
3. Volatility Exposure: Although merchants receive USD settlement, users holding ZEC could face value fluctuations, which may affect user experience.
4. Technical Failures: Bugs or downtime in the wallet, payment processing, or settlement systems could temporarily disrupt service, impacting trust and adoption.
**Mitigation Measures:**
- Implement compliance checks and clear terms of use for merchants.
- Maintain robust monitoring, incident response, and secure wallet architecture.
- Educate users about ZEC volatility and safe usage practices.
### Success Metrics
The success of Zaps will be measured using both adoption and technical performance metrics:
1. User Adoption: Number of active users making ZEC payments through the app.
2. Merchant Adoption: Number of merchants integrated with Zaps and successfully receiving USD settlements.
3. Transaction Volume: Total number and value of ZEC transactions processed via Zaps.
4. Shielded Transaction Usage: Percentage of transactions using z-addresses (privacy-preserving shielded transactions).
5. System Reliability: Uptime of mobile apps, backend APIs, and payment processing infrastructure.
6. Security & Compliance: Successful completion of wallet and backend security audits with no major vulnerabilities.
7. Developer Adoption: Number of third-party developers integrating Zaps SDKs and APIs.
These metrics will provide a clear picture of both ecosystem impact and technical success, demonstrating real-world Zcash adoption, privacy usage, and system reliability.
### Startup Funding (USD)
$60,000
### Startup Funding Justification
The startup funding is needed to initiate development and deliver the Zaps MVP, ensuring the project reaches a functional and testable stage. The requested $60,000 USD will be used to:
1. Cover Hardware and Software Costs (~$8,500): Purchase and maintain mobile development tools, backend servers, Zcash SDK integration, DevOps, and security software required for building and testing the MVP.
2. Fund Service Costs (~$12,000): Pay for essential security audits, USD off-ramp/settlement integration services, and hosting/operational infrastructure to support reliable and secure payments.
3. Provide Partial Compensation (~$39,500): Support the core team, including the CEO, CTO, COO, and development/QA team, ensuring skilled personnel are available to implement and deliver key milestones.
This initial funding will enable Zaps to build a functional, privacy-preserving, and real-world usable Zcash payment solution, validate the MVP with merchants and users, and lay the groundwork for requesting the remaining funds to scale and expand adoption globally.
### Milestone Details
```milestones.yaml
- Milestone: 1
Amount (USD): 10,000
Expected Completion Date: 2026-01-31
User Stories:
- As a project lead, I want a detailed project roadmap, so that the team has a clear development plan.
- As a developer, I want a fully configured development environment, so that I can start building the MVP efficiently.
Deliverables:
- Project roadmap and milestone documentation finalized
- Technical architecture designed and documented
- Mobile, backend, and DevOps development environments fully configured
Acceptance Criteria: Project lead and core team review confirms roadmap, architecture, and development environments are complete and ready for MVP development
- Milestone: 2
Amount (USD): 10,000
Expected Completion Date: 2026-02-28
User Stories:
- As a user, I want to store Zcash in a wallet, so that I can make payments securely.
- As a user, I want to make tap-to-pay transactions, so that I can pay merchants quickly and privately.
Deliverables:
- Mobile wallet integrated with Zcash SDK & Lightwalletd
- Support for shielded (z-address) and transparent (t-address) transactions
- Core tap-to-pay functionality implemented
Acceptance Criteria: Users can successfully add ZEC to their wallet and complete tap-to-pay transactions in a test environment
- Milestone: 3
Amount (USD): 10,000
Expected Completion Date: 2026-03-31
User Stories:
- As a merchant, I want to view received payments, so that I can track my sales.
- As a merchant, I want to receive USD settlements, so that I avoid exposure to ZEC volatility.
Deliverables:
- Web-based merchant dashboard developed
- USD off-ramp integration completed
- Initial pilot merchants onboarded
Acceptance Criteria: Merchants can log in, view transactions, and receive test USD settlements successfully
- Milestone: 4
Amount (USD): 10,000
Expected Completion Date: 2026-04-30
User Stories:
- As a user, I want my transactions to be secure and private, so that I can trust the app.
- As a merchant, I want the payment system audited, so that I know it is compliant and safe to use.
Deliverables:
- Complete backend and wallet security audits
- Compliance review for merchant settlement and operational processes
- Audit feedback addressed and fixes implemented
Acceptance Criteria: Independent security auditors and compliance team approve MVP as secure and regulatory-aligned
- Milestone: 5
Amount (USD): 10,000
Expected Completion Date: 2026-05-31
User Stories:
- As a user, I want the app to work reliably, so that I can make payments without errors.
- As a merchant, I want to test the dashboard and payments, so that I can provide feedback before launch.
Deliverables:
- Beta release of mobile apps and merchant dashboard
- Feedback collection from early users and pilot merchants
- Bug fixes and performance improvements implemented
Acceptance Criteria: Users and merchants confirm beta functions correctly and report minimal critical issues
- Milestone: 6
Amount (USD): 10,000
Expected Completion Date: 2026-06-30
User Stories:
- As a user, I want a fully functional app, so that I can make Zcash payments in real-world scenarios.
- As a developer, I want SDKs and APIs documented, so that third-party integrations are possible.
Deliverables:
- Public release of Zaps MVP (iOS & Android)
- Open-source SDKs and APIs published
- Comprehensive documentation for developers, merchants, and users
- Initial marketing and awareness activities completed
Acceptance Criteria: MVP is publicly available, SDKs and documentation are accessible, and early users/merchants successfully complete real-world transactions
```
### Supporting Documents
```files.yaml
- [PRD](https://docs.google.com/document/d/1_BVHCbqw4ZZOV0dxZZxv3965aWhVEg8l3_GScCKQghk/edit?usp=sharing) : It contents details about ZAP
```