Skip to content

Add release artifacts documentation page #1221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PauloAAlmeida wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add release artifacts documentation page #1221

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f213f68
Add release artifacts documentation page
PauloAAlmeida Feb 10, 2026
b8c7811
Address review feedback
PauloAAlmeida Feb 11, 2026
4a0db94
doc: update -debug description
PauloAAlmeida Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions _posts/en/pages/2026-02-10-release-artifacts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
title: Release Artifacts
name: release-artifacts
type: pages
layout: page
lang: en
permalink: /en/release-artifacts/
version: 1
---

Bitcoin Core release files are hosted at [https://bitcoincore.org/bin/](https://bitcoincore.org/bin/) and distributed via torrent.

## Build Suffixes

- **Standard Binaries** (`.tar.gz`, `.zip`, `-setup.exe`): Production-ready, signed binaries for general use.
- **`-debug`**: Includes symbols for backtrace generation. Larger file size and reduced performance.
- **`-unsigned`**: Raw Guix build outputs. Used to audit reproducibility against signed releases.
- **`-codesigning`**: Intermediate artifacts for macOS/Windows signing ceremonies. Not for end-users.

@willcl-ark willcl-ark Feb 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually these artefacts are all signed via the hashes SHA256SUMS file.

Perhaps update in general, and on L25 which also seems to imply only release files are hashed and signed?

@PauloAAlmeida PauloAAlmeida Feb 11, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Removed "signed" from the standard binaries description and updated SHA256SUMS to clarify it covers all artifacts.

- **Source**: `bitcoin-<version>.tar.gz` (no platform string). For manual compilation.

## Verification Files

| File | Description |
|------|-------------|
| `SHA256SUMS` | Manifest of all release file hashes. |
| `SHA256SUMS.asc` | Detached GPG signatures from trusted signers. |
| `SHA256SUMS.ots` | OpenTimestamps proof. |

For step-by-step verification instructions, see the [download page](/en/download/).