Application Owners
@Emilio983
Organization Details
Organization Name: The Social Mask
How did you learn about ZCG?
Through Zcash Community Forum while researching privacy payment solutions for our Social Mask project. During our investigation in October 2025, we studied BTCPay Server’s shielded transaction support and realized there was a critical gap in the ecosystem: no solution existed that combined easy setup with privacy-preserving shielded transactions.
Project Overview
Requested Grant Amount: $24,500 USD (MVP) — Up to $35,500 USD with optional enhancements
Category: Infrastructure
Team Information
Project Lead: Emilio Navarro Mejía
Role: Lead Developer & Project Architect
Background: Founder of NordClip.com and Nortedu.com with specialized experience in privacy technologies, Web3 integration, and zero-knowledge proof systems. Previously presented the Social Mask decentralized social network proposal to ZCG, which highlighted the need for robust Zcash payment infrastructure.
Responsibilities: Leading all technical development including WebZjs integration, plugin architecture design, security implementation, API development, documentation creation, and coordination with ChainSafe for WebZjs support.
Additional Team Members:
- Name: Oswaldo Navarro
Role: Finance & Legal Manager
Background: 15+ years of experience in accounting and financial management. Official legal representative with government credentials and regulatory compliance expertise.
Responsibilities: Managing project budget and milestone payments, ensuring legal compliance, handling vendor contracts, maintaining financial records, and coordinating KYC requirements with ZCG.
Project Details
Project Summary
Unlike checkout-oriented stacks that require Docker or custom services, our shielded-by-default toolkit runs even on cheap PHP-only shared hosting, so non-technical WordPress sites can enable rotating z-address tips/PayLinks in minutes—no custody, no third parties. For teams that later move to a VPS, the same plugin can point to a hardened verify endpoint, but MVP does not require it.
We are building lightweight open-source payment modules for WordPress and Ghost/HTML that enable shielded Zcash transactions with setup in minutes. This is the first solution combining ease of use with privacy-preserving shielded transactions, addressing the critical problem forcing users to choose between convenience or privacy. Includes per-post tips, PayLinks, Donate Banner, and Web Terminal for in-person payments.
Project Description
Today only 20% of ZEC exists in shielded pools because existing infrastructure forces an impossible choice: easy but transparent (NOWPayments, Plisio) or private but complex (BTCPay, ZGo requiring Docker and full nodes). This suppresses adoption among content creators and small businesses who lack technical expertise.
We’re building reusable payment infrastructure that extends beyond these modules. Consider our previous Social Mask proposal—you found it interesting but challenging in scope. With this infrastructure, projects like Social Mask become feasible because the payment layer will exist as battle-tested, open-source code. Any developer building Zcash applications can integrate shielded payments without becoming blockchain infrastructure specialists.
Our technical approach leverages WebZjs by ChainSafe (Hacken audited, powers MetaMask Zcash Snap). WebZjs enables browser shielded transactions via WebAssembly without full nodes. We use viewing key architecture where spending keys stay in user wallets—even if websites are compromised, funds remain secure. Requirements are minimal: modern browser, 5 minutes setup.
This infrastructure-first development means every hour we spend hardening payment code is an hour future developers won’t spend. The community has been explicit about this need: “If they can’t integrate ZEC easily… they simply won’t bother.” ZCG’s preference for focused $20-30K proposals aligns perfectly with this targeted infrastructure investment.
Proposed Problem
Current Zcash payment infrastructure forces a false choice: easy but transparent (defeating privacy) or private but technically complex (excluding non-technical users). This suppresses shielded adoption—only 20% of ZEC in shielded pools—and prevents Zcash from reaching content creators and small businesses.
Existing solutions either require technical expertise (Docker, full nodes) or only support transparent addresses. Community frustration is explicit: “If they can’t integrate ZEC easily… they simply won’t bother.” ZCG’s preference for focused $20-30K proposals confirms targeted infrastructure investments deliver better value.
Proposed Solution
MVP Modules (WordPress + Ghost/HTML sharing secure infrastructure):
- Per-post tips: Inline donation buttons on posts/articles
- PayLinks: Shareable payment URLs for social media/email
- Donate Banner: Persistent site-wide donation widget
- Web Terminal (basic): QR code generator for in-person payments
All modules feature automatic z-address rotation (privacy by default), Full Viewing Key (FVK) verification for read-only transaction monitoring, and sub-5-minute setup. No WooCommerce/subscriptions complexity in MVP—focused on tips and donations.
Key Advantages:
- Runs on cheap PHP-only shared hosting (WordPress) with client-side shielded logic and FVK-based verification—no Docker/Node required for MVP
- Non-custodial: Spending keys never touch servers
- No vendor lock-in: Open-source MIT license
- Embeddable CDN widget for any site (works in Ghost, Substack posts via embed, or any HTML)
Shared-Hosting (PHP-only) Compatibility:
A key advantage of our approach is that it runs on cheap shared hosting plans that only support PHP, which is what many WordPress sites already use. The plugin renders the UI in WordPress/PHP and performs shielded operations client-side with a lightweight JS layer, while verification uses a Full Viewing Key (read-only). This means:
- No Node/Docker requirement for the MVP
- No spending keys ever touch the server; FVK can be stored encrypted or provided on demand
- Site owners on $5-10/month shared hosting can still enable rotating z-addresses and receive tips/donations privately
- If/when a team upgrades to a VPS, the same plugin can point to a serverless/VPS verify endpoint with rate-limiting and monitoring
Why this matters versus other options:
ZGo and BTCPay are excellent for full checkout stacks, but typically require more control over the host (Docker, services, or Node), which shared hosting plans generally don’t allow. NOWPayments is easy but custodial and adds vendor lock-in. Our toolkit fills the gap for content sites on budget hosting that still want shielded-by-default payments.
Optional Enhancements (if “up to” budget activated):
- 12-month VPS hosting + monitoring/backups (not required for MVP—shared hosting works)
- External security audit (lightweight, $2,500-3,000 focused on FVK architecture & payment flows)
- Extended tutorials and onboarding materials
- Marketing assets (comparison table, social graphics)
Roadmap (Phase 2 - Beyond Grant Scope):
- WooCommerce integration for e-commerce checkout
- Recurring subscriptions support
- Advanced analytics dashboard
- Multi-currency fiat display
The real value is proving shielded payments can be dead-simple for content creators, journalists, and activists who need financial privacy. Our viewing key architecture means spending keys never touch servers—even if a site is compromised, funds stay secure. Requirements: modern browser, 2-3 clicks, 5 minutes.
Solution Format
Distribution Channels:
The WordPress plugin will be submitted to WordPress.org’s official plugin directory, making it discoverable to millions of WordPress users. The Ghost/HTML widgets will be published to npm and hosted on CDN. The embeddable CDN widget works in any site including Ghost themes and Substack posts via embed code (not an official Substack plugin).
Documentation & Support:
Comprehensive documentation including installation guides for shared hosting (PHP-only), troubleshooting steps, API references, and video tutorials. The video tutorials are particularly important because they allow content creators to see the entire process from start to finish, reducing the barrier to adoption.
Open Source:
All code released as MIT-licensed open-source library, available through both npm and CDN. We’ll maintain greater than 80% test coverage across all code, with particular emphasis on security-critical paths.
Community Engagement:
Support forum and monthly updates to Zcash Community Forum for at least 12 months after launch. Early adopters have clear channel for questions and wider community can track project impact.
Positioning & Complementarity
Our proposal focuses on tips and direct payments with privacy by default (rotating z-addresses + FVK verification), designed for content sites and non-developers with installation in minutes. Custodial payment processors are excellent for general-purpose integrations and off-ramp, and self-hosted e-commerce solutions (e.g., store-oriented stacks) are ideal for full checkout. This toolkit doesn’t compete with those use cases: it complements them by focusing on per-post/per-author tips, PayLinks, Donate Banner, and a basic Web Terminal, without third parties or custody.
Comparison Table:
| Aspect | This Project (Shielded Payments Toolkit) | ZGo | BTCPay + Zcash | NOWPayments |
|---|---|---|---|---|
| Custody / third party | No (non-custodial) | No | No | Yes (custodial account) |
| Shielded by default (z-addresses w/ rotation) | Yes (default) | Yes (depends on setup) | Yes (depends on plugin/config) | Unclear / typically transparent |
| Verification without spending keys | Yes (FVK read-only) | Possible (varies) | Possible (varies) | N/A (their dashboard) |
| Setup target | Minutes, no-devs | Technical | Technical (Docker) | Easy, but third party |
| Hosting requirement | Works on cheap PHP-only shared hosting (WP plugin + JS) or serverless/VPS | Typically needs more control (Node/services) | Needs Docker/compose & full access | SaaS (no hosting hassle) |
| Primary use case | Per-post tips, PayLinks, Donate Banner, basic QR terminal | Store/checkout | Store/checkout | General payments, off-ramp |
| Who it’s for | Creators, media, NGOs (non-technical) | Teams with infra | Teams with infra | Merchants ok with custody |
| Vendor lock-in | None (open-source) | Low | Low | High (provider account) |
| Ongoing cost | Near-zero on shared hosting; optional VPS | Server costs | Server costs (heavier) | Processing fees |
| Privacy posture | Privacy by default (rotating z + FVK) | Good if tuned | Good if tuned | Mixed (custodial policies) |
Dependencies
The project’s primary technical dependency is WebZjs by ChainSafe, which is production-ready and actively maintained. WebZjs has undergone professional security audits and is already being used in the MetaMask Zcash Snap, so we have confidence in its stability. We’ll be using public lightwalletd servers for transaction verification, with built-in failover logic to handle potential downtime of individual servers.
For development infrastructure, we’re using standard tools that don’t introduce significant risk: GitHub for source control, npm for package distribution, and VPS hosting for documentation and monitoring. We’ll use continuous integration with automated testing to catch issues before they reach users.
The project has no dependencies on other funding sources. ZCG is the sole funding for this project, which means ZCG can have full confidence that milestones will be delivered as specified without waiting for coordination with other funders.
We are not forking or depending on any other grant proposals currently in progress. This is a standalone project with clear deliverables that don’t require coordination with other teams.
Technical Approach
Milestone 1 — Build & Demo (Weeks 1-3/4):
Build WordPress plugin and Ghost/HTML widgets with z-address rotation, FVK-only verification (read-only, no spending keys on server), panel showing payment counter/totals/dates. Deploy public demo, basic docs, and 2-minute video tutorial. No adoption metrics required—pure deliverable focus.
Milestone 2 — Pilots & Validation (Weeks 4-6/7):
Launch 2 pilot sites in production (ideally 1 media outlet + 1 creator/NGO). Add basic Web Terminal for in-person QR payments. Track and verify payments via FVK. Primary success metric: ≥30 verified shielded payments/tips (any amount, any module). Export signed CSV/JSON with txid list as evidence.
Safeguard: If 30 not reached by week 7, we extend collection 2 weeks at no extra cost and bootstrap a $200 micro-tips fund to unblock adoption. Committee may accept milestone at ≥20 verified plus evidence of 10 pending (pilot commitments, queue) or request specific corrective actions within 2 additional weeks.
Milestone 3 — Hardening (Weeks 7-9/10):
Server hardening (serverless or VPS), security checklist, critical fixes, final docs. If “up to” budget activated: 12-month VPS + monitoring/backups, lightweight external audit ($2,500-3,000), extended tutorials, onboarding materials, marketing assets.
Upstream Merge Opportunities
This project involves original plugin development rather than forking existing Zcash repositories, so there won’t be traditional upstream merge opportunities. However, there are several ways we expect to contribute back to the broader ecosystem.
WebZjs Improvements: As we integrate WebZjs into production payment systems, we’ll likely discover edge cases, performance optimizations, or API improvements that would benefit all WebZjs users. We’re committed to submitting pull requests back to ChainSafe for any such improvements. This ensures that projects like the MetaMask Zcash Snap benefit from our work, and future developers using WebZjs have better documentation and more stable APIs.
BTCPay Server Knowledge Sharing: BTCPay Server currently has the most mature shielded payment implementation in the ecosystem. We’ve studied their architecture, and as we develop our own system, we’ll share insights in the Zcash Community Forum about what works well and what could be improved. This isn’t about submitting code to BTCPay, but rather about contributing to the community’s collective understanding of how to build production payment systems.
Zcash Foundation Documentation: If we identify gaps or opportunities for improvement in the official Zcash documentation, particularly around lightwalletd integration or viewing key architecture, we’ll submit documentation improvements to the Zcash Foundation. Clear, accurate documentation is infrastructure too, and improving it benefits everyone building on Zcash.
All code we produce will be released under the MIT License, which is maximally permissive and allows anyone to use, modify, and integrate our work into their own projects without restriction.
Budget
Total: $24,500 USD (MVP) — Up to $35,500 USD (with optional enhancements)
Our budget reflects a lean MVP focused on proving shielded payment adoption with content creators and journalists. The “up to” model allows ZCG to activate optional enhancements (hosting, audit, marketing) if the pilot metrics demonstrate strong traction. Rates are 40-50% below market for specialized blockchain work.
Hardware/Software Costs (USD): $200 (MVP) — $300 (with enhancements)
Hardware/Software Justification:
MVP covers basic SAST tools, linters, and CI/CD security scanning. Optional enhancement adds extended security tooling.
Service Costs (USD): $800 (MVP) — $4,300 (with enhancements)
Service Costs Justification:
MVP ($800): 3-month minimal VPS/serverless hosting ($300), monitoring basics ($200), domain/SSL/CDN ($300). Shared-hosting compatible (PHP-only). Focus is proving adoption, not 12-month sustainability in Milestone 1-2.
Optional Enhancements ($3,500 additional): 12-month VPS commitment ($600), comprehensive monitoring/backups ($900), lightweight external security audit ($2,500-3,000 for focused review of FVK architecture and payment flows—not full cryptographic audit). Note: Optional VPS is part of up-to enhancements, not required for MVP.
Compensation Costs (USD): $23,500 (MVP) — $30,900 (with enhancements)
Compensation Costs Justification:
MVP Core ($23,500):
- Backend dev (lightwalletd, FVK architecture, z-rotation): 80h × $80 = $6,400
- WordPress plugin (tips, PayLinks, Donate Banner): 60h × $70 = $4,200
- Ghost/HTML widgets: 25h × $65 = $1,625
- QA/testing (focused on payment flows): 20h × $45 = $900
- UX/UI (minimal panel, QR styling): 15h × $55 = $825
- Docs + 2-min video: 12h × $50 = $600
- PM/pilot coordination: 25h × $50 = $1,250
- Pilot support (setup, troubleshooting): 30h × $35 = $1,050
- Contingency (10%): $2,150
Optional Enhancements ($7,400 additional):
- Extended dev (Web Terminal enhancements, analytics): 30h × $70 = $2,100
- Security audit coordination: 15h × $80 = $1,200
- Extended tutorials (3-5 videos, onboarding flows): 20h × $50 = $1,000
- Marketing assets (comparison table, social graphics, press kit): 25h × $45 = $1,125
- Extended pilot support (20+ users): 30h × $35 = $1,050
- Contingency (10%): $925
Rates are 40-50% below market. We’re optimizing for rapid validation over feature bloat.
Previous Funding
Previous ZCG Funding: No
This is our first application to Zcash Community Grants. We have not received any previous funding from ZCG.
Other Funding Sources
Other Funding: No
We have not received and are not pursuing funding from any other sources. ZCG is the sole funding for this project. No coordination delays, no split deliverables.
Risk Assessment
Implementation Risks
WebZjs browser compatibility mitigated by targeting modern browsers (Chrome 90+, Firefox 88+, Safari 14+, representing 95%+ users) with QR fallback for older versions. Lightwalletd reliability addressed through multiple endpoints with automatic failover. Platform API changes handled via deprecation monitoring, comprehensive unit tests, and maintenance commitment. Security vulnerabilities mitigated through lightweight external review (optional enhancement), OWASP Top 10 protections, high test coverage, and responsible disclosure process. Low adoption countered with forum marketing, free setup for first 20 users, video tutorials, and targeting content creators on budget hosting. Scope creep prevented via clear MVP definition, Phase 2 roadmap, and GitHub tracking.
Potential Side Effects
Support burden managed through comprehensive documentation (including shared hosting setup), FAQ, community forum, and scheduled office hours. WordPress.org delays mitigated by early submission and direct download fallback during review. Transparent address usage (contra shielded adoption goal) addressed by shielded-by-default design with educational tooltips. Regulatory uncertainty handled via non-custodial disclaimers and legal consultation. Competition would validate market and benefit Zcash—our open-source approach and shared-hosting compatibility remain differentiators.
Success Metrics
Primary metric (Milestone 2): ≥30 verified shielded payments/tips, any amount, across any module (per-post tips, PayLinks, Donate Banner, or Web Terminal). Evidence provided via FVK-based verification (read-only), signed CSV/JSON export, and txid list.
Safeguard: If 30 is not reached by week 7, we will extend collection by 2 weeks at no extra cost and bootstrap a $200 micro-tips fund to unblock adoption. The committee may, at its discretion, accept the milestone at ≥20 verified plus evidence of 10 pending (e.g., pilot commitments, queue) or request specific corrective actions within 2 additional weeks.
Secondary metrics (aspirational, non-blocking):
- Active installations: ≥10 (WordPress + Ghost + HTML deployments)
- Downloads: ≥50 in first 30 days (WordPress.org + npm + CDN)
- Pilot testimonials: ≥2 published (media outlet, creator, or NGO)
- Issues resolved: ≥5 medium/low severity GitHub issues
- Documentation quality: <15% support requests about covered topics
- Test coverage: ≥80% with zero critical vulnerabilities
- Community engagement: Monthly forum updates posted on-time
These secondary metrics help tell the adoption story but don’t block milestone payments. Primary focus: proving 30 real people/organizations used shielded payments in production.
Project Schedule
Startup Funding (USD): $12,000
Startup Funding Justification: Covers Milestone 1 (Build & Demo) which establishes core payment infrastructure without adoption pressure. Pure deliverable focus: working modules, demo, docs, video.
Milestone Details
-
Milestone: 1 — Build & Demo
Amount (USD): 12000
Expected Completion Date: Weeks 1-3/4 from project start
User Stories:- “As a journalist, I want to accept Zcash tips on my blog in under 5 minutes without technical expertise”
- “As a content creator, I want shareable PayLinks for my social media without revealing my identity”
- “As an activist, I want a persistent donation banner that rotates addresses for privacy”
Deliverables: - WordPress plugin: Per-post tips, PayLinks generator, Donate Banner widget, z-address auto-rotation, FVK-only verification panel (no spending keys on server)
- Ghost/HTML widgets: Embeddable tips and Donate Banner for Ghost themes or any HTML site
- Web Terminal (basic): QR code generator for in-person payments
- Public demo site with working payment flows
- README with 3-step setup (install, paste FVK, activate)
- 2-minute video tutorial showing end-to-end flow
Acceptance Criteria: WordPress plugin installs via upload ZIP and activates without errors. Ghost/HTML widgets embed with single code snippet. FVK verification panel displays incoming payments correctly. Demo site is publicly accessible. Shielded payment (testnet or mainnet) completes successfully from external wallet to plugin-generated address. Video tutorial is published. Setup takes under 5 minutes for non-technical user. Zero critical bugs in payment flows. Forum report posted with demo link and installation instructions. No adoption metrics required.
-
Milestone: 2 — Pilots & Validation
Amount (USD): 8000
Expected Completion Date: Weeks 4-6/7 from project start
User Stories:- “As a media outlet editor, I want to deploy Zcash tips across 20+ articles and track total received”
- “As an NGO fundraiser, I want verifiable proof of donations received for transparency reporting”
- “As a street vendor, I want to accept Zcash payments via QR code without a wallet on my device”
Deliverables: - 2 pilot sites in production (confirmed deployments: ideally 1 media outlet + 1 creator/NGO)
- Web Terminal enhancements (improved QR display, amount pre-fill, session tracking)
- Pilot onboarding: Guided setup calls (20 min each), troubleshooting, feedback collection
- Payment verification report: CSV/JSON export with txid list, amounts, timestamps, addresses (derived from FVK)
- Forum update with pilot testimonials and adoption metrics
Acceptance Criteria: ≥30 verified shielded payments/tips (any amount) received across all modules and pilot sites. Evidence: FVK verification panel screenshots + signed CSV/JSON export + txid list verifiable on-chain. 2 pilot sites confirm modules are live and functional. Web Terminal generates QR codes correctly. Safeguard: If 30 not reached by week 7, extend collection 2 weeks at no extra cost and allocate $200 micro-tips fund. Committee may accept at ≥20 verified + evidence of 10 pending (pilot letters, queue) or request corrective actions within 2 weeks. Forum report posted with metrics and pilot feedback.
-
Milestone: 3 — Hardening (Base)
Amount (USD): 4500
Expected Completion Date: Weeks 7-9/10 from project start
User Stories:- “As a security-conscious user, I want confirmation that no spending keys are stored on servers”
- “As a pilot site admin, I want a checklist ensuring my setup follows best practices”
- “As ZCG, I want final documentation and operational readiness for community handoff”
Deliverables: - Security checklist: FVK-only architecture verification (no spending keys on server), encrypted FVK storage review (or option for users to input FVK on each session), HTTPS enforcement, basic XSS/CSRF protections
- Server hardening: Serverless or minimal VPS config, rate limiting, monitoring basics
- Critical bug fixes from pilot feedback
- Final documentation: Updated README, troubleshooting guide, FAQ
- Forum report: Security posture, lessons learned, next steps
Acceptance Criteria: Security checklist completed and posted publicly. Serverless/VPS config follows hardening guide (no unnecessary services, firewall rules, HTTPS only). FVK architecture verified (spending keys never touch server). Critical bugs from pilot phase resolved. Documentation updated with pilot learnings. Load testing shows modules handle 100+ concurrent requests without failures. Forum report posted with security summary and operational readiness confirmation.
-
Milestone: 3 — Hardening (with Optional Enhancements)
Amount (USD): 15500 (if “up to” budget activated)
Expected Completion Date: Weeks 7-10/11 from project start
User Stories:- “As a long-term user, I want 12-month hosting commitment so the service remains stable”
- “As a donor, I want external security audit confirmation before trusting the system with larger amounts”
- “As a new site owner, I want extended tutorials and onboarding materials for smooth setup”
Deliverables (includes all base Milestone 3 + following): - 12-month VPS hosting + monitoring: Uptime monitoring, automated backups, disaster recovery plan
- Lightweight external security audit ($2,500-3,000): Focused review of FVK architecture, payment flows, z-address rotation logic. Threat model document. Public report with all findings resolved.
- Extended tutorials: 3-5 video tutorials (pilot onboarding, troubleshooting, Web Terminal for events, bulk PayLinks)
- Onboarding materials: Step-by-step guides for media outlets, NGOs, individual creators
- Marketing assets: Comparison table (vs NOWPayments, BTCPay, ZGo), social graphics, press kit, blog post draft
- Extended pilot support: Onboarding for 10+ additional sites, office hours (2h/week × 4 weeks)
Acceptance Criteria: All base Milestone 3 criteria met. VPS 12-month contract signed with monitoring/backups active. External audit report published showing zero unresolved critical/high vulnerabilities. 3-5 video tutorials published (total runtime 10-15 min). Onboarding materials available in GitHub docs. Marketing assets completed (comparison table, 5+ social graphics, press kit PDF). Office hours logs show 10+ sites received guided setup. Forum report includes audit summary, extended pilot feedback, and sustainability roadmap.
Payment Schedule
This table shows the payment schedule with milestone amounts and timeline windows:
| Milestone | Key Deliverable | Amount (USD) | Timeline | Cumulative |
|---|---|---|---|---|
| 1 | Build & Demo — WP+Ghost/HTML modules, z-rotation, FVK panel, demo, docs, video | $12,000 | Weeks 1-3/4 | $12,000 |
| 2 | Pilots & Validation — 2 pilot sites, ≥30 verified payments, Web Terminal, report | $8,000 | Weeks 4-6/7 | $20,000 |
| 3 (Base) | Hardening — Security checklist, server hardening, critical fixes, final docs | $4,500 | Weeks 7-9/10 | $24,500 |
| 3 (Enhanced) | Hardening + 12-mo VPS, audit, tutorials, onboarding, marketing assets | $15,500 | Weeks 7-10/11 | $35,500 |
MVP Total: $24,500 (Milestones 1, 2, 3 Base)
“Up To” Total: $35,500 (Milestones 1, 2, 3 Enhanced)
The structure prioritizes rapid validation: Milestone 1 builds modules without adoption pressure, Milestone 2 proves real-world usage with one clear metric (30 payments), Milestone 3 hardens for sustainability. The “up to” model lets ZCG activate enhancements (hosting, audit, marketing) if pilot metrics demonstrate strong traction.
Supporting Documents
- GitHub Repository (Social Mask): GitHub - Emilio983/SocialMask - Our previous work demonstrating technical capability with decentralized applications and Web3 integration
- Live Demo: https://socialmask.org - Working demonstration of our team’s ability to ship production applications
- Legal Credentials: https://admiweb.col.gob.mx/osfbc/documentos/firmadas2024/Oswaldo_Navarro_Hernndez.pdf - Official documentation of Oswaldo Navarro’s legal representative status and government credentials
Why This Grant Matters to Zcash
Only 20% of ZEC exists in shielded pools. Content creators, journalists, and activists need financial privacy but are excluded by technical complexity (BTCPay/ZGo require Docker + full nodes) or forced into transparent-only solutions (NOWPayments/Plisio). We’re proving shielded payments can be dead-simple: 5-minute setup, no spending keys on servers, automatic z-address rotation for privacy by default.
This isn’t about building elaborate WooCommerce integrations or subscription platforms in an MVP. It’s about validating the simplest possible path to real adoption: tips, donations, and in-person payments. If 30 people/organizations use shielded Zcash in production during a 3-4 week pilot window, we’ve proven product-market fit. If we can’t hit 30, the safeguards let us extend collection, bootstrap with micro-tips, or adjust based on committee feedback—we don’t fail the milestone over a metric miss when modules work correctly.
The “up to” budget model gives ZCG flexibility: approve the lean MVP ($24.5K) if you want rapid validation with minimal risk, or activate enhancements ($35.5K total) if pilot metrics show strong traction and warrant 12-month hosting + external audit + extended marketing.
Success looks like: 30+ verified shielded payments within weeks 4-7, 2 pilot sites publishing testimonials, FVK-only architecture proven secure (no server compromise risk), documentation showing journalists/activists can self-deploy in 5 minutes, and a foundation for future projects (Social Mask, other apps) to integrate shielded payments without reinventing the wheel.
This aligns with ZCG priorities: increases adoption (proves privacy-preserving payments work for non-technical users), advances privacy tech (FVK architecture + z-rotation), builds ecosystem infrastructure (reusable patterns for future grants), appropriately scoped (lean MVP, clear success metric, safeguards against failure).
Contact: Emilio Navarro Mejía | hi@socialmask.org | Emilio983 (Emilio Navarro Mejia) · GitHub | @Emilio983 (Forum)
