Running A Full Node
5 stars based on
33 reviews
This release focuses on the safety of the P2P network as a precaution against potential future network forks, as well as bringing bug fixes, optimisations and improvements to the 0. A number of changes to the way Bitcoin Bitcoin core connections deals with peer connections and invalid bitcoin core connections have been made, as a safety precaution against bitcoin core connections forks and misbehaving peers.
Unrequested blocks with less work than the minimum-chain-work are now no longer processed even if they have more work than the tip a potential issue during IBD where bitcoin core connections tip may have low-work.
This prevents peers wasting the resources of a node. Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected. For a bitcoin core connections outbound peer, we now check whether their best known block has at least as much work as our tip.
If after two minutes their best known block bitcoin core connections insufficient work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable number of nodes not known to be on bogus chains. Outbound non-manual peers that serve us block headers that are already known to be invalid other than compact block announcements, because BIP explicitly permits nodes to relay compact blocks before fully validating them will now be disconnected.
If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect the peer that least recently announced bitcoin core connections new block. The set of all known invalid-themselves blocks i. This ensures that everything that descends from an invalid block is marked as bitcoin core connections.
The currentblocksize value in getmininginfo has been removed. This is a security measure as well as prevents dangerous user mistakes. The behaviour is unchanged when an empty string is provided. Though blockmaxweight has been preferred for limiting the size of blocks returned by getblocktemplate since 0. Using this option resulted in a few UI issues as well as non-optimal fee selection bitcoin core connections ever-so-slightly worse performance, and has thus now been deprecated.
Further, the blockmaxsize option is now used only bitcoin core connections calculate an implied blockmaxweight, instead of limiting block size directly. Any miners who wish to limit their blocks by size, instead of by weight, will have to do so manually by removing transactions from their block template directly. The GUI settings will now be written to guisettings. This can be used to retroactively troubleshoot issues due to the GUI settings. Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing issues when both were opened simultaneously.
It is no longer possible to open copies of the same wallet. A hidden debug argument -minimumchainwork has been added bitcoin core connections allow a custom minimum work value to be used when validating a chain. Please see the release notes for details. To download, please visit the download page. Notable changes Network fork safety enhancements RPC changes Miner block size limiting deprecated GUI settings backed up on reset Duplicate wallets disallowed Debug -minimumchainwork argument added Conclusion Hashes for verification.
Recommended View all posts Bitcoin Core 0.
