From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VYWUc-0004ot-Rz for bitcoin-development@lists.sourceforge.net; Tue, 22 Oct 2013 07:35:06 +0000 X-ACL-Warn: Received: from chrocht.moloch.sk ([62.176.169.44] helo=mail.moloch.sk) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VYWUb-00024n-EA for bitcoin-development@lists.sourceforge.net; Tue, 22 Oct 2013 07:35:06 +0000 Received: from [192.168.0.102] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 233911801A61; Tue, 22 Oct 2013 09:34:58 +0200 (CEST) Message-ID: <52662AA1.5050509@250bpm.com> Date: Tue, 22 Oct 2013 09:34:57 +0200 From: Martin Sustrik User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Gregory Maxwell , Jean-Paul Kogelman References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com> <201310211947.59640.luke@dashjr.org> <52661DB7.7040805@250bpm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: me.com] X-Headers-End: 1VYWUb-00024n-EA Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal 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: Tue, 22 Oct 2013 07:35:07 -0000 On 22/10/13 09:03, Gregory Maxwell wrote: > On Mon, Oct 21, 2013 at 11:59 PM, Jean-Paul Kogelman > wrote: >> Have you seen: https://en.bitcoin.it/wiki/Protocol_specification ? > > Take care, the information in the wiki is woefully incomplete. Imagine myself, with no prior knowledge of Bitcoin looking at the document. It starts with "Hashes". What hashes? No idea what's going on. Etc. Now compare that to a well written RFC. It starts with introduction, description of the problem, explains the conceptual model of the solution, then dives into the details. There's also Security Considerations part in every RFC that is pretty relevant for Bitcoin. As I said, I am willing to help with writing such document, it would be a nice way of learning the stuff, however, help from core devs, such as answering question that may arise in the process, or reviewing the document would be needed. Martin