Re: [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts]

The discussion highlights a significant shift in the minimum cost of joining the blockchain network, suggesting an increase from approximately $150 to $250. This change is seen as a positive development, aiming for full blocks and acknowledging the growth potential of blockchains. The email points out that even with inflation adjustments, the cost of nodes has become more accessible over time, with performances improving markedly. For instance, a node purchased in 2021 for around $330 (approximately $400 when adjusted for inflation) struggled with processing 700k blocks for weeks. Currently, similar capabilities are available for about $170, capable of completing Initial Block Download (IBD) in less than a day, depending on internet speed. Additionally, it mentions the possibility of acquiring fully validating pruned nodes for around $111, which can likely complete IBD in 2-3 days. There's also mention of the feasibility of using second-hand hardware to further reduce costs.

Core developers have made significant strides in increasing node efficiency, with the latest version being 250% faster than its predecessor. Moreover, there are unmerged optimizations that promise even greater improvements in future releases. Experiments conducted by the sender, including reindexing on a laptop and a battery-powered Raspberry Pi 5, demonstrate remarkable advancements in processing speeds, highlighting the unprecedented capability to conduct IBD from battery power alone.

The discussion also counters criticism about node setup costs and performance, arguing that market participation and use should be the metrics for success rather than online complaints. An example provided includes testing on an older Raspberry Pi 4b, which showed that even under default settings, IBD could be completed in less than three days for up to approximately 916k blocks.

Issues such as increased IBD times are attributed not to spam, as some suggest, but to outdated nodes or inefficient configurations. The necessity for better documentation and guidance for users is acknowledged, citing two GitHub pull requests aimed at addressing these concerns. The overarching message criticizes the negative focus on disagreements within the community, emphasizing the importance of constructive engagement and support to enhance the blockchain ecosystem.