Combined summary - BIP352: PSBT support

Combined summary - BIP352: PSBT support

The discussion begins with a consideration of technical feedback on the PSBT draft, suggesting a separation of the DLEQ (Discrete Logarithm Equality) proofs into their own Bitcoin Improvement Proposal (BIP).

This proposition is underpinned by a draft that builds upon @RubenSomsen's gist, providing a foundation for further development in this area. The conversation delves into several key aspects of programming and cryptocurrency transactions, emphasizing the importance of handling group proofs, silent payment verification by signers, and the intricacies of implementing Anti-Counterfeiting Proofs (ACP) within the context of cryptocurrency transactions.

On the topic of silent payments, a nuanced approach to transaction verification is outlined, focusing on the conditions under which a signer should fail a transaction involving silent payment outputs. The dialogue underscores the necessity for signers to check for ACP on inputs they are responsible for signing, particularly when a sighash type other than ALL is present alongside silent payment outputs. The exploration into this subject reveals suggestions for simplifying the process through which signers verify transactions involving silent payments, proposing the addition of global shares and proofs for all inputs if applicable. This strategy aims to balance computational and memory demands on signers, acknowledging the varied capabilities of devices used in the signing process.

The conversation also highlights the security implications of using the ACP signature, pointing out the significant risk it poses to the funds of the parties involved in a transaction. It outlines the safer alternative of signing with ALL, protecting inputs regardless of how other parties have signed the transaction. This distinction emphasizes the criticality of choosing the appropriate signature type to ensure transaction security.

Further, the discourse examines the challenges associated with the SINGLE | ACP signing mechanism, illustrating potential security vulnerabilities when incorrect script generation or manipulation by external observers occurs. This analysis leads to broader considerations on trust and verification in the transaction process, particularly for silent payment-aware signers.

Additionally, the technicalities of managing shares and proofs within Payment Service Buses (PSBTs) are explored, suggesting an efficient way to handle transaction data by incorporating shares and proofs as global attributes. This method seeks to optimize transaction verification processes while maintaining or enhancing privacy measures and transactional integrity.

In addressing the optimization of cryptographic protocols, the discussion presents two approaches for handling inputs in cryptographic proofs, advocating for a unified proof for each scan key alongside its corresponding set of inputs. This proposal aims to streamline management and verification processes, highlighting the ongoing efforts to enhance security and efficiency in cryptographic operations.

Lastly, the updated draft for the BIP introduces the DLEQ proof, marking a substantial enhancement aimed at bolstering the security and efficiency of the proposed improvements. This update signifies a commitment to incorporating advanced cryptographic techniques, underscoring the collective endeavor to refine and advance the standards governing cryptocurrency transactions and programming constructs.

Discussion History

josibake Original Post
May 17, 2024 11:51 UTC
May 19, 2024 17:32 UTC
May 20, 2024 12:01 UTC
May 20, 2024 17:56 UTC
May 27, 2024 00:34 UTC
May 27, 2024 22:13 UTC
May 28, 2024 12:16 UTC
May 29, 2024 13:51 UTC
June 1, 2024 18:04 UTC
June 2, 2024 01:44 UTC
June 2, 2024 08:44 UTC
June 11, 2024 03:41 UTC
June 13, 2024 23:11 UTC
June 14, 2024 18:10 UTC
June 14, 2024 18:38 UTC
June 14, 2024 19:24 UTC
June 14, 2024 23:45 UTC
June 14, 2024 23:48 UTC
June 18, 2024 13:10 UTC
June 18, 2024 15:50 UTC
June 20, 2024 09:21 UTC
June 20, 2024 20:29 UTC
June 21, 2024 13:15 UTC
June 21, 2024 13:41 UTC
June 21, 2024 14:07 UTC
June 22, 2024 14:51 UTC
June 29, 2024 21:00 UTC