Open-source Orchard-based Wallet Service for Enterprises – Looking for Users & Feedback

Quick update — thanks for the early feedback.

Recently we shipped v0.2.0 (housekeeping) + v0.2.1 (security hardening). Highlights:

  • Apache-2.0 LICENSE added (was missing → effectively All Rights Reserved before)
  • Removed default admin/admin123; strong secrets auto-generated on first start
  • docker compose up --build now works end-to-end (verified login → JWT)
  • Zcash deps upgraded (orchard 0.13 / zcash_primitives 0.27); fresh cargo build unblocked after the core2 yank
  • Internal security audit — closed 1×P0 (wide-open CORS) and 4×P1 (rate limit / fail-closed auth / body limits / CSP). Full delta in SECURITY.md + CHANGELOG.md.

Repo: GitHub - robustfengbin/zpay-enterprise: A modular Web3 wallet management service with multi-chain support (Rust + React) · GitHub · latest tag v0.2.1

If you held off because the project looked too rough — now’s a reasonable moment to try. Real deployment friction / API gaps / integration paper-cuts → feedback welcome.

@aarnott — your three points all land:

  1. Diversified shielded addresses — partially: FullViewingKey::address(diversifier, External) is wired internally, but the REST API only exposes one UA per wallet today. The N-diversifier endpoint is the natural next step — exactly your eZcash / Nerdbank.Zcash design.
  2. ZIP-32 + BIP-39 derivation already lives in keys.rs, but create_wallet generates an independent SpendingKey per wallet instead of using master-seed → ZIP-32 accounts. Real correctness gap, not a HSM choice. Roadmap: master-seed-per-tenant + each wallet = ZIP-32 account index.
  3. HSM — v0.1 wording was misleading. Future story: master seed sealed in HSM, derived spending keys via sign-only handle. Will fix the docs.

Three GitHub issues incoming for the items above.

2 Likes