43 lines
1.6 KiB
Text
43 lines
1.6 KiB
Text
Using bitcoin utilities on Fedora, CentOS and Red Hat Enterprise Linux
|
|
======================================================================
|
|
|
|
The bitcoin-cli and bitcoin-tx commands allow you to communicate with a running
|
|
Bitcoin daemon on a local or remote host.
|
|
|
|
Configuration
|
|
-------------
|
|
|
|
By default bitcoin-cli looks for configuration at /etc/bitcoin/bitcoin.conf.
|
|
This must be readable only by users authorized to communicate with bitcoind.
|
|
See the README file included with bitcoin-server for further details.
|
|
|
|
Berkeley DB
|
|
-----------
|
|
|
|
On all platforms, including RHEL/CentOS/Fedora and the upstream build, bitcoin
|
|
uses Berkeley DB 4.8.
|
|
Oracle makes clear that binary compatibility is not guaranteed even between minor
|
|
releases of Berkeley DB. This has implications if you move your wallet to and
|
|
from a system with a different Berkeley DB version.
|
|
|
|
It is strongly recommended that if you change Berkeley DB versions you first
|
|
dump your wallet from the old system into a text file, and then import the
|
|
wallet into the new system.
|
|
|
|
To dump or import a wallet from a Bitcoin daemon, you will need to use the
|
|
bitcoin-cli utility.
|
|
|
|
To dump your wallet on the old system, enter the command:
|
|
|
|
bitcoin-wallet dumpwallet path/to/filename.txt
|
|
|
|
Copy filename.txt from the old system to the new system, being aware that it
|
|
is not encrypted and taking appropriate precautions.
|
|
|
|
To import your wallet on the new system, enter the command:
|
|
|
|
bitcoin-wallet importwallet path/to/filename.txt
|
|
|
|
Bitcoin will automatically begin rescanning the block chain after the import is
|
|
complete. The rescan will take several minutes, depending on the speed of the
|
|
system's CPU and hard drives.
|