summaryrefslogtreecommitdiff
path: root/39/7c4a9d713868144f5840dc3ebde5e52f3c0c59
blob: 5e901c2469200ac07542f1d4ff760a7490461390 (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
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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 837784A5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  3 May 2017 22:45:38 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com
	[209.85.128.172])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6C25E138
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  3 May 2017 22:45:37 +0000 (UTC)
Received: by mail-wr0-f172.google.com with SMTP id l9so1704474wre.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 03 May 2017 15:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to; bh=2IS2IDXwyaGZgqIyUcfpVSLLIxeIl7T7QGVjvMswA9w=;
	b=bP+FGEA5a73Z4TGTOKQwZ8dR903uNDaELC8sb3ZIHZ4Lkm3giF0DeHTuLV9N97j1nY
	HL7K8svKIncx/ItMOR7JxWAvJKtahA8E/uKPWH/XYUilzQQXilpst60MYd19MuVYE23P
	91VawPGzWgqpZBTct+Y7/FRddFWWq/dNIrNqRzd5gUvmcpr9Q6kmnHwHSw9C+DVUsQDS
	hiVVaPEkNL6g3vrqwqzg4CyYd2BwG0ggU/jjbbYlJ94OsGJODZCS1RJGypca5MBi2eDz
	XVFzIyy1zWNzkp5aDzdKEcUxy2H/m8WnxX12rnvDhex55hx2u9Q9oTEW6aKoyWB8ESi9
	036A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to;
	bh=2IS2IDXwyaGZgqIyUcfpVSLLIxeIl7T7QGVjvMswA9w=;
	b=lqvAuhUEzWHGL0Hc+tWbLIrnWo2g1PIpPO+OHAGJUPmYSLG7dG6WFzSUXqt1jIENnJ
	6YOQu5soioieQJdzdkgbY407eoQlh6SfPR4B6cpJjqx8kjdcfynGm+N9ZXYnbMNuqFg0
	XKctISfozlAc9FILJq7lodqhPbRD6Ju1LutFzIOkj8+HpIBNbMSDF5gklq8MNTKP9vbS
	Wz2f8DUrBXG7EslYPQJRmxWBjh/WsD7Dqn1k2cpj4FVj+XCSYi6GkYq7pbPsX4pn6rWm
	xUF68EKoXnydKX/FPZnojMjF/HDALs3fb/zI1g+j2Mytkf5Tl1/tTbc+BIA4ZjDVbT+J
	I0jQ==
X-Gm-Message-State: AN3rC/7mMHMES3W5VuK9aHmBY4TZUvQI6Db0FO4w56oCrThlw32DoPnZ
	ROYB6QrM2XrZip1A
X-Received: by 10.223.147.225 with SMTP id 88mr18095538wrp.74.1493851535804;
	Wed, 03 May 2017 15:45:35 -0700 (PDT)
Received: from [192.168.1.10] (ANice-654-1-42-58.w83-201.abo.wanadoo.fr.
	[83.201.101.58]) by smtp.googlemail.com with ESMTPSA id
	t85sm75759wmt.23.2017.05.03.15.45.34
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Wed, 03 May 2017 15:45:35 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAFVRnypbQQ-vsSLqv48cYaqTCty4R1DmFRqfAvxe4mAqyQNXxQ@mail.gmail.com>
	<CAAS2fgT5pJh68xufv_81+N8K0asxH16WdX7PLLXGjRPmJOkYFQ@mail.gmail.com>
	<CAJowKg+UTKeU0Dj5pJbtw+LZtO9kn5LBJum9Akd11zCsW+6o4Q@mail.gmail.com>
	<CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <fbf666d7-40e1-f625-9bee-7f93e145cf6b@gmail.com>
Date: Thu, 4 May 2017 00:45:40 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101
	Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------94524430C44E8A4615A6B492"
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, 
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Small Nodes: A Better Alternative to Pruned Nodes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 03 May 2017 22:45:38 -0000

This is a multi-part message in MIME format.
--------------94524430C44E8A4615A6B492
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit



Le 03/05/2017 à 21:10, Natanael via bitcoin-dev a écrit :
>
> Den 3 maj 2017 16:05 skrev "Erik Aronesty via bitcoin-dev"
> <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>>:
>
>     > But as you've observed, the failure probabilities are rather high,
>     > especially if an active attacker targets nodes carrying less
>     commonly
>     > available blocks. 
>
>     Wouldn't the solution be for nodes to use whatever mechanism an
>     attacker uses to determine less commonly available blocks and
>     choose to store a random percentage of them as well as their
>     deterministic random set? 
>
>     IE X blocks end of chain (spv bootstrap), Y% deterministic random
>     set,  Z% patch/fill set to deter attacks
>
>
> Then he uses Sybil attacks to obscure what's actually rare and not.

> Even proof of storage isn't enough,you need proof of INDEPENDENT storage

Yes

> , which is essentially impossible

No, the bittorrent network is a good example

> , as well as a way of determining which nodes are run by the same
> people (all the AWS nodes should essentially count as one).

No, this one is impossible and you don't care in fact, as long as the
system forbids the nodes to position themselves where they like and can
check that the nodes are behaving correctly, same people's nodes/IPs
would then just do the job

And if you add to this a rewarding system that is not necessarily
profitable then you eliminate the incentive for sybil attacking the
network (like the "tip" proposal today) while motivating those that have
the resources to run full nodes, then increasing independence


>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-- 
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms


--------------94524430C44E8A4615A6B492
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">Le 03/05/2017 à 21:10, Natanael via
      bitcoin-dev a écrit :<br>
    </div>
    <blockquote
cite="mid:CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div data-smartmail="gmail_signature" dir="auto"><br>
        </div>
        <div class="gmail_extra" dir="auto">
          <div class="gmail_quote">Den 3 maj 2017 16:05 skrev "Erik
            Aronesty via bitcoin-dev" &lt;<a moz-do-not-send="true"
              href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt;:<br
              type="attribution">
            <blockquote class="quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">
                <div>
                  <div class="quoted-text">
                    <div>&gt; But as you've observed, the failure
                      probabilities are rather high,<br>
                      &gt; especially if an active attacker targets
                      nodes carrying less commonly<br>
                      &gt; available blocks.  <br>
                      <br>
                    </div>
                  </div>
                  Wouldn't the solution be for nodes to use whatever
                  mechanism an attacker uses to determine less commonly
                  available blocks and choose to store a random
                  percentage of them as well as their deterministic
                  random set?  <br>
                  <br>
                  IE X blocks end of chain (spv bootstrap), Y%
                  deterministic random set,  Z% patch/fill set to deter
                  attacks<br>
                </div>
              </div>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Then he uses Sybil attacks to obscure what's
          actually rare and not. </div>
      </div>
    </blockquote>
    <br>
    <blockquote
cite="mid:CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div dir="auto">Even proof of storage isn't enough,you need
          proof of INDEPENDENT storage</div>
      </div>
    </blockquote>
    <br>
    Yes<br>
    <br>
    <blockquote
cite="mid:CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div dir="auto">, which is essentially impossible</div>
      </div>
    </blockquote>
    <br>
    No, the bittorrent network is a good example<br>
    <br>
    <blockquote
cite="mid:CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div dir="auto">, as well as a way of determining which nodes
          are run by the same people (all the AWS nodes should
          essentially count as one). <br>
        </div>
      </div>
    </blockquote>
    <br>
    No, this one is impossible and you don't care in fact, as long as
    the system forbids the nodes to position themselves where they like
    and can check that the nodes are behaving correctly, same people's
    nodes/IPs would then just do the job<br>
    <br>
    And if you add to this a rewarding system that is not necessarily
    profitable then you eliminate the incentive for sybil attacking the
    network (like the "tip" proposal today) while motivating those that
    have the resources to run full nodes, then increasing independence<br>
    <br>
    <br>
    <blockquote
cite="mid:CAAt2M1_TH=1Xw=65QxxCHMZzE-fzC3UhRaEk+KkKY2SHkN6CbQ@mail.gmail.com"
      type="cite">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
  </body>
</html>

--------------94524430C44E8A4615A6B492--