Public key recovery for EC leaves in P2MR (BIP-360)

In the discussion about blockchain technology and crypto wallet output types, several key points emerge regarding the practicality and privacy implications of different approaches. The comparison between utilizing P2MR and P2TRv2 output types is central to this analysis. These types are distinct in their susceptibility to security threats, such as long-exposure attacks, particularly affecting P2TRv2. This vulnerability underscores a significant privacy concern: at the time of transaction, it becomes apparent whether the commitment was made in the style of P2MR or P2TRH, thereby distinguishing these outputs in terms of spending-policy privacy.

From an analytical perspective, combining these formats into a single offering might seem efficient, but it leads to them being treated as two separate anonymity sets by chain analysts. This differentiation could potentially compromise user privacy due to the distinguishable nature of transaction commitments. Moreover, to the end-users, these dual formats would appear identical, which can be perceived as either advantageous or disadvantageous depending on the user’s perspective on privacy versus simplicity.

After further deliberation, the suggestion leans towards deploying two distinct output types rather than merging them into a unified format. This approach not only simplifies the specification and coding requirements but also aligns better with engineering practices by facilitating separate Bitcoin Improvement Proposals (BIPs) for each type. Additionally, the proposal to consider another combination of output types, P2QR alongside P2TRv2, introduces an alternative worth exploring that might balance the technical and privacy considerations more effectively.