Prohibit Merkle Internal Node Preimages That Encode Minimal 64-Byte Transactions

The discussion revolves around the potential design and implications of an SPV (Simplified Payment Verification) protocol that leverages chains of transactions based on an anyone-can-spend connector output. The concern highlighted involves the creation of a fake connector output by miners, which could invalidate these transaction chains before they are jeopardized by other risks such as double spending. This raises significant doubts about the practical utility of such a protocol design.

Furthermore, the conversation touches upon a proposal to invalidate 64-byte transactions universally to enhance security for established use cases without necessitating modifications by SPV verifiers. Advancing this idea, it is suggested that excluding any inner node of the Merkle tree from being a valid bitcoin transaction serialization could complicate block template creation significantly. This addition would aim to secure more speculative constructions without requiring updates from SPV verifiers. However, the consensus seems to lean towards the view that the increase in complexity and the broader attack surface this would introduce may not justify the benefits, considering the alternative of patching SPV verifiers remains viable.

These insights were derived from discussions within the Bitcoin Development Mailing List, emphasizing the nuanced trade-offs between security enhancements and system complexity in blockchain protocol development.