From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X6eOo-0008VB-8Y for bitcoin-development@lists.sourceforge.net; Mon, 14 Jul 2014 11:26:26 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.41 as permitted sender) client-ip=209.85.219.41; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f41.google.com; Received: from mail-oa0-f41.google.com ([209.85.219.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X6eOn-0006ty-4A for bitcoin-development@lists.sourceforge.net; Mon, 14 Jul 2014 11:26:26 +0000 Received: by mail-oa0-f41.google.com with SMTP id j17so1249756oag.0 for ; Mon, 14 Jul 2014 04:26:19 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.63.3 with SMTP id c3mr17244130oes.16.1405337179660; Mon, 14 Jul 2014 04:26:19 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Mon, 14 Jul 2014 04:26:19 -0700 (PDT) In-Reply-To: <53C3A8C0.5070608@googlemail.com> References: <53C3A8C0.5070608@googlemail.com> Date: Mon, 14 Jul 2014 13:26:19 +0200 X-Google-Sender-Auth: FP8jmu_8uzoWdquZWpj4vWazUjA Message-ID: From: Mike Hearn To: Krzysztof Okupski Content-Type: multipart/alternative; boundary=001a11c1d24262278904fe258fdc 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1X6eOn-0006ty-4A Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 11:26:26 -0000 --001a11c1d24262278904fe258fdc Content-Type: text/plain; charset=UTF-8 Nice work, but please don't call it the "Bitcoin protocol spec". Your document is not a spec. It is an attempt to describe in English the Bitcoin 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 quite possibly dangerous - the only spec that matters is the C++ original. On Mon, Jul 14, 2014 at 11:54 AM, Krzysztof Okupski < k.okupski@googlemail.com> wrote: > Dear all, > > thank you for your invaluable feedback. As requested, the spec > will from now on be under version control. It can be found under: > > https://github.com/minium/Bitcoin-Spec > > The old link to the PDF will be, just in case, kept updated as well. > > > Warm greetings, > Krzysztof Okupski > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck® > Code Sight™ - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a11c1d24262278904fe258fdc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Nice work, but please don't call it the "Bitcoin = protocol spec". Your document is not a spec. It is an attempt to descr= ibe in English the Bitcoin protocol, but anyone who implemented it based on= your description would get it wrong. For example you didn't mention th= e SIGHASH_SINGLE bug and many other important areas like the difficulty tra= nsitions 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 quite possibly = dangerous - the only spec that matters is the C++ original.


On Mon,= Jul 14, 2014 at 11:54 AM, Krzysztof Okupski <k.okupski@googlemail= .com> wrote:
=20 =20 =20
Dear all,

thank you for your invaluable feedback. As requested, the spec
will from now on be under version control. It can be found under:

=20 ht= tps://github.com/minium/Bitcoin-Spec

The old link to the PDF will be, just in case, kept updated as well.

Warm greetings,
Krzysztof Okupski

-----------------------------------------------------------------------= -------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck&#174;=
Code Sight&#153; - the same software that powers the world's larges= t code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/b= ds
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a11c1d24262278904fe258fdc--