Historical Commonveil release, 29 October 2026. Based on the project's official versioned release record. This does not establish an independent cryptographic audit.
Commonveil 0.1.1 records signed group changes. Here is the project history, technical detail and reasoning behind the update.
Why this update matters
The earliest rebuild already needed to confront how group membership and keys can change. Signed group changes and the ability to pause membership helped establish a direction: membership actions should be verifiable, not taken merely on the server's word. A browser test suite made those flows easier to check.
What changed in version 0.1.1
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.
- Changes to groups need a device signature, membership can be paused, a stale-keys fix, and a browser test suite.
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.
This update is deliberately narrow. The release record does not provide enough evidence to invent further implementation details, so we have kept its scope precise and linked the source history for anyone who wants to inspect the code.
What to check next
Preserve tests as features grow, especially when a device has old keys or a membership change is interrupted.
