Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG
Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG
Date: June 18, 2010
Source: BitcoinTalk Forum
URL: https://satoshi.nakamotoinstitute.org/posts/bitcointalk/127/
A second version would be a massive development and maintenance hassle for me. It's hard enough maintaining backward compatibility while upgrading the network without a second version locking things in. If the second version screwed up, the user experience would reflect badly on both, although it would at least reinforce to users the importance of staying with the official version. If someone was getting ready to fork a second version, I would have to air a lot of disclaimers about the risks of using a minority version. This is a design where the majority version wins if there's any disagreement, and that can be pretty ugly for the minority version and I'd rather not go into it, and I don't have to as long as there's only one version.
I know, most developers don't like their software forked, but I have real technical reasons in this case.
Quote from: gavinandresen on June 17, 2010, 07:58:14 PM