Know what keeps funds safe
Who can do what, what is checked where, and what isn’t done yet.
Status
Zafe is a beta on Zcash mainnet and hasn’t had an external security audit. Only use money you can afford to lose. The audit’s scope is public, and where Zafe departs from the Zcash drafts, the Zcash Foundation has confirmed the approach (frost#1094).
Who can do what
- Fewer members than the rule can’t spend, and can’t make another member’s phone sign something it didn’t check.
- Enough members together can spend; that is the rule. If money leaves without a payment in the vault’s history, every phone shows “Money left without approval”.
- The member who proposes picks the payment, but can’t change what the others’ phones check: recipients, amounts, memos, change and fee.
- The server, or anyone on the network, sees who talks and when. It can’t read messages, forge them, spend, or slip in an older or different history without phones noticing.
- Zafe, the project, can’t move or see your funds. There are no accounts, analytics or crash reports.
What is checked where
- Setup: safety words, compared out loud, prove that no one sat in the middle.
- Each payment: every phone rebuilds and checks it before approving and again before signing (what it checks).
- On the phone: approving, proposing and sending need an unlock. The wallet data is encrypted, and Android backups and device transfers never copy the key share.
Known limits
- Members and the rule can’t change. Anyone who was a member can still see the vault, and their key share still counts. To rule someone out, make a new vault and move the funds.
- Every member sees every payment, memo and the balance, past and future.
- If quantum computers ever break today’s cryptography, one member’s copy of the vault secret could be enough to spend. The funds would then need to move to a quantum-safe vault, once Zcash offers one.
- The first time a phone loads a vault, it trusts the server’s history once. After that it checks every change.
- Android only for now.
Report a problem
Write to security@zafe.cash. The design is in the spec and the code is open source.
Checked with Zafe 0.1.23 · 2026-10-27