Key Transparency

The check runs entirely in your browser: this page downloads the signed log's static files from verify.pollis.com/v1/commit-log-2/ and verifies the signature, the inclusion proofs and the commit chain itself, exactly as the pollis-verify group command does. No server computes the verdict. To check the same proof without relying on this page, download the pollis-verify tool (tags pollis-verify-v*, guide here). The only thing you have to trust is the log's pinned public key. It is an ML-DSA-44 (post-quantum) key, so its signatures over past history stay trustworthy even against a future quantum computer. It is published on the artifacts page, in the pollis-verify release body, and compiled into every app build.

The commit log was reset. On 28 and 29 October 2026 the publisher signed three commit-log tree heads (sizes 56, 113 and 129) that do not extend the log's earlier history. It had rebuilt the tree from a database table the server prunes, so the rebuilt tree no longer matched what it had already signed. The first tree is retired and left exactly where it was, so anyone can still check its consistent history up to size 137, and a signed reset statement lists the three forked heads. The commit log continues as a new tree, commit-log-2, that is only ever appended to. No message content was exposed, and no check the Pollis apps run was affected. What happened, and how to verify both trees.