How to verify a release

A version should connect the app, source, signature and test results.

What belongs next to a download

List the platform, version, date, distribution channel, SHA-256 and signature-verification method. A public link appears only for an existing artifact. An App Store label is not a substitute for a real app listing.

Repeat the build

Reproducibility instructions pin source commit/tree, toolchain, dependency locks, commands and differences between signed and unsigned artifacts. An independent reproduction is recorded separately. One successful local build does not earn that badge.

What is available here

You can download the local documentation kit and read the verification snapshot. Mobile binaries and a miner release are not included. Prepared release templates are not a signed release.

Verification center↗