Zkool

Key Facts

• The official repository describes Zkool as a multi-account Zcash wallet and the successor to YWallet.
• Zkool documents transparent, Sapling, and Orchard support plus rotated addresses and coin control.
• The wallet supports viewing-only accounts, FROST threshold signatures, and offline PCZT transaction workflows.
• Connections can use full nodes or light nodes, with Tor proxy and onion-service support documented for Zcash servers.
• The current reviewed release is zkool-v6.23.0, published on July 2, 2026.

Zkool is built for control rather than concealment

Zkool's feature table reads more like an operator console than a consumer wallet checklist. It supports multiple accounts, hidden protected accounts, an encrypted database, per-account synchronization state, transparent and shielded pools, rotated addresses, memo search, multiple recipients, and explicit node selection. That breadth makes it relevant to developers, treasuries, testers, and experienced users who need to see what a transaction is doing.

The same breadth can be dangerous when it is mistaken for automatic privacy. Zkool lets the user choose among transparent, Sapling, and Orchard behavior. A transparent receiver remains public. Cross-pool movement can create observable structure. A viewing key deliberately grants visibility. The wallet provides the controls; the operator still needs a threat model and a reason for each choice.

The YWallet succession is explicit

Zkool is not merely another wallet from the same maintainer. Its repository presents the project as YWallet's successor, and the feature set carries forward many of YWallet's advanced account and pool controls. Existing YWallet users should treat that as a migration signal, not an instruction to move funds blindly. Account formats, recovery material, viewing keys, and transaction history all need to be understood before changing the application that manages them.

A safe comparison begins with read-only evidence. Confirm which receiver types and keys the old account uses. Back up recovery data before installing anything. If importing into Zkool is appropriate, test one account and one small transaction before moving the rest. A successor can be actively developed while an older wallet still receives maintenance releases, so the decision is about long-term operating fit rather than a dramatic shutdown date.

FROST and PCZT enable serious signing workflows

Zkool documents distributed key generation and FROST signatures for shielded multisignature accounts. In a threshold setup, participants hold shares rather than one person holding the entire signing key. That can reduce a single point of key compromise, but it adds coordination, participant authentication, share backup, and recovery questions. The threshold must fit the real organization, including what happens when a signer is unavailable.

The wallet also supports loading, saving, and signing transactions for offline and cold-wallet operation through PCZT. Separating construction from signing can keep spending authority away from a networked device. It does not make the transaction safe by itself. The offline signer still needs a trustworthy way to inspect recipients, amounts, fees, and pool behavior before approving the final transaction.

Node and Tor choices expose the real privacy tradeoffs

Zkool can connect to full nodes and light nodes, and its documentation includes Tor proxy and onion-service support. A self-operated full-node path can reduce dependence on a third-party lightwallet service, while Tor can change what a direct server learns about the connecting network address. Neither option erases all metadata, and both create operational responsibilities around updates, availability, certificates, and endpoint trust.

The practical question is whether the user can maintain the selected route. A stale full node is not better because it belongs to the user. A Tor configuration that silently falls back to clearnet may violate the intended threat model. A light node can be entirely reasonable when its metadata boundary is understood. Zkool is valuable because it makes these choices visible, not because one toggle guarantees anonymity.

The limitations are part of the recommendation

The repository says the user interface is basic and names missing features including an address book, third-party swaps, spending tracking, a pool-transfer tool, and automatic shielding. That candor is useful. A basic interface can be easier to audit mentally, but it can also place more burden on the user to recognize a wrong receiver, an unexpected pool, or a workflow that a mainstream wallet would guide more tightly.

Choose Zkool when the advanced controls solve a problem you actually have. For a first Zcash wallet, a shielded-first mobile product may be easier to operate correctly. For an experienced user who needs multi-account state, viewing-only access, Tor, FROST, or offline signing, Zkool deserves serious evaluation. Install only from the official repository or linked release artifacts, then test backup and recovery before relying on it.

FAQ