Bitcoin Core with
Bitcoin Core is used by Counterparty to interact with the Bitcoin blockchain.
Depending on your OS and other preferences, download one of the binaries or source code from the link below. Optionally you can verify the file’s checksum and author’s PGP signature. These binaries are built deterministically.
Unlike the Linux binaries, the Windows packages are installers. Uninstall any older version and download and install a 32-bit or 64-bit version. A 32-bit version consumes slightly less memory and is recommended for regular desktop use.
C:\Program Files (x86)\Bitcoin
bitcoind.exe can be found in the
daemon subdirectory. This path can be manually added to the system PATH variable.
The Linux binaries are precompiled executables + dependencies, and they’re deployed by decompressing them into the desired location. Once that is done, they can be executed directly like so.
You may want to do one or more of the following optional steps:
* Move the binaries around.
* Edit your
PATH variable to allow you to execute the binaries (
bitcoin-qt) without specifying their path.
Your Bitcoin Core configuration file should match this:
rpcuser=bitcoinrpc rpcpassword=<password> server=1 daemon=1 rpctimeout=300 txindex=1 addrindex=1
- Choose a secure password.
- By default, on Windows, this file is located at
- By default, on Linux, this file is located at
~/.bitcoin/bitcoin.conf, and the permissions of the file should be set with
chmod 600 ~/.bitcoin/bitcoin.conf.
To run with the standard GUI interface, start Bitcoin Core (
./bitcoin-qt on Linux), and to run the daemon, execute
bitcoind. A full list of options can be obtained like this:
* Bitcoin Core: go to
Help > Command-line options or execute
* bitcoind: run
./bitcoind --help (
bitcoind.exe -help on Windows)
bitcoin-cli to interact with Bitcoin Core.
Usage on Testnet
For testnet use, add
testnet=1 to a separate copy of the above configuration file or run bitcoind with
-testnet from a script or the console. Examples:
./bitcoind -testnet - start bitcoind on testnet using the default configuration file (blockchain data would be stored in the default data path under
bitcoind.exe -testnet -datadir=E:\testing\testnet-blockchain - use the default configuration file, run on testnet, but place blockchain data in the specified data directory
bitcoin-qt.exe -conf=E:\testing\testnet.conf - start Bitcoin Core GUI and service using a custom configuration file (which presumably cointains
testnet=1 and other custom options that justify the creation of a testnet-specific configuration file)
To interact with a testnet instance of Bitcoin Core, use
bitcoin-cli with the same
conf options that were used to start it.
Leveraging existing blockchain data from a higher Bitcoin Core version
Existing Bitcoin Core users with blockchain data created by a higher version of the official Bitcoin Core may not be able to reuse their blockchain data from a lower version of Bitcoin Core because higher Bitcoin Core releases may have a database (or wallet, if used) format that older Bitcoin Core versions cannot recognize.
This changes from one Bitcoin Core version to another, so please check Bitcoin Core Release Notes for database (and wallet, if applicable) format changes.
In cases where an in-place change is not possible or desired, you can setup a separate Bitcoin Core instance and add
adddnode=<IP-address-of-newer-version-on-LAN> to the new instance’s bitcoin.conf.