/
sipaPosted by sipa
Sep 11, 2026/16:58 UTC
The discussion revolves around the deployment and specifications of different output types in a blockchain context, specifically addressing concerns and proposals regarding P2TRv2 and other related types. It is clarified that the first output type does not utilize P2MR or P2TRH; instead, it is suggested that including at least one such type in the initial deployment would set clear expectations. A tripwire is recommended as a viable choice for this purpose.
Additionally, there is an exploration of the possibility of integrating v2 SegWit in a way that allows for later soft-forking by CISA, without requiring a new version bump. However, this appears unfeasible if the objective includes covering key path spends, which are considered the most interesting application. An update suggests the potential allocation of 1 bit of the public key to designate it as anyone-can-spend, effectively creating a separate output type but within the same witness version. This proposal aims to streamline the process while maintaining functional distinctions between output types.
Thread Summary (38 replies)
Jul 27 - Oct 2, 2026
39 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