0xramp: ZEC payments and wallet integrations (revision of #408)

1. Executive summary and decision snapshot

0xramp Labs requests $45,000 over 16 weeks, delivered by two part-time founders, Michael and Vini Barbosa, with no hires. The request remains under review. It funds Zcash-only payments through local rails, risk disclosures, ZEC-attributed metrics, documentation and a reusable wallet integration—not new settlement infrastructure. [1][4]

Funding comprises $7,500 upfront and four $9,375 acceptance-based milestones. The strongest capability evidence is an operating payment product and wallet-integration work already underway; the principal evaluation issues are demonstrable Zcash-specific demand, third-party financial risks and completion of a partner-validated route. Inference: this is best assessed as a bounded integration experiment, rather than established adoption infrastructure. [6][7]

2. Applicant and team track record

Michael leads architecture, security, integrations and delivery; his stated background includes over 4.5 years leading Zcash Brazil and creating openzcash.org. Vini leads SDK development, documentation, pilots, reporting and funds management, citing technical-writing and developer-relations experience since 2020. The application says neither 0xramp Labs nor Vini previously received ZCG funding; Michael contributed to separately funded Zcash Brazil work. No grounded evidence found of accepted milestones or measured outcomes from those earlier team activities. [1]

The applicant reports 357 completed orders and $25,533.83 in USDC settlements during August 1–September 27, 2026. These totals support operating experience, but explicitly do not identify ZEC’s share. The SDK is a non-production v0 pilot, with a Zingo reference application described as public work in progress—not a completed wallet integration. [6][7]

3. Proposal scope, milestones, budget, technical approach, and dependencies

Budget: $30,000 founder compensation, $12,000 services/reserves and $3,000 infrastructure/tools. The supplied budget gives category totals, not a detailed allocation within services/reserves. [7]

These follow the $7,500 startup payment. No grounded evidence found of milestone completion for this request. [7]

PAY currently supports Brazil’s static Pix QR codes. P2P.me handles fiat settlement through merchants and Base escrow; NEAR Intents supplies conversion through an intermediate USDC/Base step. The current ZEC route uses transparent receivers, not an end-to-end shielded payment journey. [6]

The proposed first wallet pilot is SELL ZEC → BRL, subject to partner confirmation. QR-PAY is outside the current v0 SDK scope; wallet signing, browser transport, return handling and recovery require validation. [7]

4. Community discussion, arguments, responses, and resolution

Strongest arguments against: the previous $206,000 request was declined on September 14. Committee concerns included user safety, bank-account freezes, unclear responsibility across providers, limited incremental Zcash value, centralized settlement dependence and subsidizing a business that should sustain itself. Artkor supported the proposal’s ambition despite its risks. [11]

Strongest substantive case for the revision: the applicant identifies Zcash-specific contributions beyond settlement—ZEC-only PAY, ZIP-321 handoff, wallet integration, ZEC-attributed reporting and educational material. It clarifies that 0xramp does not receive users’ funds and proposes actor-specific risk and recovery disclosures. It also commits to zero interface fees during the grant and characterizes the work as a public good rather than startup financing. [5]

Resolution assessment—Inference: the revision answers the scope and deliverable-definition objections more directly, but disclosures do not remove bank/provider risk, and a smaller request does not establish sustainable economics. The applicant acknowledges dependence on a settlement company and offers a second-provider study, not guaranteed replacement infrastructure. No grounded evidence found that the committee has accepted these remedies; the remaining substantive question is whether the incremental public benefit justifies the residual exposure. [5][6]

5. Relevant precedents and documented outcomes

• Zcash WalletConnect Integration — $50,000, approved. Closest comparison for a reusable wallet-to-application layer. Committee support emphasized portability beyond Noir, team capability and a reasonable budget, while acknowledging uncertain immediate demand. Startup payment and first-milestone completion are recorded; No grounded evidence found of demonstrated ecosystem adoption or independently described functional outcomes. Completion labels alone do not establish impact. [12]
• ZEX integration — $75,000, declined. Relevant to the boundary between Zcash access infrastructure and subsidizing an early-stage commercial platform. Documented rejection reasons included centralization, technology not yet operating, weak demonstrated demand, existing alternatives and unclear incremental benefit. Inference: 0xramp’s reported settlements distinguish it from an entirely unproven concept, but not yet on ZEC-specific demand. [14][6]

6. Material risks and execution considerations

• Affordability and reliability: the applicant reports approximately 4%+ above mid-market despite zero interface fees. It also describes a September provider outage affecting ZEC routes. Inference: cost and upstream reliability could constrain repeat use independently of interface quality. [6][7]
• Capacity and sustainability: two part-time founders cover engineering, security, support, documentation and outreach; the post-grant operating approach is deferred to a continuation plan. Inference: this creates delivery concentration and continuity risk. [4][7]
• Conflicts and funding overlap: Michael leads separately funded Zcash Brazil; the applicant says none of that funding flowed to 0xramp. Vini operates a NEAR validator and is a House of Stake delegate while NEAR Intents is a dependency. These are disclosed relationships, not evidence of misconduct. [7]

7. Material gaps and questions for the applicant

• What baseline ZEC volume, repeat-user activity and PAY usage can you substantiate, and what numerical outcomes would make this grant worthwhile?
• Will Zingo confirm the pilot scope, engineering availability and acceptance responsibilities before funding? What happens to M3 payment if partner delivery slips?
• What exactly does the $12,000 services/reserves allocation purchase, and how are shared costs separated from non-Zcash work?
• What security review and failure testing will precede SDK v1, and who handles or bears losses when conversion succeeds but fiat settlement fails?
• What minimum service and maintenance commitments survive week 16, under what funding model, and with what unused-fund treatment?

8. Neutral decision considerations

Inference: committee evaluation can separate three questions: whether the SDK and documentation constitute reusable public goods; whether the spending/access route creates measurable Zcash benefit; and whether the remaining financial risks are acceptable even with better disclosure.

Possible funding conditions—not an approval recommendation—include written partner acceptance, an itemized reserve budget, a pre-release security gate and reporting that separates ZEC usage from overall settlements. A narrower SDK-focused scope is another option if reusable integration value is persuasive but payment-route exposure is not.

9. Numbered source list

• [1] Grant Application - 0xramp: ZEC payments and wallet integrations (revision of #408) — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/454
• [4] Grant Application - 0xramp: ZEC payments and wallet integrations (revision of #408) — posts 1–5, part 1 — https://forum.zcashcommunity.com/t/grant-application-0xramp-zec-payments-and-wallet-integrations-revision-of-408/57892/1
• [6] Grant Application - 0xramp: ZEC payments and wallet integrations (revision of #408) — posts 1–5, part 3 — https://forum.zcashcommunity.com/t/grant-application-0xramp-zec-payments-and-wallet-integrations-revision-of-408/57892/1
• [7] Grant Application - 0xramp: ZEC payments and wallet integrations (revision of #408) — posts 1–5, part 4 — https://forum.zcashcommunity.com/t/grant-application-0xramp-zec-payments-and-wallet-integrations-revision-of-408/57892/1
• [11] 0xramp: Non-custodial ZEC ⇿ local-fiat ramp for emerging markets - decision minutes — https://forum.zcashcommunity.com/t/zcash-community-grants-meeting-minutes-9-14-2026/57615
• [5] Grant Application - 0xramp: ZEC payments and wallet integrations (revision of #408) — posts 1–5, part 2 — https://forum.zcashcommunity.com/t/grant-application-0xramp-zec-payments-and-wallet-integrations-revision-of-408/57892/1
• [12] Zcash WalletConnect Integration — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/391
• [14] {ZEX for Zcash: CEX Speed, DEX Security, Simple and Global Access to ZEC.} — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/208