Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <k.okupski@googlemail.com>) id 1X07sg-0004E1-Pq
	for bitcoin-development@lists.sourceforge.net;
	Thu, 26 Jun 2014 11:30:18 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of googlemail.com
	designates 74.125.82.44 as permitted sender)
	client-ip=74.125.82.44; envelope-from=k.okupski@googlemail.com;
	helo=mail-wg0-f44.google.com; 
Received: from mail-wg0-f44.google.com ([74.125.82.44])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X07sf-0008BN-1M
	for bitcoin-development@lists.sourceforge.net;
	Thu, 26 Jun 2014 11:30:18 +0000
Received: by mail-wg0-f44.google.com with SMTP id x13so3283716wgg.3
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 26 Jun 2014 04:30:08 -0700 (PDT)
X-Received: by 10.194.77.103 with SMTP id r7mr17070349wjw.67.1403782206967;
	Thu, 26 Jun 2014 04:30:06 -0700 (PDT)
Received: from [192.168.1.65] (s53751712.adsl.online.nl. [83.117.23.18])
	by mx.google.com with ESMTPSA id gi7sm64894712wib.1.2014.06.26.04.30.06
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 26 Jun 2014 04:30:06 -0700 (PDT)
Message-ID: <53AC0439.9070501@googlemail.com>
Date: Thu, 26 Jun 2014 13:30:01 +0200
From: Krzysztof Okupski <k.okupski@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.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: 1X07sf-0008BN-1M
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: Thu, 26 Jun 2014 11:30:18 -0000

Dear all,

a while ago I've posted a work of mine, namely the Bitcoin Protocol
Specification,
that should by now ring a bell to some of you. Ever since I've received
plenty of
comments from Bitcoin Core developers, Bitcoin enthusiasts and many others.
For the encouraging words and improvement proposals I'm very grateful. I
tried
to incorporate to the best of my abilities and am happy to present a
revised version.
As before, it can be found under:

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

I hope it will prove useful to the community and thank in advance for
any further
improvement proposals.


Kind regards,
Krzysztof