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
112
113
114
115
116
117
118
119
120
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
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 1WXECt-0007pd-JP
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 18:23:43 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.47 as permitted sender)
client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f47.google.com;
Received: from mail-oa0-f47.google.com ([209.85.219.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXECs-0006Eu-DL
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 18:23:43 +0000
Received: by mail-oa0-f47.google.com with SMTP id i11so7132412oag.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 11:23:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.76.194 with SMTP id m2mr8515839oew.47.1396895017022; Mon,
07 Apr 2014 11:23:37 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Mon, 7 Apr 2014 11:23:36 -0700 (PDT)
In-Reply-To: <6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<5342C833.5030906@gmail.com>
<CAAS2fgTqBfEPXh2dfcL_ke6c0wfXw4qUM1rAYMkAHcAM6mYH+g@mail.gmail.com>
<6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net>
Date: Mon, 7 Apr 2014 20:23:36 +0200
X-Google-Sender-Auth: aSHqr6mox6nPElFCPrqDVHtC21c
Message-ID: <CANEZrP1-9LpPw4WuY8bfsEG0OLoDECXTfQCoZsZ4tmOn2H7Omw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Chris Williams <chris@icloudtools.net>
Content-Type: multipart/alternative; boundary=047d7b33cea6473f9704f677f7c0
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: 1WXECs-0006Eu-DL
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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, 07 Apr 2014 18:23:43 -0000
--047d7b33cea6473f9704f677f7c0
Content-Type: text/plain; charset=UTF-8
>
> * Sent 456.5 gb data
>
> At my geographic service location (Singapore), this cost about $90 last
> month for bandwidth alone.
One of the reasons I initiated the (now stalled) PayFile project was in
anticipation of this problem:
https://github.com/mikehearn/PayFile
http://www.youtube.com/watch?v=r0BXnWlnIi4&feature=youtu.be
At some point if you want to actually download and validate the full block
chain from scratch, you will have to start paying for it I'm sure.
In the meantime:
1. Getting headers-first implemented and rolled out everywhere would
reduce the amount of redundant downloading and hopefully reduce transmit
traffic network-wide.
2. Implementing chain pruning would allow people to control upload
bandwidth consumption by reducing the amount of disk storage they allow.
--047d7b33cea6473f9704f677f7c0
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"><blo=
ckquote 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;paddi=
ng-left:1ex">
* Sent 456.5 gb data<br>
<br>
At my geographic service location (Singapore), this cost about $90 last mon=
th for bandwidth alone.</blockquote><div><br></div><div>One of the reasons =
I initiated the (now stalled) PayFile project was in anticipation of this p=
roblem:</div>
<div><br></div><div><a href=3D"https://github.com/mikehearn/PayFile">https:=
//github.com/mikehearn/PayFile</a></div><div><a href=3D"http://www.youtube.=
com/watch?v=3Dr0BXnWlnIi4&feature=3Dyoutu.be">http://www.youtube.com/wa=
tch?v=3Dr0BXnWlnIi4&feature=3Dyoutu.be</a></div>
<div><br></div><div>At some point if you want to actually download and vali=
date the full block chain from scratch, you will have to start paying for i=
t I'm sure.</div><div><br></div><div>In the meantime:</div><div><ol>
<li>Getting headers-first implemented and rolled out everywhere would reduc=
e the amount of redundant downloading and hopefully reduce transmit traffic=
network-wide.<br></li><li>Implementing chain pruning would allow people to=
control upload bandwidth consumption by reducing the amount of disk storag=
e they allow.</li>
</ol><div><br></div></div></div></div></div>
--047d7b33cea6473f9704f677f7c0--
|
