ZECsy Community Building: 12 Months of Zcash on the Ground [Revised]

1. Executive summary and decision snapshot

The ZECsy Team requests $550,000 for a revised 12-month community-outreach program intended to place Zcash educators and ambassadors at crypto/technology events, adult-industry events, and recurring privacy workshops. The applicant is Mylo Bennett (“ReadyMouse”), working with lead educator Violet/“fabacab,” community connector Molly Simmons, demonstration developer Zach M., and rotating veterans and apprentices. [1][5][6]

The revised proposal shifts emphasis toward adult-industry outreach: 4 crypto/tech events, 5 adult-industry activations, and 8 weekend workshops. It also adds a small stipend for participation in a Zcash-focused event and reduces the request from the prior $588,000 proposal to $550,000. [10][13]

Funding is proposed as one startup payment followed by 11 monthly payments, each conditional on the preceding month’s work and forum report. [6]

Decision snapshot: The strongest case is a team with firsthand supporter testimony, a previously approved $30,000 ZCG activation, demonstrated in-person event experience, and access to communities facing privacy and debanking concerns. [7][9][14] The principal decision issue is value-for-money and verifiability: the program proposes a large annual field budget, flexible rather than fixed event selection, and privacy-preserving aggregate reporting that will not measure participant-level retention or longer-term adoption. [5][9][10]

2. Applicant and team track record

Mylo Bennett is presented as the full-time program lead responsible for calendar management, budget, logistics, partnerships, outreach strategy, and reporting. Violet/“fabacab” leads workshop curriculum, technical education, developer relations, and apprentice mentorship. The proposal also identifies Molly Simmons for community connection and workshop recruitment, Zach M. for a point-of-sale demonstration, and rotating field staff. [1][5][6]

The team reports prior ZCG-funded and community-funded work at Devconnect Buenos Aires, ETHBoulder/ETHDenver, ETHCC Cannes, Exxxotica Chicago, Berlin Blockchain Week, and DWeb Camp. It reports that six workshops reached more than 100 participants from sex-worker, gig-worker, and LGBTQIA+ communities. These are applicant-reported accomplishments; outcome documentation beyond the supplied statements is limited. [1][6][13]

The most concrete reported event result is the Berlin “Zcash Privacy Späti,” said to have drawn 912 unique attendees. The team also reports that more than 600 people visited its Exxxotica Chicago booth over three days. [6]

A prior $30,000 proposal for the team’s Cypherpunk Week Amsterdam activation was approved in July 2026. Committee members cited favorable feedback from prior events, engagement, perceived traction with high-potential users, and the team’s performance to date. Approval is evidence of prior committee confidence, not proof that the Amsterdam activation has delivered outcomes. [14]

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

The proposed program runs from September 2026 through August 2027 and combines event booths or activations, workshops, relationship-building, user onboarding, and apprenticeship training. The revised annual mix is four crypto/tech events, five adult-industry events, and eight weekend workshops. [4][10]

The field model uses a four-person crew at major activations: lead, lead educator, veteran, and apprentice. Workshops use a smaller crew. The apprentice model aims to turn prior participants or community members into capable field educators over time. [4][6]

The technical-education component covers self-custody wallets and a broader privacy-tool curriculum including password managers, Tor, Signal, and off-ramping options. Zach M. is expected to expand the CipherPay iPad demonstration into a merchant point-of-sale flow. [6][10]

The team proposes selecting individual events about 90 days in advance based on cost, speaking or booth acceptance, and audience fit. This gives flexibility but leaves final annual venues and per-event commitments unspecified. [5]

Budget evidence is limited in the supplied record. The applicant states that a line-item workbook exists and that the total was reduced from $588,000 to $550,000, but the actual line items, payment amounts, and milestone acceptance criteria are not included here. [6][10][13]

4. Community discussion, arguments, responses, and resolution

Strongest arguments for: Multiple commenters with claimed firsthand exposure endorse the team’s ability to attract attention, teach users, collect field feedback, and build relationships in communities that may have practical privacy needs. CipherPay’s developer states the team has used its point-of-sale demonstration in the field and supplied a meaningful user-to-builder feedback loop. [7][9] Supporters particularly value sustained post-workshop support and outreach to adult-industry communities affected by debanking. [8][10]

Strongest arguments against or unresolved: The material concern raised was whether reported onboarding can distinguish wallet installation, first shielded transactions, and follow-up engagement. This matters because the grant’s value proposition rests on durable adoption rather than event attendance. [9]

Applicant response: The team explicitly declined longitudinal participant tracking, reasoning that linking people’s wallet creation, transactions, and later support-channel activity would conflict with the privacy principles being taught. It instead commits to aggregate, in-the-moment counts: attendance, wallets installed during hands-on onboarding, in-workshop transactions, apprentices trained, and publicly declared merchant acceptance where the team made an introduction. [9]

Resolution: The commenter who raised the measurement concern accepted the privacy rationale and aggregate approach. [10] Remaining disagreement: No disagreement is recorded after that exchange, but aggregate measures cannot establish participant retention or sustained Zcash use; this is an evidence limitation, not a demonstrated program failure.

5. Relevant precedents and documented outcomes

ZECsy Team in Amsterdam — approved, $30,000. This is the closest precedent because it funds the same team’s in-person, community-specific Zcash outreach. The committee approved it based on positive feedback and engagement from prior events, perceived traction, and the team’s prior performance. No post-grant delivery or impact evidence is supplied. [14]

ZecHub 2026 — approved, $419,361. This is relevant as a substantial ecosystem education and engagement grant. The committee described ZecHub as having onboarded 232 contributors and delivered education, events, partnerships, and communication over three years; it considered ZecHub a visible and valued ecosystem contributor. The comparison supports the relevance of sustained education/community work, while ZECsy differs by emphasizing physical outreach and higher-cost travel activations. [16]

Nesthub for Zcash Developers — declined, $9,600. This is relevant because it was an in-person education/events proposal. The committee questioned whether generic developer hubs were an effective Zcash-growth format, found the three-month budget potentially unrealistic for feasible impact, and said stronger proof of prior event organizing would improve a future request. ZECsy offers more event experience, but the precedent underscores the need to establish format-specific impact and credible delivery economics. [17]

6. Material risks and execution considerations

• Budget and scale risk: At $550,000, this is materially larger than the team’s documented prior approved $30,000 activation. Evidence provided does not show a full cost breakdown or how funds divide among staffing, travel, booths, workshops, merchandise, and the POS work. [10][14]
• Flexible calendar risk: Event choices remain provisional and depend on future costs and acceptance decisions. This could improve responsiveness but complicates advance assessment of audience quality, duplication, and per-event value. [5]
• Impact-measurement limit: The privacy-preserving reporting design can demonstrate activity and immediate onboarding, but not durable individual adoption or retention. [9][10]
• Delivery dependency: Event access, speaker or booth acceptance, venues, travel, local partners, and merchant or wallet ecosystem collaboration can all affect outcomes; the proposal identifies these selection factors but does not document commitments for the revised schedule. [5]
• Inference: The adult-industry emphasis may provide differentiated outreach, but concentrating five major activations in one sector increases the importance of clear event-specific objectives and safeguards for measuring value across a diverse annual portfolio. [10]

7. Material gaps and questions for the applicant

1. Provide the revised line-item budget and the amount requested for startup funding and each of the 11 monthly milestones; reconcile these explicitly to $550,000.
2. Define objective acceptance criteria for each monthly milestone beyond submission of a report—for example, required event/workshop delivery, spend documentation, and minimum reporting contents.
3. Identify the planned allocation of funds and team time among crypto events, adult-industry events, workshops, the flagship activation, and the POS demonstration.
4. For each event category, state the decision criteria, target audience, expected onboarding activity, and circumstances under which an event would be substituted or cancelled.
5. Specify how aggregate metrics will be consistently counted and independently reviewable without collecting participant-level data.
6. Clarify the expected deliverables, ownership, maintenance responsibility, and user-validation plan for the CipherPay merchant-flow demonstration.
7. Explain what evidence from prior ZECsy activations supports the claimed relationship between attendance, wallet onboarding, merchant engagement, and longer-term community value.

8. Neutral decision considerations

Committee members may weigh whether the proposal’s differentiated access to privacy-sensitive and potentially underserved communities justifies a year-long, travel-intensive field program. Supporter testimony and the team’s prior approval provide meaningful confidence in capability and community fit. [7][9][14]

The central trade-off is between privacy-respecting reporting and rigorous attribution of lasting adoption. The applicant’s aggregate approach is aligned with its stated educational principles, but it limits the committee’s ability to assess retention, repeated use, or cost per sustained user. [9][10]

Possible funding conditions for discussion could center on a complete revised budget, measurable monthly acceptance criteria, event-selection controls, transparent aggregate reporting, and defined technical deliverables for the POS component. These considerations support structured evaluation; they do not determine an automatic approval or rejection.

9. Numbered source list

• [1] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground Revised — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/402
• [5] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 1–5, part 2 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/1
• [6] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 1–5, part 3 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/1
• [10] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 16–20 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/16
• [13] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/383
• [7] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 1–5, part 4 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/2
• [9] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 11–15 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/11
• [14] ZECsy Team in Amsterdam - decision minutes — https://forum.zcashcommunity.com/t/zcash-community-grants-zcg-meeting-minutes-7-20-2026/56763
• [4] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 1–5, part 1 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/1
• [8] Grant Application - ZECsy Community Building: 12 Months of Zcash on the Ground — posts 6–10 — https://forum.zcashcommunity.com/t/grant-application-zecsy-community-building-12-months-of-zcash-on-the-ground/56890/6
• [16] ZecHub 2026 — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/153
• [17] Nesthub for Zcash Developers — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/141