Posted by salvatoshi
Jul 10, 2025/08:07 UTC
The discussion revolves around the complexities and limitations involved in committing to a single input in transaction systems, specifically highlighting the issues that arise when only the output side is considered. A significant point raised is the inability to add extra inputs once a commitment to a single input has been made, suggesting that this constraint could potentially be addressed by adopting a standardness policy. However, the efficacy of combining policy rules with replacement rules to universally solve for an arbitrary number of inputs remains an intriguing yet unresolved question.
Furthermore, the conversation touches upon several problems associated with committing solely to the output side, such as the half-spend issue and malleation concerns. These issues are notably discussed within the context of BIP-119, where it's clarified that malleation primarily affects the TXID, placing it somewhat outside the current discussion scope. The half-spend problem receives acknowledgment as a valid concern, contrasting with the Cross-Input Signature Aggregation (CCV) approach which avoids this issue through its cross-input amount logic.
The possibility of implementing a CTV-like opcode that limits its use to a single input is proposed as a potential solution to these challenges. This approach would necessitate some form of simple cross-input logic, aiming to mitigate the identified problems without introducing undue complexity. The conversation includes references to specific Bitcoin Improvement Proposals (BIPs) to provide further insight and rationale behind these points, such as rationale from BIP-119 and CCV, enriching the discussion with technical details and proposals for addressing these issues within digital transaction systems.
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