From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net, xor@freenetproject.org
Subject: Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken
Date: Tue, 3 Jun 2014 04:52:39 +0000 [thread overview]
Message-ID: <201406030452.40520.luke@dashjr.org> (raw)
In-Reply-To: <2341954.NpNStk60qp@1337h4x0r>
On Tuesday, June 03, 2014 4:29:55 AM xor wrote:
> Hi,
>
> I thought a lot about the worst case scenario of SHA256d being broken in a
> way which could be abused to
> A) reduce the work of mining a block by some significant amount
> B) reduce the work of mining a block to zero, i.e. allow instant mining.
C) fabricate past blocks entirely.
If SHA256d is broken, Bitcoin as it is fails entirely.
Luke
next prev parent reply other threads:[~2014-06-03 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 4:29 [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken xor
2014-06-03 4:52 ` Luke Dashjr [this message]
2014-06-03 11:51 ` Ethan Heilman
2014-06-03 15:12 ` Ashley Holman
2014-06-03 12:45 ` Rusty Russell
2014-06-04 1:38 ` Charlie 'Charles' Shrem
2014-06-05 6:09 ` Rusty Russell
2014-06-03 14:43 ` Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201406030452.40520.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=xor@freenetproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox