From: Rusty Russell <rusty@rustcorp.com.au>
To: Charlie 'Charles' Shrem <cshrem@gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken
Date: Thu, 05 Jun 2014 15:39:15 +0930 [thread overview]
Message-ID: <87mwdr3n1w.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAC787aM3bcfcw8zQQbNYXqxASFarW-z9wqiePmb6rv0RiiTdeA@mail.gmail.com>
Charlie 'Charles' Shrem <cshrem@gmail.com> writes:
> Hey Rusty,
>
> This is intriguing, do you have a writeup somewhere I can read more about ?
OK, ignore the FIXMEs, but I rehashed my stupid sim code, added some
graphs to the (clearly unfinished) paper and uploaded it to github:
https://github.com/rustyrussell/bitcoin_hashchange
PDF is in there too, for easier reading.
Cheers,
Rusty.
next prev parent reply other threads:[~2014-06-05 6:10 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
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 [this message]
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=87mwdr3n1w.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=cshrem@gmail.com \
/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