### 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)
imerkle
### Organization Name
imerkle
### How did you learn about Zcash Community Grants
tg
### Requested Grant Amount (USD)
$40,500
### Category
Non-Wallet Applications
### Project Lead
```project-lead.yaml
Name: imerkle
Role: founder/lead dev
Background: Sr soft engg, worked with defi startups
Responsibilities: build and launch , initial bootstrap mm, onboarding initial users
```
### Additional Team Members
```team-members.yaml
- Name: to be hired
Role: community manager
Background: community manager
Responsibilities: documentation, and support, dispute mediation
```
### Project Summary
An P2P mobile app enabling Indian users to buy and sell Zcash via Cash Deposit Machines (CDMs) using NEAR smart contracts for escrow, eliminating the threat of bank account freezes and de-anonymization when linking real-world bank accounts to public blockchain addresses.
### Project Description
In India, peer-to-peer cryptocurrency onboarding is broken across two major vectors:
The Bank Account Freeze Crisis: Nearly all P2P traders using digital rails (UPI, IMPS, NEFT) experience abrupt bank account freezes. When cyber-crime authorities flag a compromised transaction, automated bank liens cascade down 3–5 hops, locking accounts of innocent buyers and sellers. The Cash Deposit Machine (CDM) rail solves this: buyers physically feed paper cash into a seller’s account at a bank kiosk/cash recycler, severing the digital inter-bank fraud-lien chain.
The KYC / On-Chain Doxxing Threat: Currently, no non-custodial, privacy-preserving fiat ramp exists for Indian users. Centralized P2P desks force invasive identity collection, permanently linking real-world identities, PAN numbers, and physical bank accounts directly to on-chain cryptocurrency addresses. On public blockchains, this gives anyone visibility into a user's net worth, balance history, and transaction counter-parties. Giving a bank account to a counterparty and linking it to a transparent ledger is inherently unsafe.
Why Zcash Is the Only Viable Solution:
Zcash is uniquely positioned to solve this paradox through its zero-knowledge shielded pools By combining real-world physical cash deposits with shielded ZEC payouts, the connection between physical fiat and on-chain holdings is completely severed:
The seller receives physical cash clearance in their bank account or withdraws cash from atm.
The buyer receives shielded ZEC into a unified address (u1...), ensuring their wealth and future spending habits cannot be tracked, profiled, or tied back to their bank visit.
A modest protocol fee (e.g., 0.5%–0.75%) collected on completed trades is programmatically directed to a protocol treasury to automatically buy back ZEC
### Proposed Problem
No Private Indian Ramps: Indian users have zero privacy-preserving fiat on/off-ramps for Zcash.
Doxxing Vulnerabilities: Sharing bank account details on transparent P2P desks permanently doxxes users by associating real-world banking metadata with public blockchain addresses.
### Proposed Solution
NEAR Smart Contract Escrow: A lightweight, non-custodial NEAR smart contract that securely time-locks bridged ZEC collateral, preventing either party from rug-pulling during a physical cash exchange.
Bootstrapped Liquidity Pool: A dedicated $10,000 liquidity buffer deployed into verified market-maker maker-orders on the app to ensure reliable order fill rates from day one.
Community Manager & Operations: A dedicated regional community lead to handle merchant onboarding, dispute arbitration, user education, and support.
ZEC Buyback Treasury: Platform trading fees are routed directly to buy ZEC on the open market, locking it into the project treasury to fund ongoing operations and long-term liquidity.
### Solution Format
Mobile application (React Native / Flutter for Android and iOS).
Rust-based NEAR time-locked escrow smart contract.
Operational runbooks for regional community management and dispute mediation.
### Dependencies
NEAR Protocol for smart contract execution and NEAR Chain Signatures (MPC) for cross-chain bridging.
Lightwalletd / Zcash shielded RPC endpoints.
### Technical Approach
1. End-to-End User Experience (Native Wallet Flow)
From the user’s perspective, the experience is strictly native Zcash to native Zcash. Neither buyer nor seller needs to hold NEAR tokens or manage gas. The seller funds the escrow by sending ZEC to a deposit address generated by the platform. The platform bridges this into wrapped ZEC on NEAR.
2. Non-Custodial Time-Locked Escrow (NEAR Smart Contract)
The seller locks the bridged ZEC into a dedicated, audited NEAR Escrow Contract.
Time-Lock: Funds are locked for a strict x-minute window to allow for physical travel to the ATM.
Trustless Security: During this window, the seller cannot withdraw the funds. The funds can only be released with cryptographic confirmation of fiat settlement (seller confirmation). If the timer expires without a deposit, the seller can unilaterally reclaim their ZEC.
3. Cross-Chain Settlement & Zcash Auto-Shielding
Upon escrow release, the NEAR contract triggers a cross-chain Chain Signature transaction.
Native ZEC is sent directly to the buyer's Transparent Zcash Address (t1...).
The buyer's mobile wallet (e.g., Zashi, Ywallet) utilizes built-in Auto-Shielding to immediately sweep the funds from the transparent address into their shielded pool (u1...), breaking the linkability perfectly while keeping the UX seamless.
### Upstream Merge Opportunities
no
### Hardware/Software Costs (USD)
0
### Hardware/Software Justification
n/a
### Service Costs (USD)
$500
### Service Costs Justification
domain infra app store
### Compensation Costs (USD)
$40,000
### Compensation Costs Justification
$25,000 - founder compensation - ~2m+ fulltime
$5,000 - community manager hire
$10,000 - initial liquidity bootstrap -> treasury for ops/marketing/maintenance
### Total Budget (USD)
$40,500
### Previous Funding
No
### Previous Funding Details
_No response_
### Other Funding Sources
No
### Other Funding Sources Details
_No response_
### Implementation Risks
Cold-Start Liquidity Starvation: P2P platforms fail if initial buyers find empty order books.
Mitigation: The $10,000 bootstrap liquidity fund allows the team to maintain active sell/buy quotes on top CDM networks (SBI, HDFC) from day one.
### Potential Side Effects
Regulatory & PMLA Scrutiny: Operating a fiat-to-crypto ramp using privacy-focused assets can attract scrutiny
Mitigation via Zcash Viewing Keys
Selective Audit Disclosure: By separating spending keys from viewing keys, users can generate read-only Unified Full Viewing Keys (UFVKs) or transaction-specific viewing proofs. This allows individuals to cryptographically prove the legitimate origin, destination, and exact value of their funds to tax authorities or auditors without exposing their overall balance or forfeiting fund custody.
### Success Metrics
The project will use measurable adoption metrics.
Product metrics
By the end of the pilot:
100+ completed INR → ZEC transactions;
10+ active P2P sellers;
90%+ successful order completion rate;
median settlement time below 30 minutes for transactions where the seller and CDM workflow are immediately available;
dispute rate below 10%.
### Startup Funding (USD)
$12500
### Startup Funding Justification
Covers initial solo engineering to scaffold the mobile codebase, write and test the dedicated NEAR escrow smart contract before public launch.
### Milestone Details
```milestones.yaml
Milestone: 1
Amount (USD): 23000
Expected Completion Date: 1-2 months after startup funding
User Stories:
"As an Indian crypto buyer, I want to view active Zcash buy/sell orders and pay via cash deposit or cardless ATM withdrawal, so that I can acquire shielded ZEC without exposing my bank account to digital UPI/IMPS freeze risks."
"As a trader, I want an active order book from day one, so that my trade orders are filled quickly without waiting for organic liquidity."
Deliverables:
Production-ready mobile application release (Android APK and iOS build) supporting dual ATM flows (buyer CDM cash deposit and seller cardless ATM cash withdrawal).
On-chain deployment of $10,000 bootstrap liquidity into a multi-sig order book maker float.
Acceptance Criteria: The application is publicly downloadable, test users complete an end-to-end mainnet trade from an Indian ATM/CDM into a shielded Zcash address, and the $10,000 liquidity float is verifiable on-chain and actively quoting on the order book.
Milestone: 2
Amount (USD): 5000
Expected Completion Date: 2 months after startup funding
User Stories:
"As a new user visiting an ATM/CDM for the first time, I want dedicated support and localized onboarding guides, so that I do not make errors at the machine."
"As a trader facing a bank or slip dispute, I want an active regional arbitrator, so that physical deposit proof is evaluated quickly and fairly."
Deliverables:
Onboarding of a dedicated regional Community Manager ($5,000 allocation) to handle merchant outreach, dispute arbitration, and daily user support.
Demonstration of organic platform traction with at least 30 verified completed mainnet P2P trades across distinct users.
Active community help channels (Telegram/Discord) and published user guides covering CDM bank operations, PAN cash deposit limits, and Unified Full Viewing Key (UFVK) tax compliance.
Acceptance Criteria: Verified completion of at least 100 mainnet trades validated by community participants on the Zcash Community Forum, active regional support channels managed by the community lead, and public release of compliance/user guides.
```
### Supporting Documents
```files.yaml
- File Name 1: Brief description of the file contents
- File Name 2: Brief description of the file contents
```