Im all alone for thanksgiving since my parents arent coming to visit me till friday at midnight . Drugs and the promise of new weeknd in 11 hours and 49 minutes is what keeps me goin on this gloomy day in this empty fucking town <| sep |> Garbage officiating . Good to see we ' re starting early today . <| sep |> The Vikings are thankful for NFL referees <| sep |> We can ' t stop ! <| sep |> M ' ahnwalt tippt die Jura . <| sep |> Relevant conversation between Satoshi and Gavin 195 . msg 1611 # msg 1611 SatoshiI don ' t believe a second , compatible implementation of Bitcoin will ever be a good idea . So much of the design depends on all nodes getting exactly identical results in lockstep that a second implementation would be a menace to the network . The MIT license is compatible with all other licenses and commercial uses , so there is no need to rewrite it from a licensing standpoint . GavinGood idea or not , SOMEBODY will try to mess up the network or coopt it for their own use sooner or later . They ' ll either hack the existing code or write their own version , and will be a menace to the network . I admire the flexibility of the scriptsinatransaction scheme , but my evil little mind immediately starts to think of ways I might abuse it . I could encode all sorts of interesting information in the TxOut script , and if nonhacked clients validatedandthenignored those transactions it would be a useful covert broadcast communication channel . That ' s a cool feature until it gets popular and somebody decides it would be fun to flood the payment network with millions of transactions to transfer the latest Lady Gaga video to all their friends . SatoshiA 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 .