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-06 15:36:38 +00:00
Code Issues Releases Wiki Activity

updating banlist file extension in /.bitcoin/testnet3

Browse Source 
The instructions state that updating banlist in /.bitcoin/testnet3 is the dat file.
I think the file type should be json.
This commit is contained in:
Grisha Lyukshin 2022-01-17 16:59:45 -08:00 committed by GitHub
parent ff4d5167f8
commit 5744135fb1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
03_2_Knowing_Your_Bitcoin_Setup.md
View File

@ -16,7 +16,7 @@ The setup guides in [Chapter Two: Creating a Bitcoin-Core VPS](02_0_Setting_Up_a
Moving back to your ~/.bitcoin directory, you'll find that the testnet3 directory contains all of the guts: Moving back to your ~/.bitcoin directory, you'll find that the testnet3 directory contains all of the guts:
``` ```
$ ls ~/.bitcoin/testnet3 $ ls ~/.bitcoin/testnet3
banlist.dat blocks debug.log mempool.dat peers.dat banlist.json blocks debug.log mempool.dat peers.dat
bitcoind.pid chainstate fee_estimates.dat onion_private_key wallets bitcoind.pid chainstate fee_estimates.dat onion_private_key wallets
``` ```
You shouldn't mess with most of these files and directories — particularly not the `blocks` and `chainstate` directories, which contain all of the blockchain data, and the information in your `wallets` directory, which contains your personal wallet. However, do take careful note of the `debug.log` file, which you should refer to if you ever have problems with your setup. You shouldn't mess with most of these files and directories — particularly not the `blocks` and `chainstate` directories, which contain all of the blockchain data, and the information in your `wallets` directory, which contains your personal wallet. However, do take careful note of the `debug.log` file, which you should refer to if you ever have problems with your setup.