Author: Jeff Garzik 2015-05-12 16:05:44
Published on: 2015-05-12T16:05:44+00:00
The email thread dated May 12, 2015, discusses the proposal for a hybrid option in nodes that would reduce storage needs on a node while allowing it to continue validating all transactions. The proposed solution involves flipping the --no-wallet toggle, selecting a section of the blockchain to store fully (percentage-based), and pruning all sections not included in this selection. This approach is similar to how Koorde works, where the network decides which sections to retrieve. The user prompts the node to store a particular percentage of the blockchain, and it selects the least-occurring options from its peers and their peers (if secure). This solution should have little impact on security and would allow for a retroactive --max-size flag, where the node prunes until it reaches the specified size, continuing to prune over time while keeping to the sections defined by the network. However, some concerns were raised regarding side effects or network vulnerabilities that this solution might introduce. While it may not be Sybil resistant, it is no less so than a fully pruned node. Overall, the proposal aims to address concerns about increasing storage needs due to the 20MB step and switching to pruned nodes partially, reducing network security. It seeks to provide a solution that retains full validation capabilities while distributing the full copy among many nodes, significantly reducing storage needs on a node. Jeff Garzik, a Bitcoin core developer and open-source evangelist, was part of the email thread.
Updated on: 2023-06-09T20:52:07.919518+00:00