Changes to BIP-360 - Pay to Quantum Resistant Hash (P2QRH)

Posted by dr-orlovsky

Jul 15, 2025/11:19 UTC

The discussion revolves around the security mechanisms in place for tapscript outputs, particularly how P2QRH safeguards against long-exposure attacks. This protective measure is effective unless the wallet descriptor becomes exposed, highlighting the importance of maintaining confidentiality to ensure security. The choice of Segwit version 3 over version 2 is strategically motivated by the need for efficiency and compatibility with existing payload sizes. Specifically, the utilization of version 3 is preferred due to the requirement that version 2 would necessitate a different payload size to be reused. Given that the payload size in question is exactly 256 bits (hash), adopting a newer version eliminates the need for appending unnecessary bytes to extend it. This approach not only maintains the integrity of the data but also conserves blockchain space by avoiding permanent consumption through extensions. This decision underscores a broader principle in blockchain development: optimizing for both security and efficiency without compromising on either.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback