Bitcoin node starts the first blockchain download every time it starts
The Bitcoin node is a crucial component of the Bitcoin network and is responsible for downloading and processing new blocks. In this article, we will show how to configure a pruned Bitcoin node with the following settings:
- Pruning: The number of blocks that will be discarded during the first blockchain download
- Disk cache: A cache used to store frequently accessed files
- Protocol version: The version of the Bitcoin protocol used by the node
- Network connection settings:
+ Server: A single server is configured for this example
+ RPC username and password: A test username and password are provided
- File system configuration:
+ Data directory: A specific directory where the node stores its data
Pruning configuration
The pruning configuration determines how many blocks will be discarded during the first blockchain download. By setting prune=550 we are telling the node to discard 550 blocks.
{
"prune": 550,
...
}
This is a high value and most users will not need to adjust it. However, if you are having problems with a congested or slow network, reducing the pruning value may improve performance.
Disk Cache Configuration
The disk cache configuration determines how frequently the node checks the disk for new blocks before downloading them from the network. By setting dbcache=6192 we are telling the node to store 6192 blocks on disk before checking the network.
{
"dbcache": 6192,
...
}
This is a high value and most users will not need to adjust it. However, if you are having problems with a full or slow disk, reducing the database cache size may improve performance.
Protocol version configuration
The protocol version configuration determines which Bitcoin protocol version is used by the node. By setting rpcprotocol=3 we are telling the node to use version 3 of the Bitcoin protocol.
{
"rpcprotocol": 3,
...
}
This is a default value and most users will not need to adjust it.
Network connection settings
The network connection settings determine which server(s) are used for this example. By setting server=1 we are telling the node to use a single server.
{
"server": 1,
...
}
This is a default value and most users will not need to adjust it.
File system configuration
The file system configuration determines where the node stores its data. By setting datadir=/root/.bitcoin/blocks we tell the node to store its data in the /root/.bitcoin/blocks directory.
{
"datadir": "/root/.bitcoin/blocks",
...
}
This is a default value and most users will not need to adjust it.
Testing the Node
To test the pruned Bitcoin node with the given configuration, you can use the following commands:
- Start the node by running
service bitcoin-node start
- Connect to the node using
bitcoin-cli getblockcount(this will download a block and display its number)
- Use
bitcoin-cli getblocks(this will download all blocks in the blockchain)
Note: Make sure you have bitcoin-cli installed on your system before testing the node.
Conclusion
The pruned Bitcoin node with the given configuration is ready to process initial blockchain downloads. By adjusting the pruning value, disk cache size, protocol version, and network connection settings, you can optimize the node’s performance for your specific use case.