Terms and Conditions
- I agree to the Grant Agreement terms if funded
- I agree to Provide KYC information if funded above $50,000 USD
- I agree to disclose conflicts of interest
- I understand that this grant program is only eligible for completed work, as it is a retroactive grant program. Applications for planned or partially completed work will not be considered. All completed work will be verified and accepted by its intended users or their representatives, who will confirm that the outputs meet the required quality, functionality, and usability before the work is listed as an option for Coinholder voting.
- 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
librustzcashstyle guides as a primary reference. - 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, branch, pull request, and commit guidelines as exemplified in the librustzcash repository.
- I understand all grants are valued in USD but will be disbursed in Shielded ZEC. I acknowledge and accept that disbursement amounts may fluctuate based on the ZEC/USD exchange rate at the time of payment.
Application Owners (@octocat, @octocat1)
@oolu4236
Organization or Individual Name
OLA (ola_olu)
Additional Team Members
N/A — sole operator
How did you learn about the Lockbox: Coinholder Retroactive Grants Program?
Zcash Community Forum — Q4 2026 CDRGP call for proposals thread
Requested Grant Amount (USD)
$9,100
Category
Media
Project Summary
The Zcash Daily is a sourced, opinionated editorial digest covering what happened in the Zcash ecosystem each day and why it matters. 50+ editions published to the Zcash forum between August 27 and November 3, 2026, with 417 inline source links, a structured log.json, and an automated publishing pipeline. Every edition is publicly verifiable. This is a retroactive request for work already completed.
Project Description
The Zcash Daily is a sourced, opinionated editorial digest covering what happened in the Zcash ecosystem each day and why it matters. Every edition draws from 8+ source channels — price action, governance debates, GitHub commits, on-chain metrics, external press — and publishes to the Zcash forum, Notion, and X. Across 10 weeks, mostly weekdays, it has built a daily public record with rotating thematic focus: community pulse early in the week, builder spotlights midweek, broader ZK ecosystem context to close it out.
This is information infrastructure. The community has funded this kind of work before — the Arborist Call note-taker role exists because someone recognized that protocol-level conversations needed a reliable, consistent communication layer between developers and coinholders. The Zcash Daily extends that logic to the full ecosystem — governance, community sentiment, builder activity, external coverage — on a daily cycle. Same category, broader scope.
ZecHub already does valuable work as a weekly education hub with its DAO model. The Zcash Daily isn't a replacement — it's a different instrument. Daily vs. weekly. Editorial voice vs. encyclopedic reference. Real-time tracking vs. macro explainers.
Major events covered during the period:
- NU7 activation countdown and Zondax/Ledger migration warnings
- ZCG governance crisis — all four competing proposals, the $455K ZSA grant controversy, ZCG taper withdrawal
- Grayscale ZCSH ETF inflow tracking (eight consecutive inflow sessions tracked in the digest)
- Zcon7 Cancun event spotlighted
- Zcash 10th birthday (October 28)
- CoinShares/Euronext ETP suspension on debut day
- Shielded pool usage tracking across the period (supply in shielded pools, transaction share trends)
- HashSmash launch, ROZO shielded payments, Kestrel WalletConnect, 10-second block spacing ZIP
Technical Approach (how you did it)
I designed the editorial system: the voice, format rules, source methodology and themed calendar. Claude drafts from that system. I review, correct, decide what publishes, and write it myself when the draft doesn't meet the bar.
A typical day is 45 minutes to an hour of editorial work. Early sessions ran longer while I built the framework, and heavy news days took more. Across the full run, that averages about 1.5 hours per digest.
Automation handles the publishing mechanics, so my time goes to editorial decisions.
The publishing pipeline is at github.com/oolu4236/zcash-digest:
- GitHub Actions automated workflow (daily + manual dispatch)
- Claude API integration for generation assistance and fact-checking
- Automated link verification (HEAD requests to all inline URLs)
- Notion API integration (child pages with rich text and hyperlinks)
- Twitter/X OAuth 1.0a integration (automated tweet condensing and posting)
- Structured log.json tracking every published digest
- Batch tweet backfill system for missed posts
- Format validation (char counts, link counts, paragraph structure)
Time Period of Work Completion
August 27, 2026 – November 3, 2026
Total Budget (USD)
$9,100
Budget Breakdown
- Compensation:
- $(USD): 5,625
- Justification: Editorial work: 50 digests x 1.5 hrs avg x $75/hr ($112.50/digest). Designing the voice and format system, scanning 8+ source channels, verifying facts against primary sources, reviewing and correcting Claude's drafts, deciding what publishes. Early sessions were longer (building the editorial framework); later ones shorter (45 min – 1 hr). Average across the full run: 1.5 hours per digest including building the editorial framework. The automation handles publishing mechanics — the paid hours go to editorial judgment.
- Technology/Software:
- $(USD): 475
- Justification: API costs (Anthropic, X/Twitter)
- Infrastructure/Hosting:
- $(USD): 0
- Justification: GitHub Pages hosting (free)
- Services/Contractors:
- $(USD): 0
- Justification: N/A, sole operator
- Other:
- $(USD): 3,000
- Justification: Publishing pipeline development (~40 hrs x $75/hr)
- Total $(USD): 9,100
Previous Funding
No
Previous Funding Details
No response
Other Funding Sources
Yes
Other Funding Sources Details
I moderated engineering meetings for ZingoLabs' Zaino team, which receives ZCG funding. That role was entirely separate from The Zcash Daily — different project, different scope, different deliverables. No ZCG or ecosystem funds have been used for the digest. All costs to date have been self-funded.
Success Metrics
All independently verifiable:
- 50+ digests posted to the Zcash forum across 10 weeks (Aug 27 – Nov 3, 2026)
- 417 inline source links across all editions (avg 7.0 per digest)
- 114 links driving attention back to Zcash forum threads
- 58 links to X/Twitter ecosystem posts
- 35 links to GitHub PRs and repos
- 33 tweets posted to @thezcashdaily
- 40+ Notion pages as searchable archive
- 15–31 unique daily views on the forum thread, peaking during high-signal events (NU7, ZCG crisis)
Per-unit cost: $9,100 / 50 digests = $182/digest.
Proof of completion
Every claim is independently auditable:
- Repository/Commit:
- oolu4236/zcash-digest - source code, GitHub Actions workflow, log.json with all entries. Tagged snapshot: cdrgp-v1
- Publication:
- log.json - structured record of every digest: date, full HTML content, Notion page ID, tweet ID
- Forum thread: The Zcash Daily - 50+ editions posted with community engagement visible
- Deployment/Release:
- @thezcashdaily - 33 tweets with digest summaries and forum links
- Notion archive: 40+ pages accessible via Notion page IDs in log.json
- Other Evidence:
- GitHub Actions runs - workflow history
Conflict of Interest Disclosure
I hold ZEC. I moderated engineering meetings for the Zaino team at ZingoLabs (ZCG-funded). The Zcash Daily is an independent project with no connection to that work. Editorial coverage of ZingoLabs in the digest is held to the same sourcing standard as every other ecosystem project.
Community Forum Posting
- I understand it is my responsibility to post a link to this issue on the Zcash Community Forums after this application has been submitted so the community can give input. I understand this is required in order for the community to discuss and vote on this grant application. Note: If you are unable to post on the forum (for example, due to new user restrictions), please leave a comment below, and we will adjust your posting permissions.