Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <k.okupski@googlemail.com>) id 1Wm1Fe-00022w-Hd
	for bitcoin-development@lists.sourceforge.net;
	Sun, 18 May 2014 13:35:42 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of googlemail.com
	designates 74.125.83.42 as permitted sender)
	client-ip=74.125.83.42; envelope-from=k.okupski@googlemail.com;
	helo=mail-ee0-f42.google.com; 
Received: from mail-ee0-f42.google.com ([74.125.83.42])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Wm1Fc-0000Y7-Kr
	for bitcoin-development@lists.sourceforge.net;
	Sun, 18 May 2014 13:35:42 +0000
Received: by mail-ee0-f42.google.com with SMTP id d49so2840691eek.29
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 18 May 2014 06:35:34 -0700 (PDT)
X-Received: by 10.15.36.8 with SMTP id h8mr38843538eev.12.1400420134374;
	Sun, 18 May 2014 06:35:34 -0700 (PDT)
Received: from [192.168.1.66] (s53751712.adsl.online.nl. [83.117.23.18])
	by mx.google.com with ESMTPSA id 8sm34632093eea.10.2014.05.18.06.35.33
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sun, 18 May 2014 06:35:33 -0700 (PDT)
Message-ID: <5378B725.50400@googlemail.com>
Date: Sun, 18 May 2014 15:35:33 +0200
From: Krzysztof Okupski <k.okupski@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
	(k.okupski[at]googlemail.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: 1Wm1Fc-0000Y7-Kr
Subject: [Bitcoin-development] Bitcoin Protocol Specification
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
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: Sun, 18 May 2014 13:35:42 -0000

Dear all,

I'd like to kindly ask, those of you that have a bit of spare time, to
take a look at a Bitcoin protocol specification I've written. It is still
in development and, as some of you have already indicated, needs
improvement. I'd be very thankful if some of you could take the
time to review it. If there are any errors or suggestions from your
side, I'd gladly hear them. My e-mail can be found on the front page
of the document:

http://enetium.com/resources/Bitcoin.pdf

Warm greetings,
Chris