Zkool Documentation
  • What's new

    • Since 6.35
    • Since 6.34
    • Since 6.32
    • Since 6.31
    • Since 6.30
    • Since 6.29
    • Since 6.28
    • Since 6.27
    • Since 6.26
    • Since 6.25
    • Since 6.24
    • Since 6.23
    • Since 6.22
    • Since 6.21
    • Since 6.20
    • Since 6.19
    • Since 6.18
    • Since 6.17
    • Since 6.16
    • Since 6.15
    • Since 6.14
    • Since 6.13
    • Since 6.12
    • Since 6.11
    • Since 6.10
  • Guides

    • Getting Started
    • Account Manager
    • Synchronization
    • Account
    • Addresses
    • Payments
    • Other features
    • Building Zkool from source
  • Recipes

    • Edit an Account
    • Supported Key Types
    • Cold Wallet
    • Ledger
    • Troubleshooting Synchronization Issues
    • Folders
    • Contacts
    • Database/Wallet Files
    • Using TOR
    • Security
    • Kiosk Zkool
    • Mempool
    • Payment URI
    • Locking Notes
    • Mainnet, Testnet, Regtest
    • Export to CSV
  • Categories / Reports

    • Overview
    • Examples
    • Categories
    • ZEC Price
    • Charts
  • MultiSig Accounts / FROST

    • Overview
    • Key Generation
    • Signing a Transaction
  • GraphQL

    • GraphQL API
    • Build
    • GraphIQL
    • Account Management
    • Synchronization
    • Balance
    • Transaction History
    • Receiving Funds
    • Sending Funds
    • Unconfirmed Funds
    • Notifications / Subscriptions
  • ZSA

    • Zcash Shielded Assets
    • Testnet
    • Using ZSA with Zkool
  • Coin Weighted Voting

    • Overview
    • How to vote
  • Cloud Vault

    • Overview
    • How to use
  • Zcash tech

    • Shielded Pools
    • Bitcoin Data Model
    • Transaction Graph
    • Privacy

A release of fixes for multisig accounts, the Orchard migration and the Cloud Vault.

Released 1 September 2026.

Multisig sessions follow the chain

Key generation and signing sessions used to synchronize on their own, on a 30 second timer. They now rely on the wallet's autosync and take one step per block, so a session cannot stall because another synchronization was running, and two passes can no longer overlap. A payment whose funds are tied up in change that is not yet mined waits for the next block instead of failing.

The key generation page reports every stage, from broadcasting the participant keys through the round 1 and round 2 packages to the final key. The notes spent by a group transaction are locked when it is broadcast, so a second session cannot spend them again before the transaction is mined. See the MultiSig Accounts section.

Also

  • The Orchard migration no longer stalls when the remaining Orchard balance is between 0.005 and 0.0062 ZEC.
  • Turning the Cloud Vault off signs out of Google, so turning it on again lets you pick another account.
  • Saved transactions (PCZT files) use the standard bincode encoding, so other tools can read them.
  • Fetching the details of a transaction waits for a running synchronization rather than racing it.
Last Updated: 11/6/26, 12:26 AM
Contributors: hhanh00
Prev
Since 6.29
Next
Since 6.27