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 ) 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: Message-ID: <1405395282.75933.YahooMailNeo@web164501.mail.gq1.yahoo.com> Date: Mon, 14 Jul 2014 20:34:42 -0700 From: Ron To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: 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 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 =0ASubject: Re: [Bitcoin-= development] Bitcoin Protocol Specification=0ATo: Krzysztof Okupski =0ACc: Bitcoin Dev =0AMessage-ID:=0A=A0=A0=A0 =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
=
Message: 6
Date: Mon, 14 Jul 2014 13:26:19 += 0200
From: Mike Hearn <mike@plan99.net>
Subject: Re: [Bitcoin-de= velopment] Bitcoin Protocol Specification
To: Krzysztof Okupski <k.okupski@googlemail.com>
Cc: Bitcoin Dev <bitcoin-developm= ent@lists.sourceforge.net>
Message-ID:
    <= CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@m= ail.gmail.com>
Content-Type: text/plain; charset=3D"utf-8"
Nice work, but please don't call it the "Bitcoin protocol spec". Your
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
it wrong. For example you didn't mention the SIGHASH_SINGLE bug and = many
other important areas like the difficulty transitions are also left=
unspecified.

As a loose description of the protocol for newbies = it's an invaluable
resource and perhaps we should link to it from the developer guide. As
something that claims to be a specification it is q= uite possibly dangerous
- the only spec that matters is the C++ original= .
...

Hello Mike,

What C++ original might that be?  V= ersion 0.1.0? 0.9.x? 0.8.6?  And what parts of which version?

R= on




<= /html> --792791180-1999138569-1405395282=:75933--