Zcash Privacy Ecosystem Mapping & Adoption Data

1. Executive summary and decision snapshot

Web3Privacy Now requests $5,000 for Zcash wallet measurements, reproducible shielded-adoption data, an ecosystem-map refresh, and a written case study. Lead researcher jensei and designer Talia would deliver the work. The applicant requests one payment rather than tranches, with outputs published together alongside a report targeting 2 November 2026. [1][4]

The strongest capability evidence is the applicant’s reported prior mapping and privacy research, supplemented by a collaborator’s endorsement. Evaluation inference: the central decision is whether this becomes reusable, independently checkable research—not merely another publication. Methodological credibility, standalone delivery, and acceptance conditions matter most. The September 28 committee minutes leave the request open. [4][6][9]

2. Applicant and team track record

• jensei: identified as a Web3Privacy Now core contributor and lead author of the State of Decentralized Privacy 2026 report; responsible for research design, verification, adoption methodology, analysis, publication, and reporting. Talia: responsible for visualization and layouts; the application cites prior work on the summit report, event design, and Walletbeat’s redesign. These are applicant-reported credentials. [1]
• Relevant prior work: the applicant reports publishing a 128-project Zcash map in April, updating it in August, and publishing a June report covering 826 privacy projects. These are concrete claimed outputs, but the supplied evidence does not independently establish their accuracy, readership, or practical impact. [4]
• External support: Mf recommends jensei based on previous collaboration, without specifying deliverables or measured results. For prior ZCG-funded delivery performance: No grounded evidence found; this does not establish that no prior grants exist. [6]

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

Planned outputs:

• Real-device, real-fund wallet testing: time to first shielded transaction, proof-generation time, sync behavior, and errors; at least three repetitions per measurement, publishing raw timings rather than medians alone. [4]
• Reproducible derivation of shielded adoption and standalone open Zcash datasets; committee minutes describe the datasets as CC BY 4.0. [1][9]
• A CC BY 4.0 case study, including Orchard-related analysis, and re-verification of 128 map entries against repository activity and website availability, incorporating corrections such as Gem Wallet. [4]

Funding and milestones: $5,000 represents approximately 23% of a $21,500 research programme. The applicant says the remaining approximately $16,500 “is raised from other supporters” and argues parallel research and joint publication make tranching disproportionate. Payment timing is not specified in the supplied text. For itemized costs, effort estimates, formal acceptance milestones, or completed deliverables under this request: No grounded evidence found. [4]

Dependencies: the November publication target is tied to Ethereum Cypherpunk Congress. Testing requires devices, funded wallets, and usable infrastructure. ZecHub is a prospective publication destination, not a demonstrated maintenance commitment. [4][5]

4. Community discussion, arguments, responses, and resolution

Strongest case for: the applicant proposes replacing acknowledged desk-research gaps with live measurements and reusable evidence. It argues that cross-ecosystem comparison can reach builders, journalists, and policymakers beyond Zcash. ZecHub offers a research-page destination; a previous collaborator endorses the lead. Reach remains an applicant argument, not a documented outcome. [4][5][6]

Strongest countercase—evaluation inference, not a recorded objection: existing ZecHub supply visualization and Orchard coverage make additionality important. New measurements and reproducibility would offer a clearer distinction than parallel explanatory material. [5]

Responses and resolution:

• On overlap, jensei says he would rather cite ZecHub’s Orchard series and cover what it does not address. This acknowledges duplication risk but does not establish a final division of scope. [5]
• LowKey asks for evaluation of slow-sync messages and recovery guidance. jensei agrees to try to include this; the response is constructive but not a firm test requirement. [5]
• ZecHub suggests DAO funding; jensei expresses interest in exploring it. No funding arrangement is documented. [5]

For an explicit opposing position or substantive committee disagreement on this request: No grounded evidence found. The recorded committee outcome is only “Remains open.” [9]

5. Relevant precedents and documented outcomes

• Zcash in the privacy stack — $5,000, approved: the closest comparison by price and cross-ecosystem research framing. The committee accepted a reduced, standalone pilot after concerns about cost, Zcash relevance, and readership. Two milestones are recorded complete, but readership or ecosystem impact is not documented. Inference: bounded scope and demonstrable Zcash relevance matter more than broad publication ambitions. [11]
• Zcash Privacy Academy — $7,000, declined: relevant to the publication component. The committee cited overlap with ZecHub, insufficient audience justification, and weak additional value from more theoretical material. Inference: original wallet measurements distinguish this request, but dissemination and reuse still need a credible case. [12]

6. Material risks and execution considerations

• Causal overstatement: the applicant attributes a reported rise in shielded supply—from roughly 8% to 30%—to default-on wallets. Inference: reproducing that trend would not alone establish causation or show how many people adopted shielded payments. The research should distinguish supply concentration, usage, and causal attribution. [4]
• Measurement validity: three repetitions and raw timings improve inspectability. Inference: generalizable findings still depend on device selection, wallet versions, network conditions, clean-state procedures, and clear definitions of proof time versus total transaction time. [4]
• Independence: the applicant discloses Zcash event support and annual membership, promises funders no influence over conclusions, and limits stated AI use to drafting and code assistance. Inference: transparent methods and publication of unfavorable findings would help substantiate independence; disclosures alone do not establish it. [4]

7. Material gaps and questions for the applicant

• Delivery accountability: What exact artifacts trigger acceptance and the single payment, who validates them, and what happens if the November launch slips? [1][4]
• Cost and standalone viability: How is the $5,000 allocated, are other supporter funds committed, and can all Zcash deliverables ship if the broader programme is delayed or underfunded? [4]
• Testing design: Which wallets, devices, operating systems, and test conditions will be covered? How will repeated tests preserve the claimed first-use perspective, and will stalled-sync recovery be mandatory? [4][5]
• Adoption methodology: What sources, formulas, and executable materials will reproduce the shielded-supply series, and which conclusions about users or default-driven behavior can the evidence actually support? [1][4]
• Incremental value and ownership: What is genuinely new relative to existing ZecHub work, who will maintain the map, and which intended users will validate or reuse the outputs? [4][5]

8. Neutral decision considerations

Evaluation inference: a bounded research award is more compelling if it purchases auditable measurements and transferable datasets rather than requiring confidence in the applicant’s preferred narrative. The proposal’s open-output commitments and modest requested amount support that framing; the unresolved questions determine whether it is achievable. [4][9]

Committee options include accepting the single-payment model with explicit acceptance conditions, negotiating deliverable-linked payment, or seeking methodological and funding clarification before deciding. The relevant precedents support judging incremental utility, scope, and audience—not treating either approval or milestone labels as proof of impact. [11][12]

9. Numbered source list

• [1] Grant Application - Zcash Privacy Ecosystem Mapping & Adoption Data — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/448
• [4] Grant Application - Zcash Privacy Ecosystem Mapping & Adoption Data — posts 1–5, part 1 — https://forum.zcashcommunity.com/t/grant-application-zcash-privacy-ecosystem-mapping-adoption-data/57843/1
• [6] Grant Application - Zcash Privacy Ecosystem Mapping & Adoption Data — posts 6–10 — https://forum.zcashcommunity.com/t/grant-application-zcash-privacy-ecosystem-mapping-adoption-data/57843/7
• [9] Zcash Community Grants (ZCG) Meeting Minutes 9/28/2026 — posts 1–5, part 12 — https://forum.zcashcommunity.com/t/zcash-community-grants-zcg-meeting-minutes-9-28-2026/57928/2
• [5] Grant Application - Zcash Privacy Ecosystem Mapping & Adoption Data — posts 1–5, part 2 — https://forum.zcashcommunity.com/t/grant-application-zcash-privacy-ecosystem-mapping-adoption-data/57843/2
• [11] Zcash in the privacy stack — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/339
• [12] Grant Application: Development of the “Zcash Privacy Academy” Course — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/20