Hi all,
Grant application (GitHub): [[paste the link to your GitHub issue here once you have filed it]]
I want to share a small, focused grant and get feedback before it goes through review.
The gap: Zallet, the Rust wallet replacing the zcashd wallet in the Z3 stack, is in alpha, and the maintainers have opened several operability features for outside contributors. Each of these carries the `E-help-wanted` and `Z-contributors-wanted` labels in zcash/wallet, so the work is explicitly requested:
- #316 `getwalletstatus` RPC: report the wallet’s observed and processed tip heights, so tests and operators can poll for sync state instead of using sleeps.
- #366 readiness and liveness endpoints (`GET /ready`, `GET /healthy`) on a dedicated port, matching what Zebra already exposes, so Zallet runs reliably under orchestration.
- #321 translatable CLI messages: move the remaining user-facing CLI strings into the existing Fluent framework.
The proposal: Implement these three as reviewable pull requests against zcash/wallet, each with tests, coordinated with the maintainers. The deliverables are the PRs themselves.
Proof of work: I have already opened a PR for the smallest one (#321, translatable CLI): i18n: make remaining user-facing CLI error messages translatable by AngryDavee · Pull Request #460 · zcash/wallet · GitHub . I also built a PCZT interoperability proof of concept recently ( GitHub - AngryDavee/pczt-interop: Proof of concept: PCZT round-trip, role-boundary, and test-vector generation for cross-implementation interop testing · GitHub ), and I have a separate PCZT grant under review (#311), which I mention here for transparency.
I would value feedback on scope and on whether the readiness/liveness endpoint approach in #366 matches how operators want to run the Z3 stack. Thanks.