Full Nodes & Core Wallets

Bitcoin Download, Installation and Release Verification

Get Bitcoin for Windows, check release hashes and PGP signatures, and learn what this peer-to-peer cash system involves before you install.

Free Open source Windows: Yes Updated 30 Oct 2026
10 min read Last update 30 Oct 2026 github.com/bitcoin-core/guix.sigs

Bitcoin is a peer-to-peer electronic cash system, and this page is for Windows users who want to get the software from a trustworthy source and confirm that the file they run matches what the project published. The program is free and open source, and it sits in our Full Nodes & Core Wallets category.

Because Bitcoin is a payment network, the software you install is tied closely to funds and network trust. The project publishes hash lists, detached PGP signatures and build attestations for each release, so you can check that your binary matches what the signers produced. This page explains those files, walks through installing the Windows build or installer, and points out what to check before you run anything.

02

What Is Bitcoin and How Does It Work?

Bitcoin is a peer-to-peer electronic cash system. Instead of relying on a bank or a payment company to keep records, computers running the software connect directly to one another and share the same transaction history. Each participant that keeps a full copy of that history is called a node, and the network is maintained by many such nodes working together.

The unit of account on the network is bitcoin, usually written as BTC. Transactions are grouped into blocks, and new blocks are added through mining. The mining algorithm used by the network is SHA-256, the same hashing function that appears throughout the verification files that come with every release.

For a Windows user, the practical takeaway is that the software is more than a single app. It is part of a network, so the quality of the release file you install matters, and the way the project signs and checks its builds is a large part of why people can trust it.

03

Who Bitcoin Is For

Bitcoin software suits users who want to run their own node rather than rely on a third party to read the blockchain. A developer might run a node to test applications against the real network. A privacy-minded user might prefer to check transactions against their own copy of the history. A technically curious person might simply want to see how a peer-to-peer ledger behaves on an everyday Windows PC.

It is also useful for people who care about software supply chains. If you manage a small team and want to confirm that every machine runs the same verified build, the hash lists and attestations give you a concrete basis for that check. Engineers who review open source projects can use the same files to study how releases are produced.

The software is less suited to people who want a quick, consumer-style app with no setup. Verifying a download and understanding a node's role takes some patience, and the material on this page assumes you are ready to read technical documentation and follow instructions carefully.

04

Understanding Hashes, Signatures and Build Attestations

A hash is a fixed-length fingerprint generated from a file. If even one byte of the file changes, the hash changes completely. SHA-256 is the algorithm used for the hash lists that come with Bitcoin releases. When you compute the SHA-256 value of your downloaded file and find the same value in the official list, you know the file is identical to the one the list was built from.

A signature answers a different question: who vouched for the list? A PGP signature is created with a private key that only the signer holds. The matching public key lets anyone confirm that the signer approved that exact list. Detached signatures keep the signature in a separate file, which means the hash list stays readable on its own.

Build attestations add one more step. An attestation records that a specific signer built and checked a particular version tag. Several signers can attest to the same release, so no single person has to be trusted completely. Over time, a release that many independent signers have attested to is harder to tamper with unnoticed than one that rests on a single party.

05

Key features

Per-version build attestations

For each release tag, the project stores attestations that record which signer built and checked that version. Each attestation sits in a folder named after the version and the signer, which makes it straightforward to see who vouched for a given release and to compare the record against the file you downloaded.

First-stage hash list

The noncodesigned.SHA256SUMS file lists SHA-256 hashes of the binaries produced by the first build stage for a given version. Comparing a file's hash with this list tells you whether it matches that first stage output, which is useful when you want to follow the build chain step by step.

Full release hash list

The all.SHA256SUMS file is the one to check your Windows release against. It covers all the binaries uploaded to the official website, produced by the second build stage. If you only check one file, this is the list to use, because it matches the packages you are actually meant to install.

Detached PGP signatures

Both hash lists come with separate .asc signature files. A detached signature sits next to the list rather than inside it, so you can verify the list's authenticity with a PGP tool without changing the list itself. This adds a second layer of assurance on top of the hash comparison.

Builder keys directory

The project keeps the PGP public keys of its signers in a builder-keys folder, with one key file per signer. Anyone who wants to take part in builds and contribute attestations can submit a key through a pull request, which keeps the list of trusted signers visible and reviewable.

CI test scripts

A contrib folder holds the scripts used in the continuous integration tests. Reading these scripts shows how the project checks its builds automatically, and developers who want to reproduce the testing process can start from the same tools the maintainers use.
06

Supported coins

The software is associated with Bitcoin (BTC) and uses the SHA-256 mining algorithm. Its release materials are written around the Bitcoin network, so the program is aimed at people who want to run or interact with that network rather than other chains.

07

How to install Bitcoin on Windows

  1. 1

    Get the file from an official source

    Download the Windows build or installer only from the official website or from the project's GitHub Releases page. Avoid mirrors, forum links and file-sharing sites, even when they appear near the top of a search. Note the exact version number on the release page before you continue, because the hash lists are tied to a specific version.

  2. 2

    Download the matching hash lists

    On the same release, save the all.SHA256SUMS file and its all.SHA256SUMS.asc signature. These are the files you will use to confirm that your Windows binary is the one the project published. Keep them in the same folder as the installer so the steps that follow are easier to follow.

  3. 3

    Verify the installer

    Compute the SHA-256 hash of the installer and find the matching line in all.SHA256SUMS. Then check the detached signature against the signer's public key from the builder-keys folder. Only proceed to installation once both checks pass. If either check fails, do not run the file, and report the mismatch through the project's channels.

  4. Run the installer and launch

    Run the verified installer or Windows build and follow the on-screen prompts. Choose an install location with enough free disk space, since a full node stores a growing copy of the network's history. After installation, open the program once to confirm it starts before you change any settings or connect it to the network.

08

How to use Bitcoin

Once the program is installed, the most useful habit is to keep verification in your routine. Each time you update to a new version, repeat the same check before you run the new file. The steps below show how to compare a downloaded file with the official hash list on Windows.

  1. Open the folder that contains your installer and the all.SHA256SUMS file.
  2. Open PowerShell in that folder and run Get-FileHash with the SHA256 algorithm on the installer file.
  3. Copy the hash value that PowerShell prints, ignoring any spaces or capital letter differences.
  4. Open all.SHA256SUMS in a plain text editor and search for the installer's file name.
  5. Confirm that the hash on the matching line is identical to the value from step three.
  6. Check the detached signature for all.SHA256SUMS using your PGP tool and the appropriate signer key.
  7. Only after both checks pass, run the installer or launch the program from its install folder.

If you keep several versions on the same machine, label each folder with its version number. That way you always know which hash list belongs to which binary, and you avoid mixing up files from different releases.

09

Pros & cons

Pros
  • Free and open source, so the code can be reviewed by anyone who wants to read it
  • Release files include SHA-256 hash lists and detached PGP signatures for checking downloads
  • Build attestations from named signers give a transparent record for each version
  • Available as a Windows build or installer, with macOS listed as a supported platform
  • Verification files cover the full set of binaries uploaded to the official website
Cons
  • The verification workflow is technical and assumes some familiarity with hashes and PGP
  • Running a full node requires local disk space and time to keep a copy of the network history
  • The program is designed for people who want to run network software, not a simple one-click app
  • Security depends on the user actually completing the checks, which takes extra effort
10

Is Bitcoin safe?

Bitcoin is free and open source, but it is network software that handles real value, so treat every download with care. Get the Windows build or installer only from the official website or the project's GitHub Releases page. Compute the SHA-256 hash of the file and compare it with all.SHA256SUMS, then check the detached PGP signature before running anything. The project's code was last updated on 2026-10-30, so check the latest version on the official website before you install. Never enter a seed phrase or private key on a third-party website, and be suspicious of any site or message that asks for one.

  • Official source only. Download from github.com/bitcoin-core/guix.sigs. Ignore ads and lookalike domains.
  • Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
  • Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
11

Alternatives

Bitcoin is the reference network for the Bitcoin (BTC) chain, and its software is built around that network alone. Dogecoin Core and Litecoin Core follow a similar full node and wallet model, but each serves its own coin and network rules. Monero CLI works differently: it is a daemon and console wallet for Monero, which focuses on privacy. Namecoin Core runs a node and wallet for Namecoin, and it adds decentralized .bit domains to the mix.

If your goal is to run a node for Bitcoin specifically, this program is the direct choice. If you want a different chain or a different set of features, the alternatives above are better matches. Compare the release verification process as well, since the way each project publishes hashes and signatures can differ.

12

Specifications

Price
Free
Type
Open source
License
—
Latest version
—
Last update
30 Oct 2026
Windows support
Yes (Windows build or installer)
Source code
github.com/bitcoin-core/guix.sigs
13

Frequently asked questions

Yes. Bitcoin is free and open source, and the Windows build or installer costs nothing to download. The software itself carries no license fee. Use the official channels listed in the installation and safety sections to get the file, and verify it before you run it.

It can be, as long as you verify the file before running it. Compare the installer's SHA-256 hash with the all.SHA256SUMS list and check the detached PGP signature. Only install a file that passes both checks, and avoid any copy that comes from an unofficial source or a third-party download site.

Start by computing the SHA-256 hash of the installer using PowerShell's Get-FileHash command. Then find the matching line in all.SHA256SUMS and confirm the two values are identical. Finally, check the detached signature with your PGP tool. The full steps are listed in the how-to section of this page.

The noncodesigned.SHA256SUMS file lists hashes from the first build stage for a given version. The all.SHA256SUMS file covers the second stage and includes all the binaries uploaded to the official website. For checking a release binary, the all.SHA256SUMS file is the one to use.

A build attestation is a record that a named signer built and checked a specific version tag of the software. Each attestation is stored in a folder labeled with the version and the signer. Multiple signers can attest to the same release, which makes it harder for one party to alter a build without others noticing.

The software is associated with Bitcoin (BTC) and uses the SHA-256 mining algorithm. It is designed for the Bitcoin network, so it does not work as a wallet or node for other chains. If you want to use a different coin, look at the alternatives listed on this page.

Yes, macOS is listed as a supported platform alongside Windows. The verification method is the same in principle, but the commands differ. On macOS you would use a terminal tool to compute the hash, while the PGP check works in the same way across systems.

A seed phrase is a list of words that can restore a wallet, so it should never be shared or typed into a website. Keep it offline, written on paper or in a secure physical location. Never enter it on a third-party page, even if the page claims to be an official support service.

14

Verdict

Bitcoin suits Windows users who want to run network software they can verify and review. Its release process, with SHA-256 hash lists, detached PGP signatures and named build attestations, gives careful users a clear way to check what they install. It is not an easy consumer app, and it asks for patience with technical steps. If you are ready to verify each download and treat your keys with care, it is a solid choice. If you want a simple tool with no setup, look for something designed for casual use.

Download now