blob: 4dd0d3c14e287409daedaa1099d7728020a03e60 (
plain)
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
|
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 <bip@mattwhitlock.name>) id 1X4bcu-0005zF-Ro
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Jul 2014 20:04:32 +0000
X-ACL-Warn:
Received: from qmta03.westchester.pa.mail.comcast.net ([76.96.62.32])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1X4bcr-0002bm-Pi for bitcoin-development@lists.sourceforge.net;
Tue, 08 Jul 2014 20:04:32 +0000
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74])
by qmta03.westchester.pa.mail.comcast.net with comcast
id PvcB1o0071c6gX853w4Ql7; Tue, 08 Jul 2014 20:04:24 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
by omta23.westchester.pa.mail.comcast.net with comcast
id Pw4M1o0124VnV2P3jw4Qqu; Tue, 08 Jul 2014 20:04:24 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Date: Tue, 08 Jul 2014 16:04:19 -0400
Message-ID: <2098096.PBWFJaSQzq@crushinator>
User-Agent: KMail/4.13.2 (Linux/3.12.20-gentoo; KDE/4.13.2; x86_64; ; )
In-Reply-To: <CAC0TF=kuC9zdyvJXKiBzV=5anAt5szcD-Otp1EeoD5ukm-W1Uw@mail.gmail.com>
References: <53AC0439.9070501@googlemail.com>
<CANVdSAp_1wBYuh2+hcR_HCtOjmwDm8EJdWLdJ4ZWcd5PARVW6A@mail.gmail.com>
<CAC0TF=kuC9zdyvJXKiBzV=5anAt5szcD-Otp1EeoD5ukm-W1Uw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [76.96.62.32 listed in list.dnswl.org]
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: 1X4bcr-0002bm-Pi
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: Tue, 08 Jul 2014 20:04:33 -0000
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.
|
