Hello Zcash Community,
We’re building Recoverify — a tool that lets you verify whether a Zcash wallet backup can actually reproduce the wallet state you expect, while the original wallet is still available. Think of it as a fire drill for your backup: you find out if your backup works before your device is lost, not after.
Why this matters
Zcash wallets involve multiple pools (Transparent, Sapling, Orchard) and different address/key-derivation models. A seed phrase can look valid and still fail to reproduce everything. There are documented cases of Zcash users discovering recovery problems only after losing access to their original wallet, including cases involving legacy wallet state and recovery material that did not reproduce the expected funds.
A restore can also fail simply because it did not search far enough, such as using an incorrect birthday height or insufficient discovery range. Normally, you only discover these problems when the original wallet is already gone.
How it works
- You provide your recovery material locally, prioritizing viewing keys where supported.
- Recoverify derives the applicable recovery information and scans the relevant chain data using existing Zcash Rust wallet infrastructure.
- It reports what was verified, what was not, and why, for example:
- Orchard: Verified
- Transparent: Verified through index 24
- Legacy Sapling: Additional backup required
- If something is missing or cannot be verified, you can address the problem while the original wallet access is still available.
Recoverify is not another wallet or recovery implementation. It is a verification layer built on zcash_keys, zcash_client_backend, and ZIP-32, with recovery profiles per supported wallet model. Sensitive recovery material stays on the user’s machine; seed phrases and spending keys are never sent to us.
Grant request: $2,990 USD over 8 weeks — recovery engine, initial recovery profiles, CLI, minimal local web UI, light-client integration, tests, and documentation.
About us: Previously received Zcash Foundation funding for a governance voting widget shipped on the Zcash Discourse forum. The same approach applies here: narrow scope, build on existing Zcash primitives, keep sensitive processing loca
Link: