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
121
122
123
124
125
126
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WXMxo-0007Oq-9S
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 03:44:44 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.169 as permitted sender)
client-ip=74.125.82.169; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f169.google.com;
Received: from mail-we0-f169.google.com ([74.125.82.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXMxk-0007WQ-TX
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 03:44:44 +0000
Received: by mail-we0-f169.google.com with SMTP id w62so338402wes.14
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 20:44:34 -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=l6dDLew+xxCzlthqs7g+omky5EHllHKIalm5DQHs/3E=;
b=hO6m+Z2rjcyHrY6QPppJ3C/ZPjAPuOzErQ/vjdCaz2OZQT4Et4t/u4k6veUGxESYlV
gvTomckXKbdio+mOEIK31ORCjUrd6P0KDeNTXTv06T8AOJouiVYOgu4Hcl7FlrT5zpKq
OgaVxgWvTGgeuBe7GBeAadl7ZHJZgU1UNUjAjazl03wxSM347uVYxyEepa4uyI67S0hD
5pvciMciEyEQrvN5+FdJooN0vNrO9/xWg6H0fFbQQry0p7YITfCEu4rayvcSEFLiLDhO
kBn4Uvgm4Zgm7IVpPUNktgKx3vunCZU60GS6ZDWigtcZTXFHRTdEwwdzhgPesw62FfJ1
pehg==
X-Gm-Message-State: ALoCoQldrh6DUjhxQhdcX+EyNaxlAvSf3iiUWfH8BDjrEf1H3DX/ry3d0zri7c2UoSGfc6BKdl78
X-Received: by 10.194.19.161 with SMTP id g1mr1397829wje.20.1396928674749;
Mon, 07 Apr 2014 20:44:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.243.138 with HTTP; Mon, 7 Apr 2014 20:44:14 -0700 (PDT)
In-Reply-To: <CAAS2fgQaJ6P4Aj2A5Zox+CiGQK6jHvF1CkLH1R6xbadYhUXO2g@mail.gmail.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<5342C833.5030906@gmail.com>
<CAAS2fgTqBfEPXh2dfcL_ke6c0wfXw4qUM1rAYMkAHcAM6mYH+g@mail.gmail.com>
<6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net>
<CANEZrP1-9LpPw4WuY8bfsEG0OLoDECXTfQCoZsZ4tmOn2H7Omw@mail.gmail.com>
<6D6E55CE-2F04-4C34-BEE6-98AEF1478346@bitsofproof.com>
<CAAS2fgQaJ6P4Aj2A5Zox+CiGQK6jHvF1CkLH1R6xbadYhUXO2g@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 7 Apr 2014 23:44:14 -0400
Message-ID: <CAJHLa0MOB2=1JNfXCb-DY24ssTi7hVFi6H7JDaeVp5oOUUMy=A@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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: 1WXMxk-0007WQ-TX
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: Tue, 08 Apr 2014 03:44:44 -0000
Being Mr. Torrent, I've held open the "80% serious" suggestion to
simply refuse to serve blocks older than X (3 months?).
That forces download by other means (presumably torrent).
I do not feel it is productive for any nodes on the network to waste
time/bandwidth/etc. serving static, ancient data. There remain, of
course, issues of older nodes and "getting the word out" that prevents
this switch from being flipped on tomorrow.
On Mon, Apr 7, 2014 at 2:49 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Mon, Apr 7, 2014 at 11:35 AM, Tamas Blummer <tamas@bitsofproof.com> wrote:
>> BTW, did we already agree on the service bits for an archive node?
>
> I'm still very concerned that a binary archive bit will cause extreme
> load hot-spotting and the kind of binary "Use lots of resources YES or
> NO" I think we're currently suffering some from, but at that point
> enshrined in the protocol.
>
> It would be much better to extend the addr messages so that nodes can
> indicate a range or two of blocks that they're serving, so that all
> nodes can contribute fractionally according to their means. E.g. if
> you want to offer up 8 GB of distributed storage and contribute to the
> availability of the blockchain, without having to swollow the whole
> 20, 30, 40 ... gigabyte pill.
>
> Already we need that kind of distributed storage for the most recent
> blocks to prevent extreme bandwidth load on archives, so extending it
> to arbitrary ranges is only more complicated because there is
> currently no room to signal it.
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
