Historical Commonveil release, 12 November 2026. Based on the project's official versioned release record. This does not establish an independent cryptographic audit.
Commonveil 0.20.0 records a full security review, and Secure Net. Here is the project history, technical detail and reasoning behind the update.
Why this update matters
This update focused on reducing risk before expanding the protocol. It records 24 findings from an independent security review and the tests added for each. That is valuable evidence of remediation, but it must not be misrepresented as an independent cryptographic audit of every protocol component. The release also strengthened session invalidation, key rotation, first-admin setup, update behaviour and the independence of the self-hosted build.
What changed in version 0.20.0
The official release notes recorded the following changes. These describe the version at the time, and later releases may have replaced, improved or removed particular mechanisms.
- All 24 findings from an independent security review are fixed, each with a test. docs/SECURITY_REVIEW.md lists them.
- Disconnecting a device, changing your password or recovering your account now signs out every other session at once.
- Adding a passkey, approving a new browser or replacing your owner key now needs proof it's you: one of your devices confirms it without asking, or you enter your password.
- Removing a device now changes the keys of every community it could read, so it can't read anything new.
- Self-hosted sites: the first admin needs a one-time setup code printed on the server, so a stranger can't claim a new site first. ADMIN_USERNAMES and email (SMTP) settings are gone.
- Self-hosted sites: updates that fail no longer stay "Updating…", the updater won't go backwards unless you allow it, and backups are pruned by age.
- Self-hosted sites no longer depend on Base44 in any way: the image builds and runs with nothing of theirs, and a check stops the build if that ever changes.
- Talking to other sites is safer: a site's address is checked at the moment of connecting, and replies are cut off as soon as they're too big.
- Commonveil is now built on Secure Net, our protocol as a separate library (github.com/Comutability/secure-net) that other apps and sites can use. It adds communities that approved sites can mirror and keep running if their home site goes down, structured debates and votes (public or secret) that can authorise changes, private tokens (RFC 9497), personas, consent capsules, and extension and theme manifests.
How this fits the wider Commonveil direction
Comutability's wider aim is useful, accessible technology that gives people more control. For Commonveil that means encrypted communication, meaningful user permissions and the option to run a site independently. We also need to keep a clear boundary between what the project records as implemented, what has been tested and what still needs expert review.
The detailed release notes above provide a starting point for members and contributors to test the behaviour, read the documentation and challenge assumptions.
What to check next
Review the security notes and tests, repeat deployment checks and continue qualified review of the newer Secure Net cryptography.
