1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
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 <jgarzik@bitpay.com>) id 1X6jrj-0002c2-Ud
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 17:16:39 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.176 as permitted sender)
client-ip=209.85.212.176; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f176.google.com;
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X6jrj-00065m-0v
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 17:16:39 +0000
Received: by mail-wi0-f176.google.com with SMTP id bs8so2989139wib.15
for <bitcoin-development@lists.sourceforge.net>;
Mon, 14 Jul 2014 10:16:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=K0dG7bWCrfPji74bjos2E0sEXKewu5wxRV5rAFyAQs8=;
b=gJGipMIKmHWQb2IfJROXVFNA6D0nmGHK3M08AbARD0ZC6UbwOsMinZWj/USZC1snxc
V57CIG5+Sf1m/HZju3YQEW2Nz7mCCbO+WvsIKrY1sARQ5UWdmL1ys2s8HULa75IORabx
q01OuHGZI8jEQOVPYfnDdWsJP+4nFpSPQ/q39dBEHz9KsN63jhiHWp7rTizgGsEGjn8y
gkVxu7ajyvvjGXzkY9HN5/G1BlecEVCT7Gp+y1lIw0n3Ffh8jefEs4sLnk0Wx/dwWEmB
3BVVGHHItEuR+yb8nf6fqI3QLEdxo0XvJWqEh4U2Zngzi4LsvaumDsfKY3L4bnD+6XnP
wAaA==
X-Gm-Message-State: ALoCoQmNx2V2bZZTMTTuc3jafp+Jc1tYK7/w8gxGMqFibK5Vg9edGqp6aRA8uDP7mmBJO5vWBWE1
X-Received: by 10.180.208.13 with SMTP id ma13mr26161667wic.45.1405358192783;
Mon, 14 Jul 2014 10:16:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Mon, 14 Jul 2014 10:16:12 -0700 (PDT)
In-Reply-To: <53C3ECD0.2000809@googlemail.com>
References: <53C3ECD0.2000809@googlemail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 14 Jul 2014 13:16:12 -0400
Message-ID: <CAJHLa0NHtFF58o7yG_r9gEWC=p7_E=i7Ed2C5eMBSEB078h+aQ@mail.gmail.com>
To: Krzysztof Okupski <k.okupski@googlemail.com>
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 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: 1X6jrj-00065m-0v
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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: Mon, 14 Jul 2014 17:16:40 -0000
On Mon, Jul 14, 2014 at 10:44 AM, Krzysztof Okupski
<k.okupski@googlemail.com> wrote:
> I've renamed it to "Bitcoin Developer Specification" a little while ago.
> Maybe it should rather be named "Bitcoin Developer Reference"? Either
> way, creating a good description of Bitcoin is an incremental process
> and there are certainly many quirks I'm not aware of. I hope that
> together we will soon be able to fill in the missing gaps.
Firstly, it is an excellent document, and it should be useful in
educating others.
I do agree that "specification" is not a good word to use.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
