Repository navigation
Konclave v0.13.0
Pre-release
Pre-release
The app
Security
- A device checks more of a transaction before it signs. In earlier versions a device checked what
a transaction pays (since 0.10.0) and not much else about it. A coordinator could build the
approved payment with an expiry far in the future and keep the signed transaction to broadcast
later; could set a fee above the network rule, within the ceiling the device allowed; and could ask
the devices that approved a payment to sign a second, different transaction for it, so that both
could go out. A device now refuses a transaction that expires outside the window its own clock
allows, that is built for another network or transaction version, or whose fee is not exactly the
network rule (ZIP 317). On this device, it refuses to sign a second transaction for the same
approval without the explicit confirmation of the member who signs. We have no report that any of this
was used; we did not check. What a member can notice: a device may refuse to sign with one of a
few new messages, each saying what to check. - Creating or joining a vault needs an up-to-date app. An app cached from before 0.12.0 could
still create a vault the old way, the one the 0.12.0 notice describes, and the coordinator gave
that vault an address. The app now sends, with every registration, a field that identifies the
version of the app, so the coordinator can ask an outdated app to update; when it does, this app
says so before a creation or a join starts, and asks to reload (or, on the desktop app, to install
the latest release from the project's releases page). The coordinator does not refuse yet; a
notice period comes before it does (Known limits).
Changed
- The signing panel shows the whole destination address and the network fee before you sign. The
address is no longer shortened, the fee and the total that leaves the vault are shown as the
estimate they are, and the confirm repeats them. A payroll's fee appears once its lines are known.
Known limits
- Apps up to v0.12.0 cannot say they are out of date. Once the coordinator asks for an
up-to-date app, one of these creating or joining a vault may not finish: it may get no address, so
nothing could be received into it, without the app saying why. Reloading the page brings the
current app. The desktop app has no updater yet (#606): install the latest release by hand. The
plan: the app side ships first, desktop installer included, and the coordinator asks only after a
notice period. - The exact-fee check uses the network's current fee per action. If the network lowers it (ZIP
2009 proposes this at block 3,590,000), devices on this version would refuse honest payments until
they update. Plan: a build that follows the network's fee by block height, out before block
3,590,000. Status: planned, not started. - The
/netpage does not have the signer's newer checks, nor a content check of its own; use
the vault's own signing screen for payments. - A device that signed a payment does not answer a new attempt at that same payment until the page
is reloaded. Nothing is signed meanwhile; reload the page, then sign the new attempt.
The desktop shell and shared parts
Services deployed when this was cut (2026-10-15): coordinator
4223028, relay42da05bf003afc41.
The web app is this release's own commit. The two services are deployed by hand and may be
older than it - recording what they were ANSWERING is the point, not what they should have been.
The notice for this release: https://forum.zcashcommunity.com/t/konclave-a-group-vault-on-zcash-frost/57218/23
Security
- The browser signer checks more of a transaction before it signs. In earlier versions a device
checked what a transaction pays (since 0.10.0) and not much else about it. A coordinator could build the
approved payment with an expiry far in the future and keep the signed transaction to broadcast
later; could set a fee above the network rule, within the ceiling the device allowed; and could ask
the devices that approved a payment to sign a second, different transaction for it, so that both
could go out. A device now refuses a transaction that expires outside the window its own clock
allows, that is built for another network or transaction version, or whose fee is not exactly the
network rule (ZIP 317). On this device, it refuses to sign a second transaction for the same
approval without the explicit confirmation of the member who signs. We have no report that any of this
was used; we did not check. What a member can notice: a device may refuse to sign with one of a
few new messages, each saying what to check.
Changed
- A desktop release's notes now list its commits. Under the changelog's own words, the notes on a
GitHub release list the commits since the previous release, grouped by type (security, added,
fixed, and so on, merges left out), each linked to the commit. The list comes from git-cliff, pinned to 2.14.2 in the
release workflow and installed from crates.io with its lockfile.
Known limits
- The
/netlab screen does not have the signer's newer checks, and still signs with no content
gate of its own (it has no approved payment to compare with). - The approved lines a device compares with still come from the coordinator at signing (#567).
Commits
Security
- signer: a device checks more of a transaction before it signs, and a vault is created only by an up-to-date app (
21220b1)
Documentation
- changelog: state what each closed route could and could not do (#654) (
c0d1398) - changelog: state what each closed route did and when it opened (#656) (
724fa00) - security: say that current vaults are not ZIP 2005 recoverable (#665) (
9328641)
Maintenance
- release: release notes list the commits since the previous release, grouped by type (#650) (
f913d97) - release: v0.13.0 (
f91cb48)
Desktop installers (Windows / macOS / Linux) are attached below.