Posted by stevenroose
Jul 15, 2025/15:09 UTC
The concept proposed involves a modification to the current taproot mechanism, introducing what could be referred to as a 'taproot v2'. This version would still commit to a 32-byte output, allowing for the standard taproot spend actions such as signing with an output key or showing a MAST (Merkelized Abstract Syntax Tree) tweak. A novel inclusion in this iteration would be the ability to present the MAST root as the preimage of the output, adding a layer of functionality.
However, it's important to note that this suggestion does not address quantum resistance, a significant consideration given the advancements in quantum computing. The reliance on the security assumption that no one can sign for an arbitrary 32-byte SHA256 output or reverse-engineer the SHA256 preimage of a public key is crucial for this system's integrity.
Regarding privacy, the proposed method suggests there would be no discernible difference in cases where a key spend is not involved. This implies that for transactions opting not to use the key spend feature, their privacy impact remains unchanged from the current taproot implementation, maintaining the status quo in terms of user anonymity and transaction obfuscation.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback