Zcash Early Builders Lab (ZEBL) Cape Town

1. Executive summary and decision snapshot

Request: ZEBL Cape Town seeks $47,300 for a three-month youth developer initiative: a two-day workshop and mini-hackathon, followed by a 30-day virtual cohort for 80+ participants aged 16–22. The application is under review. Delivery would be led by educator Thabo Makoena, with technical, logistics, media, safeguarding, and retention roles. [1][4]

The reported funding schedule comprises $19,000, $18,300, and $10,000; its treatment of startup funding is disputed below. [5]

Decision focus—inference: The strongest capability signal is the proposed division of educational and technical responsibilities, rather than demonstrated delivery. Funding confidence turns principally on a coherent budget, credible recruitment and technical preparation, and evidence that workshop activity can become sustained contribution. [1][4][5]

2. Applicant and team track record

The applicant describes Makoena as a teacher experienced in curriculum and student engagement; Sipho Dlamini as a senior blockchain developer with Rust/Go and SDK experience; and Nomda Nkosi as an experienced event planner. Johannes van der Merwe would document the event, Mercy Murife would oversee youth safeguarding, and Lerato Molefe is named for retention and outreach. These are applicant-supplied qualifications. [1]

The team claims an active presence and track record in South Africa’s technology ecosystem. No grounded evidence found for named previous projects, independently corroborated qualifications, prior ZCG delivery, or measured recruitment and retention outcomes. This does not establish that no prior grants or experience exist. [1][4]

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

• Learning and outputs: Testnet wallet setup, zero-knowledge concepts, shielded transactions, prototype applications, and a reusable MIT-licensed curriculum repository. Targets include 60+ connected testnet wallets, 150+ shielded transactions with encrypted memos, and 10+ student repositories containing working prototypes. [4]
• Technical approach: Exercises are proposed exclusively on Zcash testnet, using lightwalletd connectivity. The technical mentor would configure ZODL/YWallet environments, manage testnet faucets, and review student code. These are plans, not demonstrated integrations. [1][4]
• Retention: The “Young Builders Circle” would track code commits during a 30-day follow-up period; no numerical retained-contributor target is supplied. [4]
• Funding and milestones: The three amounts reported in discussion total $47,300. No grounded evidence found for a complete milestone-to-deliverable schedule, payment dates, or milestone-specific acceptance tests. The application accepts intended-user validation in principle. [1][5]
• Dependencies: Proposed responsibilities encompass school/STEM outreach, venue and connectivity, transport, equipment, parental consent, and mentor preparation. Inference: These require confirmation before attendance and technical-delivery targets can be treated as credible commitments. [1]

4. Community discussion, arguments, responses, and resolution

Strongest case for funding: The applicant proposes hands-on development rather than awareness alone, reusable educational materials, and follow-up beyond the event. One community participant praised the proposal’s preparation, but supplied no additional delivery evidence. [4]

Strongest documented objection: A reviewer identified three financial inconsistencies:

• Startup funding of $19,000 appeared both separately and as Milestone 1, potentially implying $66,300 rather than $47,300.
• Hardware, services, and stated compensation totaled $41,300; prizes and transport subsidies were mentioned but omitted from cost lines.
• Compensation line items allegedly totaled $32,200, not the stated $33,200. [5]

Applicant response: Makoena thanked the reviewer and promised a correction. No corrected budget is supplied, so none of these concerns can be treated as resolved. The remaining issue is the payable total and allocation—not evidence of a broader community rejection of the concept. [6]

5. Relevant precedents and documented outcomes

ZecHub—open-source education: ZCG approved $50,000 for five months in November 2023. Committee members cited tangible output, demonstrated work, and net benefit. This is relevant because it connects education funding to established public deliverables. The documented evidence is the committee’s assessment of existing work; No grounded evidence found for subsequent quantified learning or retention outcomes from that award. Inference: It supports asking ZEBL for demonstrable curriculum and technical work, not assuming comparable capability from a similar funding amount. [9]

Zcash East Africa Kampala Meetup—local education and events: The $1,000 request was declined in September 2025. The committee stated it could support funding where a meetup demonstrably attracted a broad audience and provided high-quality feedback, including metrics, photos, testimonials, and a post-event report. This is relevant to ZEBL’s recruitment and outcome-reporting obligations, though not a like-for-like budget benchmark. Inference: Reporting expectations should preserve those accountability goals while accounting for ZEBL’s minor participants. [11]

6. Material risks and execution considerations

• Activity versus impact—inference: Wallets, transactions, and repositories can demonstrate participation without demonstrating independent developer capability. Commit tracking needs a substantive quality threshold to support the claimed sustainable developer pipeline. [4]
• Teaching breadth—inference: The combination of school and university participants, wallet setup, cryptography concepts, and prototype development within two event days creates curriculum and mentor-capacity risk. [4]
• Safeguarding and privacy—inference: Youth participation alongside photography, video, public repositories, and activity tracking requires coordinated consent and publication safeguards. Testnet-only exercises do not address these nonfinancial risks. [1][4]
• Value sensitivity—calculation: At the minimum target of 80 participants, the request is approximately $591 per participant. This is not a retained-developer cost and would fall with higher attendance; evaluation should consider reusable curriculum value alongside participant outcomes. [1][4]

7. Material gaps and questions for the applicant

• Funding certainty: What is the corrected, exhaustive $47,300 budget, including startup treatment, compensation arithmetic, prizes, transport, rates, and staff time?
• Payment conditions: Which deliverables unlock each payment, who accepts them, and what happens if recruitment or event delivery falls short?
• Capability: What prior workshops, curricula, technical repositories, and references substantiate the team’s stated qualifications?
• Recruitment readiness: Which schools or universities have committed participants, and what are the selection criteria, prerequisite skills, mentor ratio, and device-access arrangements?
• Technical readiness: Can the team demonstrate the complete wallet, faucet, lightwalletd, and prototype exercise before participant onboarding?
• Durable outcomes: What minimum number of participants must remain substantively active after 30 days, how will independent work be distinguished from copied exercises, and who maintains the curriculum afterward?
• Youth protection: What consent, supervision, incident-response, and data-publication rules govern minors, including photographs and public GitHub activity?

8. Neutral decision considerations

Committee judgment options, not a funding recommendation:

• Distinguish educational value, reusable public goods, and sustained developer contribution; establish which outcome principally justifies expenditure.
• Consider whether a smaller preparation or pilot tranche would provide useful evidence before committing event-scale funding.
• If considering the full scope, use observable acceptance conditions: tested curriculum, confirmed recruitment, working exercises, reviewed prototypes, and defined follow-up results.
• Assess corrected compensation against disclosed effort and responsibilities, rather than headline budget comparisons alone.
• Preserve a meaningful outcome-linked payment while balancing the applicant’s documented need for advance commitments.

9. Numbered source list

• [1] Grant Application - Zcash Early Builders Lab (ZEBL) Cape Town — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/493
• [4] Zcash Early Builders Lab (ZEBL) Cape Town — posts 1–5 — https://forum.zcashcommunity.com/t/zcash-early-builders-lab-zebl-cape-town/58204/1
• [5] Comment on #493: Grant Application - Zcash Early Builders Lab (ZEBL) Cape Town — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/493#issuecomment-6177545653
• [6] Comment on #493: Grant Application - Zcash Early Builders Lab (ZEBL) Cape Town — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/493#issuecomment-6177920715
• [9] ZecHub, An open source education hub for Zcash — comparison summary — https://forum.zcashcommunity.com/t/zcash-community-grants-meeting-minutes-11-27-2023/46186
• [11] {Zcash East Africa Kampala Meetup} — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/79