How to Contribute to Zcash: Code, Docs, and Community

You Don't Need to Be a Cryptographer

Many people assume contributing to a privacy cryptocurrency requires deep cryptographic knowledge. It doesn't. Zcash needs writers, translators, designers, community managers, event organisers, educators, and advocates just as much as it needs Rust developers. The Zcash ecosystem is broad — somewhere in it is a gap your skills can fill.

This guide covers every major contribution path. Start with what fits your skills, and grow from there.

Code Contributions

Zcash's code lives primarily on GitHub at github.com/zcash. Key repositories include:

• zcash/zcash — The core node (C++). Requires familiarity with Bitcoin's codebase and Zcash-specific privacy constructs.
• zcash/librustzcash — Rust library for Zcash cryptographic primitives. Requires Rust experience.
• zcash/zashi-android / zashi-ios — The official mobile wallets. Requires Kotlin/Swift experience.
• zcash/zcash-light-client-ffi — Light client bindings. Cross-language experience helpful.

Start by looking for issues labelled "good first issue" or "help wanted." Read the contributing guidelines (CONTRIBUTING.md) in each repo before submitting a pull request. Join the developer Discord to introduce yourself and discuss your intended contribution before writing significant code.

Documentation and Technical Writing

Clear documentation is perpetually under-resourced in open source projects, and Zcash is no exception. Opportunities include:

• Improving or expanding the official Zcash documentation
• Writing tutorials for specific use cases (using Zcash for business payments, running a node, etc.)
• Creating developer onboarding guides for the Zcash SDKs
• Writing ZCG grant proposals for documentation projects

If you see documentation that's outdated, incomplete, or unclear — fix it. Submit a PR if it's on GitHub, or post a correction on the forums if it's web content.

Translation and Localisation

Zcash is a global tool but most of its documentation is English-only. Translating key resources — the z.cash website, wallet documentation, privacy guides — into other languages dramatically expands Zcash's reach. Spanish, Mandarin, Portuguese, Hindi, and Arabic translations are particularly impactful given the size of those language communities.

You can apply for a ZCG grant specifically for translation work. Some translation projects (wallet strings, for example) are managed through Transifex or similar platforms where individual contributions don't require a grant.

Community Building and Advocacy

Community contributions that don't involve code or writing are equally valuable:

• Local meetups: Organise Zcash meetups in your city. Even a small group discussing privacy technology raises awareness.
• Conference talks: Speak about Zcash at cryptocurrency, privacy, or developer conferences.
• Social media: Accurate, thoughtful content about Zcash on Twitter/X, Reddit (r/zec), and other platforms helps correct misconceptions and build community.
• Forum participation: Thoughtful engagement on grant proposals and governance discussions is a genuine contribution, even without a vote.

Building on Zcash

If you're a developer, building applications that use Zcash's privacy features is one of the most impactful contributions possible. Merchant payment integrations, privacy-preserving apps, DeFi connectors, and tooling all expand the ecosystem's utility. The Zcash SDKs (available in Rust, Swift, Kotlin, and via FFI for other languages) make this more accessible than ever. See our developer resources guide for the full toolkit.

Testing and Bug Reporting

Quality assurance is underappreciated but essential. You can help by:

• Testing pre-release wallet versions and reporting bugs on GitHub
• Running testnet transactions to verify new protocol features
• Testing ZIP implementations on testnet before mainnet activation
• Reporting UX issues, not just code bugs — confusing UI is also a bug