Create 156.md

2021-01-08 23:43:58 -06:00
parent 85a490dd3b
commit 7379501a61
1 changed files with 26 additions and 0 deletions
@@ -0,0 +1,26 @@
+---
+layout: forum
+title: 'Re: Major Meltdown'
+grand_parent: Forum Posts
+parent: Bitcoin Forum
+nav_order: 156
+date: 2010-06-27 19:06:09 UTC
+original: https://bitcointalk.org/index.php?topic=202.msg1838#msg1838
+---
+
+# Re: Major Meltdown
+---
+
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight">
+<code>Re: Major Meltdown
+June 27, 2010, 07:06:09 PM
+
+Here's an answer to a similar question about how to recover from a major meltdown.
+https://www.bitcoin.org/smf/index.php?topic=191.msg1585#msg1585
+
+<a href="https://bitcointalk.org/index.php?topic=191.msg1585#msg1585">Quote from: satoshi on June 14, 2010, 08:39:50 PM</a>
+-------------
+If SHA-256 became completely broken, I think we could come to some agreement about what the honest block chain was before the trouble started, lock that in and continue from there with a new hash function.
+
+If the hash breakdown came gradually, we could transition to a new hash in an orderly way.  The software would be programmed to start using a new hash after a certain block number.  Everyone would have to upgrade by that time.  The software could save the new hash of all the old blocks to make sure a different block with the same old hash can't be used.</code></pre></div></div>
+-------------