Posted by jeanpablojp
Jul 28, 2026/21:43 UTC
The recent implementation of BIP 360 in Bitcoin Core on the regtest network has yielded significant results and insights into the protocol's functionality and reliability. In a detailed testing process, all construction vectors aligned with expectations, confirming their robustness. However, during these tests, two critical bugs were identified in the pqc vector file. These issues have been addressed through proposed fixes submitted to the relevant repositories, which can be found at bitcoin/bips2220, with additional documentation adjustments in 2221 and a crucial amendment regarding witness size savings in 2223. The full documentation and analysis of these findings, including measured witness sizes and further specification feedback, are comprehensively detailed at DelvingBitcoin.org.
Moreover, an important observation from the implementation highlights a gap in the testing framework: the official test vectors currently only address construction scenarios without providing for consensus spend path testing. This lack of shared oracle for consensus spend path testing signifies a potential area for improvement in ensuring comprehensive validation processes. To aid in resolving this, there is a willingness to generate and contribute spend path vectors to the community, which would enhance the robustness and reliability of the testing framework by covering more extensive scenarios and use cases. This collaborative approach would undoubtedly benefit the Bitcoin development ecosystem by reinforcing the accuracy and security of implementations.
Thread Summary (30 replies)
Jul 7 - Jul 28, 2026
31 messages
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback