Konclave is officially submitted to @colosseum.
A private group treasury on Zcash, built for shared approvals, threshold signing and private payments.
The money belongs to the group.
The control should too.
https://t.co/hK5gj6zG9U
Konclave v0.19.0 is available as a pre-release.
Treasury analyses now show available, reserved and confirming funds. Spending pace and runway estimates, plus payroll, security and visibility improvements.
Release notes ↓
https://t.co/RzeaCyCLof
If every member can open the vault’s books on their device, it was not affected.
If a member cannot access their vault or sees their seat held by another device, do not fund it or try an in-app repair. Contact us privately through the advisory.
Security advisory: GHSA-42h7-6fcj-554w.
Until Nov 8, our coordinator could accept a vault’s first read key from anyone who knew its ID, before a member registered it.
Fixed in the hosted coordinator; v0.18.0 adds new-vault checks. Full advisory ↓ https://t.co/eLS6z5SHcY
The issue exposed vault records and the viewing key. It did not allow spending: payments still require members’ key shares, which never leave their devices.
We have no report that this was exploited.
Konclave v0.18.0 is out.
See what changed in your group's approvals, track treasury activity by beneficiary, and export more detailed financial records.
We've also made vault permissions and trust boundaries easier to understand.
Release notes: https://t.co/GiKyTuPxHk
Konclave v0.17.0 is out as a pre-release.
Clearer approvals, period-based treasury records, reusable payroll drafts, and more accurate financial exports.
Less friction in the work of managing shared funds on Zcash.
Release notes: https://t.co/AdFgCQYdRB
NU7 is live on Zcash mainnet.
A shielded payment from a 2-of-2 Konclave vault, signed on two of our devices, was mined in block 3,543,421, 16 blocks after activation.
It ran on v0.16.0, the version in production today.
https://t.co/QzlyB0CvXO
@konclavevault@danielgorgonha1 , pensando em como isso conseguir integrar com a vault, o time poder gastar o tesouro também. Tenho outras ideias também.
@michael2xl@konclavevault Boa, @michael2xl! Encaixa bem: o time guarda a tesouraria num cofre do Konclave e, quando a entrega é aceita, propõe o pagamento. O grupo aprova e ele sai. Concurso com vários vencedores vira uma folha só, aprovada uma vez. Bora conversar sobre esse passo do pagamento?
NU7 goes live on @Zcash mainnet this week.
Konclave is already ready for the transition.
v0.16.0 includes the network-upgrade logic needed to handle the change in consensus rules around activation.
Ready before activation. Built for the transition.
Konclave v0.16.0 is live.
Signing and vault creation are more tightly checked, Konclave is now ready for the NU7 transition, and the public proof set includes 22 Zcash mainnet transactions.
Release notes ↓
https://t.co/522nkRhbBM
Happy 10th birthday, @Zcash !
A decade of building for financial privacy.
Konclave exists because Zcash gives us the foundation to build shared control without making every payment public.
We’re proud to be building private group treasury infrastructure on Zcash.
Konclave v0.15.0 is live.
This release tightens the hosted send path, improves coordinator failure handling and adds stricter relay timeouts.
Validated on Zcash mainnet with a 2-of-2 payment signed across two devices.
Release notes ↓
https://t.co/aQ01HtLfst
Konclave v0.14.0 is live.
This release hardens the relay with explicit memory limits and per-client request budgets, while laying the groundwork for NU7 support.
More resilient infrastructure. Clearer boundaries. Same focus on shared control.
https://t.co/SXTby5A0IJ
One thing we tightened in v0.13.2:
the signer now rejects spends that still carry a dummy spending key instead of treating them as vault spends.
No key exposure. No funds moved in this failure mode.
Small edge case. Important signing boundary.
The updated flow has already been exercised with real ZEC on Zcash mainnet.
A vault created with the new ceremony completed a payment using the new signing checks.
That proves the updated path can complete end to end.
Vault creation changed too.
Before any secret material is exchanged, every member now confirms the same short code.
Only after everyone confirms the same participant set does the vault ceremony continue.
See it in action → https://t.co/hK5gj6zG9U
What does a Konclave signing device verify before it signs?
It checks the network, version, expiry and fee rules locally. It also requires explicit confirmation before signing a second transaction tied to the same approval.
See it in action → https://t.co/hK5gj6zG9U
Konclave v0.13.1 is live.
The latest releases strengthen two critical parts of the shared vault flow: vault creation and transaction signing.
Web app: live.
Desktop v0.13.x: beta/pre-release.