Download — Bitcoin
Latest version: 0.21.1
Or choose your operating system
Bitcoin Core Release Signing Keys v0.11.0+ 01EA5486DE18A882D4C2684590C8019E36C2E964
Refresh expired keys using:
gpg —keyserver hkp://keyserver.ubuntu.com —refresh-keys
Check your bandwidth and space
Bitcoin Core requires a one-time download of about 400GB of data plus a further 5-10GB per month. By default, you will need to store all of that data, but if you enable pruning, you can store as little as 6GB total without sacrificing any security. For more information about setting up Bitcoin Core, please read the full node guide.
Verify your download
Download verification is optional but highly recommended. Click one of the lines below to view verification instructions for that platform.
Windows verification instructions
Click the link in the list above to download the release for your platform and wait for the file to finish downloading.
Download the list of cryptographic checksums: SHA256SUMS.asc
Open a terminal (command line prompt) and Change Directory (cd) to the folder you use for downloads. For example:
Run the following command to generate a checksum of the release file you downloaded. Replace ‘bitcoin-0.21.1-win64-setup-unsigned.exe’ with the name of the file you actually downloaded.
Ensure that the checksum produced by the command above matches one of the checksums listed in the checksums file you downloaded earlier. We recommend that you check every character of the two checksums to ensure they match. You can see the checksums you downloaded by running the following command:
If you haven’t previously installed GNU Privacy Guard (GPG) on your system, install it now or see other installation options.
Obtain a copy of the release signing key by running the following command:
The output of the command above should say that one key was imported, updated, has new signatures, or remained unchanged.
Check the output from the above command for the following text:
A line that starts with: gpg: Good signature
A complete line saying: Primary key fingerprint: 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964
The output from the verify command may contain a warning that the «key is not certified with a trusted signature.» This means that to fully verify your download, you need to ask people you trust to confirm that the key fingerprint printed above belongs to the Bitcoin Core Project’s release signing key.
Click the link in the list above to download the release for your platform and wait for the file to finish downloading.
Download the list of cryptographic checksums: SHA256SUMS.asc
Open a terminal (command line prompt) and Change Directory (cd) to the folder you use for downloads. For example:
Verify that the checksum of the release file is listed in the checksums file using the following command:
In the output produced by the above command, you can safely ignore any warnings and failures, but you must ensure the output lists «OK» after the name of the release file you downloaded. For example: bitcoin-0.21.1-osx.dmg: OK
If you haven’t previously installed GNU Privacy Guard (GPG) on your system, install it now or see other installation options.
Obtain a copy of the release signing key by running the following command:
The output of the command above should say that one key was imported, updated, has new signatures, or remained unchanged.
Check the output from the above command for the following text:
A line that starts with: gpg: Good signature
A complete line saying: Primary key fingerprint: 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964
The output from the verify command may contain a warning that the «key is not certified with a trusted signature.» This means that to fully verify your download, you need to ask people you trust to confirm that the key fingerprint printed above belongs to the Bitcoin Core Project’s release signing key.
Click the link in the list above to download the release for your platform and wait for the file to finish downloading.
Download the list of cryptographic checksums: SHA256SUMS.asc
Open a terminal (command line prompt) and Change Directory (cd) to the folder you use for downloads. For example:
Verify that the checksum of the release file is listed in the checksums file using the following command:
In the output produced by the above command, you can safely ignore any warnings and failures, but you must ensure the output lists «OK» after the name of the release file you downloaded. For example: bitcoin-0.21.1-x86_64-linux-gnu.tar.gz: OK
Obtain a copy of the release signing key by running the following command:
The output of the command above should say that one key was imported, updated, has new signatures, or remained unchanged.
Check the output from the above command for the following text:
A line that starts with: gpg: Good signature
A complete line saying: Primary key fingerprint: 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964
The output from the verify command may contain a warning that the «key is not certified with a trusted signature.» This means that to fully verify your download, you need to ask people you trust to confirm that the key fingerprint printed above belongs to the Bitcoin Core Project’s release signing key.
Snap package verification instructions
While the Snap packages use the deterministically generated executables, the Snap tool itself does not provide a streamlined way to reveal the contents of a Snap package. Thus, the Bitcoin Core project does not have the information necessary to help you verify the Bitcoin Core Snap packages.
Additional verification with reproducible builds
Experienced users who don’t mind performing additional steps can take advantage of Bitcoin Core’s reproducible builds and the signed checksums generated by contributors who perform those builds.
Reproducible builds allow anyone with a copy of Bitcoin Core’s MIT-licensed source code to build identical binaries to those distributed on this website (meaning the binaries will have the same cryptographic checksums as those provided by this website).
Verified reproduction is the result of multiple Bitcoin Core contributors each independently reproducing identical binaries as described above. These contributors cryptographically sign and publish the checksums of the binaries they generate.
Verifying that several contributors you trust all signed the same checksums distributed in the release checksums file will provide you with additional assurances over the preceding basic verification instructions. Alternatively, reproducing a binary for yourself will provide you with the highest level of assurance currently available. For more information, visit the project’s repository of trusted build process signatures.
Bitcoin Core is a community-driven free software project, released under the open source MIT license.
Источник
Bitcoin core mac os
macOS Build Guide
Updated for MacOS 11.2
This guide describes how to build bitcoind, command-line utilities, and GUI on macOS
Note: The following is for Intel Macs only!
The following dependencies are required:
| Library | Purpose | Description |
|---|---|---|
| automake | Build | Generate makefile |
| libtool | Build | Shared library support |
| pkg-config | Build | Configure compiler and linker flags |
| boost | Utility | Library for threading, data structures, etc |
| libevent | Networking | OS independent asynchronous networking |
The following dependencies are optional:
| Library | Purpose | Description |
|---|---|---|
| berkeley-db@4 | Berkeley DB | Wallet storage (only needed when wallet enabled) |
| qt@5 | GUI | GUI toolkit (only needed when GUI enabled) |
| qrencode | QR codes in GUI | Generating QR codes (only needed when GUI enabled) |
| zeromq | ZMQ notification | Allows generating ZMQ notifications (requires ZMQ version >= 4.0.0) |
| sqlite | SQLite DB | Wallet storage (only needed when wallet enabled) |
| miniupnpc | UPnP Support | Firewall-jumping support (needed for port mapping support) |
| libnatpmp | NAT-PMP Support | Firewall-jumping support (needed for port mapping support) |
| python3 | Testing | Python Interpreter (only needed when running the test suite) |
The following dependencies are optional packages required for deploying:
| Library | Purpose | Description |
|---|---|---|
| librsvg | Deploy Dependency | Library to render SVG files |
| ds_store | Deploy Dependency | Examine and modify .DS_Store files |
| mac_alias | Deploy Dependency | Generate/Read binary alias and bookmark records |
See dependencies.md for a complete overview.
The commands in this guide should be executed in a Terminal application. macOS comes with a built-in Terminal located in:
1. Xcode Command Line Tools
The Xcode Command Line Tools are a collection of build tools for macOS. These tools must be installed in order to build Bitcoin Core from source.
To install, run the following command from your terminal:
Upon running the command, you should see a popup appear. Click on Install to continue the installation process.
2. Homebrew Package Manager
Homebrew is a package manager for macOS that allows one to install packages from the command line easily. While several package managers are available for macOS, this guide will focus on Homebrew as it is the most popular. Since the examples in this guide which walk through the installation of a package will use Homebrew, it is recommended that you install it to follow along. Otherwise, you can adapt the commands to your package manager of choice.
To install the Homebrew package manager, see: https://brew.sh
Note: If you run into issues while installing Homebrew or pulling packages, refer to Homebrew’s troubleshooting page.
3. Install Required Dependencies
The first step is to download the required dependencies. These dependencies represent the packages required to get a barebones installation up and running. To install, run the following from your terminal:
4. Clone Bitcoin repository
git should already be installed by default on your system. Now that all the required dependencies are installed, let’s clone the Bitcoin Core repository to a directory. All build scripts and commands will run from this directory.
5. Install Optional Dependencies
It is not necessary to build wallet functionality to run bitcoind or bitcoin-qt . To enable legacy wallets, you must install berkeley-db@4 . To enable descriptor wallets, sqlite is required. Skip berkeley-db@4 if you intend to exclusively use descriptor wallets.
Legacy Wallet Support
berkeley-db@4 is required to enable support for legacy wallets. Skip if you don’t intend to use legacy wallets.
Descriptor Wallet Support
Note: Apple has included a useable sqlite package since macOS 10.14. You may not need to install this package.
sqlite is required to enable support for descriptor wallets. Skip if you don’t intend to use descriptor wallets.
Bitcoin Core includes a GUI built with the cross-platform Qt Framework. To compile the GUI, we need to install qt@5 . Skip if you don’t intend to use the GUI.
Ensure that the qt@5 package is installed, not the qt package. If ‘qt’ is installed, the build process will fail. if installed, remove the qt package with the following command:
Note: Building with Qt binaries downloaded from the Qt website is not officially supported. See the notes in #7714.
The GUI can encode addresses in a QR Code. To build in QR support for the GUI, install qrencode . Skip if not using the GUI or don’t want QR code functionality.
Port Mapping Dependencies
miniupnpc may be used for UPnP port mapping. Skip if you do not need this functionality.
libnatpmp may be used for NAT-PMP port mapping. Skip if you do not need this functionality.
Note: UPnP and NAT-PMP support will be compiled in and disabled by default. Check out the further configuration section for more information.
Support for ZMQ notifications requires the following dependency. Skip if you do not need ZMQ functionality.
ZMQ is automatically compiled in and enabled if the dependency is detected. Check out the further configuration section for more information.
For more information on ZMQ, see: zmq.md
Test Suite Dependencies
There is an included test suite that is useful for testing code changes when developing. To run the test suite (recommended), you will need to have Python 3 installed:
You can deploy a .dmg containing the Bitcoin Core application using make deploy . This command depends on a couple of python packages, so it is required that you have python installed.
Ensuring that python is installed, you can install the deploy dependencies by running the following commands in your terminal:
Building Bitcoin Core
There are many ways to configure Bitcoin Core, here are a few common examples:
Wallet (BDB + SQlite) Support, No GUI:
If berkeley-db@4 is installed, then legacy wallet support will be built. If berkeley-db@4 is not installed, then this will throw an error. If sqlite is installed, then descriptor wallet support will also be built. Additionally, this explicitly disables the GUI.
Wallet (only SQlite) and GUI Support:
This explicitly enables the GUI and disables legacy wallet support. If qt is not installed, this will throw an error. If sqlite is installed then descriptor wallet functionality will be built. If sqlite is not installed, then wallet functionality will be disabled.
No Wallet or GUI
You may want to dig deeper into the configuration options to achieve your desired behavior. Examine the output of the following command for a full list of configuration options:
After configuration, you are ready to compile. Run the following in your terminal to compile Bitcoin Core:
3. Deploy (optional)
You can also create a .dmg containing the .app bundle by running the following command:
Running Bitcoin Core
Bitcoin Core should now be available at ./src/bitcoind . If you compiled support for the GUI, it should be available at ./src/qt/bitcoin-qt .
The first time you run bitcoind or bitcoin-qt , it will start downloading the blockchain. This process could take many hours, or even days on slower than average systems.
By default, blockchain and wallet data files will be stored in:
Before running, you may create an empty configuration file:
Источник