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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ricardojdfilipe@gmail.com>) id 1Ud0xn-0002vP-DM
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 16:23:31 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.52 as permitted sender)
client-ip=209.85.215.52; envelope-from=ricardojdfilipe@gmail.com;
helo=mail-la0-f52.google.com;
Received: from mail-la0-f52.google.com ([209.85.215.52])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ud0xm-0003M4-Gr
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 16:23:31 +0000
Received: by mail-la0-f52.google.com with SMTP id fo13so3168310lab.25
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 May 2013 09:23:23 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.19.199 with SMTP id h7mr20854024lae.22.1368721403760;
Thu, 16 May 2013 09:23:23 -0700 (PDT)
Received: by 10.112.127.34 with HTTP; Thu, 16 May 2013 09:23:23 -0700 (PDT)
In-Reply-To: <CA+8xBpdY9Vi+K0Cxr_AJ25Y2ieB=0EueiPHq92pdr5QdBnNj_A@mail.gmail.com>
References: <CALC81CNMTWhAQ8VSxToGcSPeJmfFJrANrdXONseTq1=WKm4=7w@mail.gmail.com>
<CA+8xBpdY9Vi+K0Cxr_AJ25Y2ieB=0EueiPHq92pdr5QdBnNj_A@mail.gmail.com>
Date: Thu, 16 May 2013 17:23:23 +0100
Message-ID: <CALC81CMRKCyvA+q7tQ8GUh_-T1N67_RQru+Vu-UCfaGQG_oVSQ@mail.gmail.com>
From: Ricardo Filipe <ricardojdfilipe@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(ricardojdfilipe[at]gmail.com)
-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: 1Ud0xm-0003M4-Gr
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Service bits for pruned 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: Thu, 16 May 2013 16:23:31 -0000
Of course.
My proposal was just for the pruned nodes.
I.e. You would have a majority (maybe not even a majority required) of
nodes storing the whole blockchain and pruned nodes would store
"random" parts of the blockchain, according to the resources they
have, which would be organized as a DHT.
2013/5/16 Jeff Garzik <jgarzik@exmulti.com>:
> On Thu, May 16, 2013 at 7:26 AM, Ricardo Filipe
> <ricardojdfilipe@gmail.com> wrote:
>> We would only end up with few copies of the historic data if users
>> could choose what parts of the blockchain to store. Simply store
>> chunks randomly, according to users available space, and give priority
>> to the "N most recent" chunks to have more replicas in the network.
>>
>> You don't need bittorrent specifically for a DHT, if publicity is a
>> problem. There are many DHT proposals and implementations, and i bet
>> one of them should be more suitable to the bitcoin network than
>> bittorrent's.
>
> That's just about the worst thing you could do for bitcoin. DoS one
> part of the DHT, you DoS the entire blockchain by breaking the chain.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
|
