From f6c5b813075cae4228d241a3567e70b210504749 Mon Sep 17 00:00:00 2001 From: mtg0001 <106211915+mtg0001@users.noreply.github.com> Date: Tue, 4 Aug 2026 10:18:01 -0300 Subject: Add release verification tooling (#108) Co-authored-by: Gilcimar Duarte --- README.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 6601384..6446b3d 100644 --- a/README.md +++ b/README.md @@ -49,13 +49,30 @@ configuration — it connects automatically and starts syncing. **Windows:** extract the `-windows.zip` and run `Bitflash.exe`. -Every release ships a `SHA256SUMS` covering both assets. Verifying takes a second +Every release ships a `SHA256SUMS` covering the assets. Verifying takes a second and is worth doing: ```bash sha256sum -c SHA256SUMS ``` +For newer signed releases, verify the checksum file itself first: + +```bash +gpg --verify SHA256SUMS.asc SHA256SUMS +sha256sum -c SHA256SUMS +``` + +The helper below downloads the release assets, verifies `SHA256SUMS.asc` when it +is present, then checks the hashes: + +```bash +scripts/verify-release.sh latest +``` + +See [release verification](docs/release-verification.md) for the full release +audit flow and the maintainer signing step. + **Keep your node current.** Consensus rules have changed since the first releases — 1.2.1 fixed a bug that let anyone spend anyone's coins, and 1.2.2 added a per-block signature-operation cap. A node on an older build will accept -- cgit v1.2.3