From:satoshiSubject:Re: Dealing with SHA-256 CollisionsDate:June 14, 2010 at 20:39:50 UTCSHA-256 is very strong. It's not like the incremental step from MD5 to SHA1. It can last several decades unless there's some massive breakthrough attack.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.
DECODED OP_RETURN OUTPUTS · 1
vout 0Message46726f6d3a7361746f7368695375626a6563743a52653a204465616c696e672077697468205348412d32353620436f6c6c6973696f6e73446174653a4a756e652031342c20323031302061742032303a33393a3530205554435348412d32353620697320…
MORE FROM BC1QKHQLK3…2T8FThis OP RETURN is purposely put together so that the number of bytes is greater than 83 bytes so as to provide replay protection on Bitcoin Blake2d.26d ago
Etched into the Bitcoin blockchain. It cannot be deleted, edited, or taken down.
ON-CHAIN RECORD
TXID
BLOCK#965,529 · 2026-09-04
FEE1 sat/vB · 1,780 sats ≈ $1.42
ADDRESS
SENDER
COLLECTION—
PROTOCOLtext
CATEGORYOther (AI)
SIZE804 bytes
TIME27d ago · 21:58 UTC
VIEW ON MEMPOOL.SPACE ↗