I think it would be great to have more nonce space with less merkle calculation; keeping track of all possible versions of a block already takes real RAM, real computation. Being able to change one bit in the header and send out a new block for checking would ease our pool server work by a real amount, somewhat on the work generation side, but also on the checking old work side; we&#39;ll have a lot fewer unique transaction / coinbase sets to hold on to for checking when we get back a solution.<div>

<br></div><div>Peter</div><div><br></div><div><br><div class="gmail_quote">On Tue, Jul 24, 2012 at 4:58 PM, Mike Hearn <span dir="ltr">&lt;<a href="mailto:mike@plan99.net" target="_blank">mike@plan99.net</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">&gt; That&#39;d be 7 bytes of nonce in the block header, which is<br>
&gt;   72,057,594,037,927,936  ~ 72 petahashes = 72,000 terahashes<br>
&gt;<br>
&gt; So: the changes for version 2 blocks would be &quot;has height in the<br>
&gt; coinbase, and has a 1-byte version number with a 3-byte extranonce.&quot;<br>
<br>
</div>I don&#39;t understand why more nonce bits are necessary. Is it really<br>
impossible for a multi-core CPU to keep up with the merkle root<br>
re-calculation and keep an ASIC miner fed, or is this working around a<br>
performance bottleneck somewhere else?<br>
<div class="HOEnZb"><div class="h5"><br>
------------------------------------------------------------------------------<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today&#39;s security and<br>
threat landscape has changed and how IT managers can respond. Discussions<br>
will include endpoint security, mobile security and the latest in malware<br>
threats. <a href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/" target="_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><hr style="font-family:Times;font-size:medium;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-top-style:solid;border-top-color:rgb(204,204,204);margin:10px 0px">

<p style="font-size:medium;font-family:Helvetica,sans-serif;line-height:1em"><span style="color:rgb(50,90,135);text-transform:uppercase"><img src="http://coinlab.com/static/images/email_logo.jpg" align="right" alt="CoinLab Logo" width="130">PETER <span style="font-weight:bold">VESSENES </span><br>

<span style="color:rgb(96,58,23);font-size:0.8em">CEO</span></span></p><p style="font-size:medium;font-family:Helvetica,sans-serif;line-height:1em"><span style="color:rgb(96,58,23);font-size:0.9em"><strong><a href="mailto:peter@coinlab.com" style="text-decoration:none;color:rgb(96,58,23)" target="_blank">peter@coinlab.com</a> </strong> /  206.486.6856  / <span style="font-size:0.7em;text-transform:uppercase">SKYPE:</span> vessenes </span><br>

<span style="color:rgb(96,58,23);font-size:0.7em;text-transform:uppercase">811 FIRST AVENUE  /  SUITE 480  /  SEATTLE, WA 98104</span></p><br>
</div>