flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-07 16:06:26 +00:00
Code Issues Releases Wiki Activity

Various updates

Browse Source 
Some courtesy @SimoneBovi and PR #114
This commit is contained in:
Shannon Appelcline 2020-05-19 11:02:48 -10:00 committed by GitHub
parent 85e77954b1
commit 9635b0fa37
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
02_1_Setting_Up_a_Bitcoin-Core_VPS_by_Hand.md
View File

@ -263,7 +263,7 @@ alias btcdir="cd ~/.bitcoin/" #linux default bitcoind path
alias bc="bitcoin-cli" alias bc="bitcoin-cli"
alias bd="bitcoind" alias bd="bitcoind"
alias btcinfo='bitcoin-cli getwalletinfo | egrep "\"balance\""; bitcoin-cli getnetworkinginfo | egrep "\"version\"|connections"; bitcoin-cli getmininginfo | egrep "\"blocks\"|errors"' alias btcinfo='bitcoin-cli getwalletinfo | egrep "\"balance\""; bitcoin-cli getnetworkinginfo | egrep "\"version\"|connections"; bitcoin-cli getmininginfo | egrep "\"blocks\"|errors"'
# next alias not working; blockexplorer.com is not redirecting properly # Currently not working. We keep losing explorers that can tell us the latest block on testnet
# alias btcblock="echo \\\`bitcoin-cli getblockcount 2>&1\\\`/\\\`wget -O - http://blockexplorer.com/testnet/q/getblockcount 2> /dev/null | cut -d : -f2 | rev | cut -c 2- | rev\\\`" # alias btcblock="echo \\\`bitcoin-cli getblockcount 2>&1\\\`/\\\`wget -O - http://blockexplorer.com/testnet/q/getblockcount 2> /dev/null | cut -d : -f2 | rev | cut -c 2- | rev\\\`"
EOF EOF
``` ```
@ -304,9 +304,9 @@ $ source ~/.bash_profile
We suggest setting up two variables to make this installation more automatic. We suggest setting up two variables to make this installation more automatic.
The first variable, $BITCOIN, should be set to the current version of Bitcoin. It was 0.16.2 when we wrote this. The second will then automatically generate a truncated form used by some of the files. The first variable, $BITCOIN, should be set to the current version of Bitcoin. It was 0.18.0 when we wrote this. The second will then automatically generate a truncated form used by some of the files.
``` ```
$ export BITCOIN=bitcoin-core-0.16.2 $ export BITCOIN=bitcoin-core-0.18.0
$ export BITCOINPLAIN=`echo $BITCOIN | sed 's/bitcoin-core/bitcoin/'` $ export BITCOINPLAIN=`echo $BITCOIN | sed 's/bitcoin-core/bitcoin/'`
``` ```
@ -410,6 +410,10 @@ After all of that, starting the Bitcoin daemon is anticlimatically simple:
``` ```
$ /usr/local/bin/bitcoind -daemon $ /usr/local/bin/bitcoind -daemon
``` ```
If everything is fine you should see the following message:
```
Bitcoin Core starting
```
You should also add a crontab entry , so that the bitcoin daemon starts up whenever your VPS restarts: You should also add a crontab entry , so that the bitcoin daemon starts up whenever your VPS restarts:
``` ```
$ ( /usr/bin/crontab -l -u user1 2>/dev/null; echo "@reboot /usr/local/bin/bitcoind -daemon" ) | /usr/bin/crontab -u user1 - $ ( /usr/bin/crontab -l -u user1 2>/dev/null; echo "@reboot /usr/local/bin/bitcoind -daemon" ) | /usr/bin/crontab -u user1 -
@ -419,11 +423,11 @@ $ ( /usr/bin/crontab -l -u user1 2>/dev/null; echo "@reboot /usr/local/bin/bitco
So now you probably want to play with Bitcoin! So now you probably want to play with Bitcoin!
But wait, your Bitcoin daemon is probably still downloading blocks. This alias, from your .bash configuration will tell you how things are going: But wait, your Bitcoin daemon is probably still downloading blocks. This alias, from your .bash configuration will tell you which blocks have been downloaded:
``` ```
$ btcblock $ btcblock
``` ```
0.15.1 is quite fast to download blocks, but it might still take an hour to download the unpruned testnet. It might be time for a few more espressos. 0.18.0 is quite fast to download blocks, but it might still take an hour to download the unpruned testnet. It might be time for a few more espressos.
> :link: **TESTNET vs MAINNET:** An unpruned mainnet will take hours longer. > :link: **TESTNET vs MAINNET:** An unpruned mainnet will take hours longer.