1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <peter@coinlab.com>) id 1StaWZ-0003ys-Ak
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jul 2012 08:31:23 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of coinlab.com
designates 209.85.161.175 as permitted sender)
client-ip=209.85.161.175; envelope-from=peter@coinlab.com;
helo=mail-gg0-f175.google.com;
Received: from mail-gg0-f175.google.com ([209.85.161.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1StaWT-0004QY-Je
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jul 2012 08:31:23 +0000
Received: by ggnp4 with SMTP id p4so6549255ggn.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jul 2012 01:31:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type:x-gm-message-state;
bh=RWIqLxMC9q9EZI7jqGfKK5gwkJFZfG4e9NKIUlhhxRA=;
b=fCnvxs5XynpMcHHALsTztnFfIEbhQtu08lYUGyR+ISgoKPc9tv+qGvj8a8FwhKWUwF
80ov/Ilc+DXLPXt65MyHhPrv2+0F4aYpOfUk45904nXi8mymb1syQ3fO/agrISO9GWAT
N06uMWL6bB+dK521ULxiafuERXZfe4uZ3fydZTe3FUZ700wrcCrE9z6gYnSdbDNXbsFL
gC4xBem1lWxe1Q5qlS6+AjBdlgmBbRtTkWAG+MLyMt9sBp7iwahe3whf7LOSFufb7+Xa
S3YvCm8XZEuJnNlRnWH93DzqnvtHdzDYqvLYGrOvgr0tsi3LvCBMy5Ph2FRgzYVPzOGw
BM/A==
Received: by 10.42.145.7 with SMTP id d7mr13185668icv.45.1343116892596; Tue,
24 Jul 2012 01:01:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.207.3 with HTTP; Tue, 24 Jul 2012 01:01:11 -0700 (PDT)
In-Reply-To: <CANEZrP0NMmwWN1U3V_hha7+C8meKWK_szhh+6xP7VQMbFTLoqQ@mail.gmail.com>
References: <201207222052.28579.luke@dashjr.org>
<CABsx9T0JK9qBKZu7YWeQCBAjT1Ur05BQ26A5NdLCwD6Wuyc0nQ@mail.gmail.com>
<CANEZrP0NMmwWN1U3V_hha7+C8meKWK_szhh+6xP7VQMbFTLoqQ@mail.gmail.com>
From: Peter Vessenes <peter@coinlab.com>
Date: Tue, 24 Jul 2012 17:01:11 +0900
Message-ID: <CAMGNxUvRXA4y98ojrzQqLhKcYPXM9CUFXKdguQz3iu=jaNvk5w@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=90e6ba6136b846696d04c58ec544
X-Gm-Message-State: ALoCoQn1BPJf792qoN64GMcmLFtYSOGma+oaa8cd9fohdqhE6ra6n07hY/2vsmQk7WtzFJMyzfjy
X-Spam-Score: -0.5 (/)
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1StaWT-0004QY-Je
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Reconsidering block version number use
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: Tue, 24 Jul 2012 08:31:23 -0000
--90e6ba6136b846696d04c58ec544
Content-Type: text/plain; charset=ISO-8859-1
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'll have a lot fewer unique transaction /
coinbase sets to hold on to for checking when we get back a solution.
Peter
On Tue, Jul 24, 2012 at 4:58 PM, Mike Hearn <mike@plan99.net> wrote:
> > That'd be 7 bytes of nonce in the block header, which is
> > 72,057,594,037,927,936 ~ 72 petahashes = 72,000 terahashes
> >
> > So: the changes for version 2 blocks would be "has height in the
> > coinbase, and has a 1-byte version number with a 3-byte extranonce."
>
> I don't understand why more nonce bits are necessary. Is it really
> impossible for a multi-core CPU to keep up with the merkle root
> re-calculation and keep an ASIC miner fed, or is this working around a
> performance bottleneck somewhere else?
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
------------------------------
[image: CoinLab Logo]PETER VESSENES
CEO
*peter@coinlab.com * / 206.486.6856 / SKYPE: vessenes
811 FIRST AVENUE / SUITE 480 / SEATTLE, WA 98104
--90e6ba6136b846696d04c58ec544
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I think it would be great to have more nonce space with less merkle calcula=
tion; 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 amou=
nt, somewhat on the work generation side, but also on the checking old work=
side; we'll have a lot fewer unique transaction / coinbase sets to hol=
d on to for checking when we get back a solution.<div>
<br></div><div>Peter</div><div><br></div><div><br><div class=3D"gmail_quote=
">On Tue, Jul 24, 2012 at 4:58 PM, Mike Hearn <span dir=3D"ltr"><<a href=
=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">> That'd be 7 bytes=
of nonce in the block header, which is<br>
> =A0 72,057,594,037,927,936 =A0~ 72 petahashes =3D 72,000 terahashes<br=
>
><br>
> So: the changes for version 2 blocks would be "has height in the<=
br>
> coinbase, and has a 1-byte version number with a 3-byte extranonce.&qu=
ot;<br>
<br>
</div>I don't understand why more nonce bits are necessary. Is it reall=
y<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=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today's security and<br>
threat landscape has changed and how IT managers can respond. Discussions<b=
r>
will include endpoint security, mobile security and the latest in malware<b=
r>
threats. <a href=3D"http://www.accelacomm.com/jaw/sfrnl04242012/114/5012226=
3/" target=3D"_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122=
263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<hr style=3D"font-family:Times;font-size:medium;border-right-width:0px;bord=
er-bottom-width:0px;border-left-width:0px;border-top-style:solid;border-top=
-color:rgb(204,204,204);margin:10px 0px">
<p style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1=
em"><span style=3D"color:rgb(50,90,135);text-transform:uppercase"><img src=
=3D"http://coinlab.com/static/images/email_logo.jpg" align=3D"right" alt=3D=
"CoinLab Logo" width=3D"130">PETER=A0<span style=3D"font-weight:bold">VESSE=
NES=A0</span><br>
<span style=3D"color:rgb(96,58,23);font-size:0.8em">CEO</span></span></p><p=
style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1em=
"><span style=3D"color:rgb(96,58,23);font-size:0.9em"><strong><a href=3D"ma=
ilto:peter@coinlab.com" style=3D"text-decoration:none;color:rgb(96,58,23)" =
target=3D"_blank">peter@coinlab.com</a>=A0</strong>=A0/=A0=A0206.486.6856 =
=A0/=A0<span style=3D"font-size:0.7em;text-transform:uppercase">SKYPE:</spa=
n>=A0vessenes=A0</span><br>
<span style=3D"color:rgb(96,58,23);font-size:0.7em;text-transform:uppercase=
">811 FIRST AVENUE =A0/=A0 SUITE 480 =A0/=A0 SEATTLE, WA 98104</span></p><b=
r>
</div>
--90e6ba6136b846696d04c58ec544--
|
