Reducing Bitcoin Full Node Storage Without Consensus Changes

This new version maintains compatibility with the original Bitcoin consensus but introduces several significant enhancements primarily around storage and database management. The key changes include switching from LevelDB to RocksDB for improved handling of chainstate and database-backed indexes, introducing compressed block storage using Zstandard to reduce disk space usage, and implementing parallel prevout fetching during the ConnectBlock process to enhance performance. Additional user-selectable relay-policy profiles have been added to allow users to tailor local relay and mempool policy without affecting consensus rules.

In terms of performance metrics and resource utilization, BitcoinRocks has demonstrated substantial improvements in storage efficiency. Through extensive testing, including a cross-check of all main-chain blocks against Bitcoin Core and a full sync audit, it was confirmed that there were no discrepancies in the data, and both implementations converged on the same live chain tip. The total storage requirement for BitcoinRocks, including optional indexes, is significantly lower than its uncompressed counterpart, highlighting a nearly 20% reduction in disk space usage due to compression alone. Furthermore, the implementation aims to balance RAM usage by optimizing synchronization times from Genesis without overly taxing system resources, achieving a full sync in about 30 hours while maintaining system responsiveness.

Regarding the ongoing development and future benchmarks, the programmer has outlined plans to further evaluate the performance, specifically how the system handles access to historically compressed data. This is seen as a potential strength of the RocksDB implementation. Additionally, they are aware of recent developments in Bitcoin Core, such as proposals to reduce the size of the txindex database, which could further improve storage efficiency and support pruning strategies that align with typical user needs for historical data access.

The comprehensive summary of changes made in BitcoinRocks compared to Bitcoin Core highlights a focus on storage optimization, database backend upgrades, and enhanced node operation performance without compromising on consensus or network message formats. The detailed documentation and open-source release invite collaboration and independent review from the community, aiming to refine and validate these improvements through broader testing and feedback. The programmer remains committed to addressing any issues identified during this review process, emphasizing the importance of community involvement in advancing the robustness and efficiency of blockchain technology implementations.