summaryrefslogtreecommitdiff
path: root/6e/9dac2b6993a2ecb2292b683779df8a63913cb9
blob: 29881174d4ed0e987377aa5c9a02fd218f4fa0fb (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <rdwnj@yahoo.com>) id 1X6tYf-0000C1-So
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 03:37:37 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of yahoo.com
	designates 98.136.217.16 as permitted sender)
	client-ip=98.136.217.16; envelope-from=rdwnj@yahoo.com;
	helo=nm33.bullet.mail.gq1.yahoo.com; 
Received: from nm33.bullet.mail.gq1.yahoo.com ([98.136.217.16])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1X6tYe-0002BG-6V
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 03:37:37 +0000
Received: from [127.0.0.1] by nm33.bullet.mail.gq1.yahoo.com with NNFMP;
	15 Jul 2014 03:37:30 -0000
Received: from [98.137.12.62] by nm33.bullet.mail.gq1.yahoo.com with NNFMP;
	15 Jul 2014 03:34:42 -0000
Received: from [98.137.12.229] by tm7.bullet.mail.gq1.yahoo.com with NNFMP;
	15 Jul 2014 03:34:42 -0000
Received: from [127.0.0.1] by omp1037.mail.gq1.yahoo.com with NNFMP;
	15 Jul 2014 03:34:42 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 869934.12398.bm@omp1037.mail.gq1.yahoo.com
Received: (qmail 3153 invoked by uid 60001); 15 Jul 2014 03:34:42 -0000
X-YMail-OSG: aq7sZXUVM1lI71eR6JAxC9LPGvKokfstDHQevv_Xp58goSc
	wagbj.iq_B9.p1s.lB0BEJ5V0_kYd4nRVii2JwrpfHXQEUJwpUeiEfz1Dopg
	IlV3taWMRqbPDeGfcA_vW4YH72AFtVs28uHhDwdvePKh6aVhvBuUsGfG6Af8
	qbwRdv8XssENf2vUH5vkKYKncp6JBnC_VX2kkdPVPN0M7J2yO2NCVvt.suyr
	Y659EkeHd2MeBNxhL1cOh8kGEpSlJl5TEpvpjgl.Ydq_yJygoBfUGShBGAvI
	VJZJV6lzhuhilURhYsMMDB2b2XATOMDJY5DEjCSRVXMYLA1Xoml_67s.Lj38
	113SgyhClocJcYghe4scqsMqeXLq_K64q9Rcn.GB8uEuxrBaWKzzduCPIgHZ
	2KeGdo90kHa8zwODuJ7jcpfv5Au2l2_C8JDwy_FucUC.DT.tzMqL.lWnkO2P
	8pxIWmuHfuxy9fqIyGmeC1xH3lnPeEOW1DfUp_xrN_TDBbi81jp3i0RJNxf9
	W5Kx93KPXqMMaERWCGXOL6PrmeRnur_Y3WSDtKKlqp2UDwcMMGOiIfC_W4iG I6QE-
Received: from [47.20.192.22] by web164501.mail.gq1.yahoo.com via HTTP;
	Mon, 14 Jul 2014 20:34:42 PDT
X-Rocket-MIMEInfo: 002.001,
	Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1lc3NhZ2U6IDYKRGF0ZTogTW9uLCAxNCBKdWwgMjAxNCAxMzoyNjoxOSArMDIwMApGcm9tOiBNaWtlIEhlYXJuIDxtaWtlQHBsYW45OS5uZXQ.ClN1YmplY3Q6IFJlOiBbQml0Y29pbi1kZXZlbG9wbWVudF0gQml0Y29pbiBQcm90b2NvbCBTcGVjaWZpY2F0aW9uClRvOiBLcnp5c3p0b2YgT2t1cHNraSA8ay5va3Vwc2tpQGdvb2dsZW1haWwuY29tPgpDYzogQml0Y29pbiBEZXYgPGJpdGNvaW4tZGV2ZWxvcG1lbnRAbGlzdHMuc291cmNlZm9yZ2UubmUBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.194.680
References: <mailman.253891.1405338074.2207.bitcoin-development@lists.sourceforge.net>
Message-ID: <1405395282.75933.YahooMailNeo@web164501.mail.gq1.yahoo.com>
Date: Mon, 14 Jul 2014 20:34:42 -0700
From: Ron <rdwnj@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <mailman.253891.1405338074.2207.bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="792791180-1999138569-1405395282=:75933"
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HK_RANDOM_FROM         From username looks random
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.6 HK_RANDOM_ENVFROM      Envelope sender username looks random
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(rdwnj[at]yahoo.com)
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [98.136.217.16 listed in list.dnswl.org]
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain 1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1X6tYe-0002BG-6V
Subject: Re: [Bitcoin-development] "Bitcoin Protocol Guide"
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Ron <rdwnj@yahoo.com>
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, 15 Jul 2014 03:37:38 -0000

--792791180-1999138569-1405395282=:75933
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A________________________________=0AMessage: 6=0ADate: Mon, 14 Jul 2014 1=
3:26:19 +0200=0AFrom: Mike Hearn <mike@plan99.net>=0ASubject: Re: [Bitcoin-=
development] Bitcoin Protocol Specification=0ATo: Krzysztof Okupski <k.okup=
ski@googlemail.com>=0ACc: Bitcoin Dev <bitcoin-development@lists.sourceforg=
e.net>=0AMessage-ID:=0A=A0=A0=A0 <CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD=
6qYEfHvpoA@mail.gmail.com>=0AContent-Type: text/plain; charset=3D"utf-8"=0A=
=0ANice work, but please don't call it the "Bitcoin protocol spec". Your=0A=
document is not a spec. It is an attempt to describe in English the Bitcoin=
=0Aprotocol, but anyone who implemented it based on your description would =
get=0Ait wrong. For example you didn't mention the SIGHASH_SINGLE bug and m=
any=0Aother important areas like the difficulty transitions are also left=
=0Aunspecified.=0A=0AAs a loose description of the protocol for newbies it'=
s an invaluable=0Aresource and perhaps we should link to it from the develo=
per guide. As=0Asomething that claims to be a specification it is quite pos=
sibly dangerous=0A- the only spec that matters is the C++ original.=0A...=
=0A=0AHello Mike,=0A=0AWhat C++ original might that be?=A0 Version 0.1.0? 0=
.9.x? 0.8.6?=A0 And what parts of which version?=0A=0ARon
--792791180-1999138569-1405395282=:75933
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:bo=
okman old style, new york, times, serif;font-size:10pt">  <div style=3D"fon=
t-family: bookman old style, new york, times, serif; font-size: 10pt;"> <di=
v style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lu=
cida Grande, sans-serif; font-size: 12pt;"> <div class=3D"y_msg_container">=
 <hr size=3D"1"><font face=3D"Arial" size=3D"2"><b><span style=3D"font-weig=
ht:bold;"></span></b></font>Message: 6<br>Date: Mon, 14 Jul 2014 13:26:19 +=
0200<br>From: Mike Hearn &lt;<a ymailto=3D"mailto:mike@plan99.net" href=3D"=
mailto:mike@plan99.net">mike@plan99.net</a>&gt;<br>Subject: Re: [Bitcoin-de=
velopment] Bitcoin Protocol Specification<br>To: Krzysztof Okupski &lt;<a y=
mailto=3D"mailto:k.okupski@googlemail.com" href=3D"mailto:k.okupski@googlem=
ail.com">k.okupski@googlemail.com</a>&gt;<br>Cc: Bitcoin Dev &lt;<a ymailto=
=3D"mailto:bitcoin-development@lists.sourceforge.net"
 href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoin-developm=
ent@lists.sourceforge.net</a>&gt;<br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;=
<a ymailto=3D"mailto:CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@ma=
il.gmail.com" href=3D"mailto:CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEf=
HvpoA@mail.gmail.com">CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@m=
ail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset=3D"utf-8"<br><br=
>Nice work, but please don't call it the "Bitcoin protocol spec". Your<br>d=
ocument is not a spec. It is an attempt to describe in English the Bitcoin<=
br>protocol, but anyone who implemented it based on your description would =
get<br>it wrong. For example you didn't mention the SIGHASH_SINGLE bug and =
many<br>other important areas like the difficulty transitions are also left=
<br>unspecified.<br><br>As a loose description of the protocol for newbies =
it's an invaluable<br>resource and perhaps we should link to it from the
 developer guide. As<br>something that claims to be a specification it is q=
uite possibly dangerous<br>- the only spec that matters is the C++ original=
.<br>...<br><br>Hello Mike,<br><br>What C++ original might that be?&nbsp; V=
ersion 0.1.0? 0.9.x? 0.8.6?&nbsp; And what parts of which version?<br><br>R=
on<br><br><br><br><a ymailto=3D"mailto:k.okupski@googlemail.com" href=3D"ma=
ilto:k.okupski@googlemail.com"></a><br></div> </div> </div>  </div></body><=
/html>
--792791180-1999138569-1405395282=:75933--