A more detailed explanation can be found here
bitcoind
bitcoin.conf
make bitcoind
to start bitcoind
bitcoind
to finish IBD (initial block download)make health
after IBD is finished to verify successful setup. (Make sure you have curl
installed)The docker-compose file under bitcoind
folder uses ruimarnho's image. Configuration is based on the local config file under the ./conf/bitcoin.conf
path.
We recommend storing the bitcoind's RPC credentials in ~/.netrc
.
The ~/.netrc
should follow the format below.
machine <Use 127.0.0.1 if run locally> login <Put RPC user name here> password <Put RPC password here>
Assume (1) ~/.netrc
uses the same credential in your bitcoin.conf
AND (2) bitcoind
is up-to-date and running in good health, you should observe the following output log by executing the make health
command.
{
"result": {
"chain": "main",
"blocks": 768376,
"headers": 768376,
"bestblockhash": "000000000000000000046c59ca7ec947dbb0008151e6d3aa1a065c5638305040",
"difficulty": 35364065900457.12,
"time": 1671639089,
"mediantime": 1671636501,
"verificationprogress": 0.9999976758420501,
"initialblockdownload": false,
"chainwork": "00000000000000000000000000000000000000003c00a6183801cbf2f8b3660e",
"size_on_disk": 505088531797,
"pruned": false,
"warnings": ""
},
"error": null,
"id": "curltest"
}
fulcrum
We chose Fulcrum based on Server Performance Guide
make download
to download the Fulcrum executable from its official website.make clean
to clean up downloaded files./conf/fulcrum.conf
make fulcrum
to start fulcrumIf everything is set up correctly and after you click Test Connection, you should see something like this:
Connected to Fulcrum 1.9.0 on protocol version 1.4
Batched RPC enabled.
Server Banner: Connected to a Fulcrum 1.9.0 server
TODO
Make sure you have created an SSL certificate for the fulcrum server. Otherwise, create your SSL certificate using the following commands:
openssl
openssl genrsa -des3 -out server.pass.key 2048
openssl rsa -in server.pass.key -out server.key
rm server.pass.key
openssl req -new -key server.key -out server.csr
openssl x509 -req -sha256 -days 365 -in server.csr -signkey server.key -out server.crt
rm server.csr
server*
to certs
folder.Please submit issues/questions here.