
The setup of a new Bitcoin Core node remains a hot-button issue, with many users expressing frustration over lengthy synchronization times, even with the 5 GB pruning feature. This ongoing debate has significant implications for software efficiency and user experience.
Reports from various forums indicate that even with pruning, Bitcoin Core nodes must still download the entire blockchain before it can delete old blocks. Many users feel misled by the pruning feature, anticipating quicker setups. One frustrated user shared, "It's been going for days; I thought it only downloaded a subset."
Community feedback highlights three key themes:
Hardware Impact: The choice of hardware drastically affects sync times. One user reported that their Raspberry Pi 4 took two weeks to download the full blockchain. In contrast, another stated they synced a Pi 5 with NVMe storage in just 36 hours.
Configuration Tips: Experts recommend adjusting configurations, such as adding an "assumevalid" line to speed up the verification of older transactions.
Alternative Solutions: Several users suggest switching to Bitcoin Knots for a potentially better experience. "Use Bitcoin Knots. More configurable," remarked one participant.
"Node must verify all blocks then delete old ones." This captures the essence of the ongoing syncing debates. The consensus appears to suggest that while pruning can reduce storage needs, it does not enhance sync speeds.
The sentiment among community members veers towards pessimism. Many express disappointment that their expectations for pruned nodes do not align with the actual performance. As one user put it, "Itโs thrashing the HD." The toll on hardware during the sync process adds to this growing frustration.
๐ซ Users are questioning the effectiveness of the Bitcoin Core node sync process.
โณ Syncing on configurations with 1GB of pruning can often complete within 24 hours, contrary to longer times for larger setups.
๐ Switching to options like Bitcoin Knots is gaining traction among users seeking faster results.
As discussions unfold, developers may need to tackle these performance issues head-on to adapt to community feedback and competitive pressures. Could significant updates be on the horizon to streamline the user experience? The answer remains to be seen, but user troubles serve as a catalyst for potential improvements.