Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <andyparkins@gmail.com>) id 1X31f9-0002BC-FC
	for bitcoin-development@lists.sourceforge.net;
	Fri, 04 Jul 2014 11:28:19 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.180 as permitted sender)
	client-ip=209.85.212.180; envelope-from=andyparkins@gmail.com;
	helo=mail-wi0-f180.google.com; 
Received: from mail-wi0-f180.google.com ([209.85.212.180])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X31f7-0000Tq-JB
	for bitcoin-development@lists.sourceforge.net;
	Fri, 04 Jul 2014 11:28:19 +0000
Received: by mail-wi0-f180.google.com with SMTP id hi2so3778552wib.7
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 04 Jul 2014 04:28:11 -0700 (PDT)
X-Received: by 10.194.177.168 with SMTP id cr8mr2103416wjc.134.1404473290474; 
	Fri, 04 Jul 2014 04:28:10 -0700 (PDT)
Received: from momentum.localnet ([91.84.15.31])
	by mx.google.com with ESMTPSA id l5sm78195732wif.22.2014.07.04.04.28.09
	for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Fri, 04 Jul 2014 04:28:09 -0700 (PDT)
From: Andy Parkins <andyparkins@gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
Date: Fri, 04 Jul 2014 12:28:08 +0100
Message-ID: <2403605.jQQrFQc91a@momentum>
User-Agent: KMail/4.12.4 (Linux/3.10-2-amd64; KDE/4.13.1; x86_64; ; )
In-Reply-To: <53B68E6B.6090602@gmail.com>
References: <10566815.3CllqoMfON@momentum> <2734024.vxftdBi7Ll@momentum>
	<53B68E6B.6090602@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(andyparkins[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1X31f7-0000Tq-JB
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] ASIC-proof mining
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2014 11:28:19 -0000

On Friday 04 July 2014 07:22:19 Alan Reiner wrote:

> I think you misundersood....  using ROMix-like algorithm, each hash

I did.  Sorry.

> requires a different 32 MB of the blockchain.  Uniformly distributed
> throughout the blockchain, and no way to predict which 32 MB until you
> have actually executed it.   If the difficulty is high enough, your
> miner is likely to end up going through the entire X GB blockchain while
> searching for a good hash, but other nodes will only need to do 32 MB
> worth of disk accesses to verify your answer (and it will be unknown
> which 32 MB until they do the 1,000,000 hash+lookup operations on their
> X GB blockchain).

Excellent.


Andy

-- 
Dr Andy Parkins
andyparkins@gmail.com