Published on: 2014-04-26T17:00:23+00:00
The discussion revolves around the need for standardization and interoperability between software in Bitcoin. While miners have the freedom to decide their own inclusion rules, it is generally accepted that transactions should be updated in the reference client to increase their chances of being accepted. There is ongoing discussion about a softfork to redo the Script language, but this will take time before it can be implemented.In an email conversation, Tier Nolan suggests that a BIP may not be necessary for cross-chain systems unless transactions are accepted in all chains. Luke Dashjr explains that BIPs are meant to define standards for interoperability, but they do not force nodes to adopt any specific policy. However, a BIP for cross-chain trading could help convince nodes to relay the transactions. It is also noted that fixing the malleability issue is crucial for secure transfers.In April 2014, Tier Nolan raises a concern about the lack of use cases defined in a Bitcoin Improvement Proposal (BIP). The response clarifies that the specification was simply unclear and that one use case would suffice. The proposal aims to allow spending to be controlled by the publication of information in another transaction, ensuring atomic completion of transactions.Peter Todd warns that P2SH redeemScripts have a size limit of 520 bytes, which may pose limitations for complex transactions. However, he notes that these transactions can already be mined into blocks and is not a protocol change. The email exchange also includes an advertisement for eXo Platform, a collaboration tool.Tier Nolan proposes a BIP to allow spenders to choose one of multiple standard scripts for spending outputs as part of the atomic cross-chain transfer protocol. Luke-Jr suggests that one use case should be enough and discusses the difficulty of getting non-standard transactions confirmed on other coins. He also recommends fixing the malleability issue for secure transfers and suggests the possibility of a future BIP for cross-chain transfers.In an email thread, Luke-Jr suggests linking to a GitHub repository instead of the current link provided. Peter Todd points out the size limit of P2SH redeemScripts. The email is signed with a digital signature.The proposed BIP allows spenders to choose from multiple standard scripts for spending outputs in the atomic cross-chain transfer protocol. It also suggests requiring P2SH and potentially implementing "Multi-P2SH" through a soft fork. The benefits of this change would be similar to MAST, but it would require further development and consensus.
Updated on: 2023-08-01T09:00:41.141042+00:00