Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X6fKq-0006zv-AA for bitcoin-development@lists.sourceforge.net; Mon, 14 Jul 2014 12:26:24 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.51 as permitted sender) client-ip=209.85.215.51; envelope-from=sickpig@gmail.com; helo=mail-la0-f51.google.com; Received: from mail-la0-f51.google.com ([209.85.215.51]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X6fKo-0004T3-I3 for bitcoin-development@lists.sourceforge.net; Mon, 14 Jul 2014 12:26:24 +0000 Received: by mail-la0-f51.google.com with SMTP id el20so208546lab.10 for ; Mon, 14 Jul 2014 05:26:15 -0700 (PDT) X-Received: by 10.112.61.162 with SMTP id q2mr1650657lbr.71.1405340775826; Mon, 14 Jul 2014 05:26:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.181.98 with HTTP; Mon, 14 Jul 2014 05:25:54 -0700 (PDT) In-Reply-To: References: <53C3A8C0.5070608@googlemail.com> From: "sickpig@gmail.com" Date: Mon, 14 Jul 2014 14:25:54 +0200 Message-ID: To: Mike Hearn Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 (sickpig[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1X6fKo-0004T3-I3 Cc: Bitcoin Dev , Krzysztof Okupski 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 12:26:24 -0000 On Mon, Jul 14, 2014 at 1:26 PM, Mike Hearn wrote: > Nice work, but please don't call it the "Bitcoin protocol spec". Your > document is not a spec. fair objection, fwiw. > 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. at the end of the day it's opensource so it could always be improved via pull request on github. Krzysztof, in that regard I would add a licence file to make integration of changes made by others smoother. > 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. just out of curiosity, do you think it will be possible to create any other proper protocol specifications rather than the C++ original? > On Mon, Jul 14, 2014 at 11:54 AM, Krzysztof Okupski > 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