BIP16/17 replacement



Summary:

On February 1st, 2012, there was a discussion between Andy Parkins and Luke-Jr regarding Bitcoin Improvement Proposals (BIP) 16 and 17. According to Luke-Jr, both BIPs were backward compatible enough that people could continue to use the old clients with each other. However, Andy questioned this statement and asked if it was true.In response to this, it was explained that IsStandard() is used for accepting transactions into the memory pool, and non-standard transactions are verified just fine when they are in the blockchain. BIP16/17 create transactions that, when interpreted as old scripts, are valid. The only change to the protocol is that previously-valid transactions become invalid. As long as a supermajority of miners enforce the new rules, everyone can happily keep using their old bitcoin client. They won't create the new transaction type, and don't accept them as payment, but they will accept the new block chain.However, it was emphasized that if a breaking change were made to the protocol, such as adding a new transaction type, ALL users must upgrade. Those who don't will see a fork of the chain from before the first new-style transaction. This was not the case with BIP16/17.


Updated on: 2023-05-18T23:04:10.775039+00:00