Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WsQse-0001G7-Bx for bitcoin-development@lists.sourceforge.net; Thu, 05 Jun 2014 06:10:28 +0000 X-ACL-Warn: Received: from ozlabs.org ([103.22.144.67]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WsQsc-0002f4-MZ for bitcoin-development@lists.sourceforge.net; Thu, 05 Jun 2014 06:10:28 +0000 Received: by ozlabs.org (Postfix, from userid 1011) id A59431400A6; Thu, 5 Jun 2014 16:10:18 +1000 (EST) From: Rusty Russell To: Charlie 'Charles' Shrem In-Reply-To: References: <2341954.NpNStk60qp@1337h4x0r> <201406030452.40520.luke@dashjr.org> <87iooi40ws.fsf@rustcorp.com.au> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Thu, 05 Jun 2014 15:39:15 +0930 Message-ID: <87mwdr3n1w.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WsQsc-0002f4-MZ Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 06:10:28 -0000 Charlie 'Charles' Shrem 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.