ZBooks

Accounting & batch payouts
for shielded ZEC teams.

Read-only UFVKs. One transaction pays everyone. Auto-reconciled. Spending keys never leave the treasurer's wallet. Built for the workflow ZecHub actually runs today.

Sign in with ZcashView on GitHub
Non-custodial M-of-N approvals ZIP 321 batches Auto-reconciled
zbooks / payouts / july
draft
ZecHub contributors, July
0.755 ZEC
  • S
    squirrel
    Ecosystem Digest
    0.080
  • G
    gorgagian123
    Wallets page
    0.080
  • 0
    0xmtg
    Tutorials page
    0.145
  • H
    Haryourdhejih
    Ambassadors wiki
    0.150
  • K
    Kellyjoe8
    Zipher motion
    0.300
Try it now

Pick a sign-in flow.

Three flows via SIWZ: memo-challenge (any shielded wallet), signed message paste, or MetaMask Snap. First sign-in on a fresh instance becomes admin.

Loading session…
  • UFVK read-only
  • ZIP 321 multi-recipient
  • ZIP 316 unified viewing keys
  • ZIP 317 fee estimation
  • M-of-N HMAC-bound approvals
  • AES-256-GCM at rest
  • HKDF-SHA256 key derivation
  • Auto-reconciled from chain
  • MetaMask Zcash Snap
  • Memo-challenge sign-in
  • MIT licensed
  • UFVK read-only
  • ZIP 321 multi-recipient
  • ZIP 316 unified viewing keys
  • ZIP 317 fee estimation
  • M-of-N HMAC-bound approvals
  • AES-256-GCM at rest
  • HKDF-SHA256 key derivation
  • Auto-reconciled from chain
  • MetaMask Zcash Snap
  • Memo-challenge sign-in
  • MIT licensed
How it works

Three steps. No spending key ever leaves the wallet.

Every write action is gated by an M-of-N approval bound to the exact payable set.

01

Bring your treasury viewing key

Paste a UFVK on the Keys page. ZBooks reads shielded history. Spending stays in the wallet.

02

Build a run, M-of-N approves

Import completed bounties or add lines by hand. HMAC-bound to the exact payable set. Editing any line invalidates older approvals.

03

One shielded tx pays everyone

Scan one ZIP 321 QR in YWallet or ZODL. ZBooks watches the treasury and marks each line paid as the chain confirms.

What's inside

Six things that make Zcash treasuries workable.

Every feature is live on mainnet today.

Bring your own viewing keys
Paste one or more UFVKs. ZBooks gets read-only access; your spending key never leaves the wallet.
Pay everyone in one batch
One multi-recipient ZIP 321 QR. The treasurer signs in their own wallet. ZBooks reconciles each payment back to its line.
Reports your accountant recognises
Monthly P&L, contractor totals, CSV export shaped for QuickBooks and Xero. Reconciled payouts post themselves.
Memos become categories
Shielded memos arrive as the first draft of every transaction's notes. Treasurer reviews. Everyone else just reads.
Roles, not seats
Admin sets policy, treasurer tags and pays, viewer reads. Onboarding a new finance contractor is one sign-in.
Shielded by default
Sign-in and balance sync ride encrypted Zcash memos. Amounts and counterparties stay off the public ledger.

Read the code, then run it.

ZBooks + SIWZ are shipped as one MIT-licensed monorepo. Docs, threat model, and the shielded deployment recipe live alongside the code.

Star on GitHubSign in ↑