j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¬<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=360.msg3067#msg3067">Quote from: bdonlan on July 15, 2010, 02:41:56 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=360.msg3064#msg3064">Quote from: Bitcoiner on July 15, 2010, 02:31:52 AM</a></div><div class="quote">Could this be fixed in the next release? We were just discussing what would happen if a flaw were found: Here we go, our first real test of the situation. <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/></div>Nope! At least, not easily - block and transaction identities are based on this hash, among other things, so this would break the chain. You'd need to do a phased rollout - first, add parsing support to all clients, then obsolete older clients, then roll out a new version which generates a new version of the block serialization format using the new hashing method.<br/></div><br/>All the better to practice now, while the network is still young! Well, if it is not a real flaw, it's not necessary, but it would be good practice. This could always be done first in the test network.</div> text/html
https://whatsonchain.com/tx/f7aa63f8bd3d6c06a6832049c8ff796835c8ff1e6180b23cd2cbe476ebf72f9b