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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1X4qVh-0005KD-Bi
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Jul 2014 11:58:05 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.174 as permitted sender)
client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f174.google.com;
Received: from mail-ob0-f174.google.com ([209.85.214.174])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X4qVg-0006cK-6J
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Jul 2014 11:58:05 +0000
Received: by mail-ob0-f174.google.com with SMTP id va2so7901637obc.5
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Jul 2014 04:57:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.125.195 with SMTP id ms3mr46021922oeb.40.1404907078702;
Wed, 09 Jul 2014 04:57:58 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Wed, 9 Jul 2014 04:57:58 -0700 (PDT)
In-Reply-To: <2098096.PBWFJaSQzq@crushinator>
References: <53AC0439.9070501@googlemail.com>
<CANVdSAp_1wBYuh2+hcR_HCtOjmwDm8EJdWLdJ4ZWcd5PARVW6A@mail.gmail.com>
<CAC0TF=kuC9zdyvJXKiBzV=5anAt5szcD-Otp1EeoD5ukm-W1Uw@mail.gmail.com>
<2098096.PBWFJaSQzq@crushinator>
Date: Wed, 9 Jul 2014 13:57:58 +0200
X-Google-Sender-Auth: jglE4wEUOmrOkyFhAX1PO-OSI54
Message-ID: <CANEZrP1uuPReuOR=0PS5bff43umk-PP9OgYd-MTycFLsqnTp9g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=047d7b33cf285e5c4804fdc16bb5
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1X4qVg-0006cK-6J
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: Wed, 09 Jul 2014 11:58:05 -0000
--047d7b33cf285e5c4804fdc16bb5
Content-Type: text/plain; charset=UTF-8
On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <bip@mattwhitlock.name>
wrote:
> Is anyone working on a similar specification document for Satoshi's P2P
> protocol? I know how blocks and transactions are structured and verified,
> but I'm interested in knowing how they're communicated over the network.
There's a high level guide here:
https://bitcoin.org/en/developer-guide#p2p-network
It's not a protocol specification however, more a lay-of-the-land type
description. The protocol is not very complicated however. The wiki page
describes it adequately. It's basically just a framing mechanism with
excessively aggressive checksumming, a version handshake, an inventory
mechanism to cut down on bandwidth usage, the alerts, and that's about it.
--047d7b33cf285e5c4804fdc16bb5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <span dir=3D"ltr"><<a href=3D=
"mailto:bip@mattwhitlock.name" target=3D"_blank">bip@mattwhitlock.name</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Is anyone working on a similar specification document for =
Satoshi's P2P protocol? =C2=A0I know how blocks and transactions are st=
ructured and verified, but I'm interested in knowing how they're co=
mmunicated over the network.</blockquote>
<div><br></div><div>There's a high level guide here:</div><div><br></di=
v><div><a href=3D"https://bitcoin.org/en/developer-guide#p2p-network">https=
://bitcoin.org/en/developer-guide#p2p-network</a></div><div><br></div><div>
It's not a protocol specification however, more a lay-of-the-land type =
description. The protocol is not very complicated however. The wiki page de=
scribes it adequately. It's basically just a framing mechanism with exc=
essively aggressive checksumming, a version handshake, an inventory mechani=
sm to cut down on bandwidth usage, the alerts, and that's about it.</di=
v>
</div></div></div>
--047d7b33cf285e5c4804fdc16bb5--
|
