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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1UZO9E-0007Ig-GR
for bitcoin-development@lists.sourceforge.net;
Mon, 06 May 2013 16:20:20 +0000
X-ACL-Warn:
Received: from mail-pd0-f170.google.com ([209.85.192.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UZO9C-0007IE-FT
for bitcoin-development@lists.sourceforge.net;
Mon, 06 May 2013 16:20:20 +0000
Received: by mail-pd0-f170.google.com with SMTP id 10so2089505pdi.1
for <bitcoin-development@lists.sourceforge.net>;
Mon, 06 May 2013 09:20:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-received:x-originating-ip:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
bh=sZDoE+AO4K60RCoZmXcADcDDrUoGUhm+Gtux18ERI9Y=;
b=et19h+DMupg5ac113Q6V2/7hfMKXQJk4nb6ig6HzgLXbk5QCKSndwu6l5qhdW/POOg
/Va0evrE1l+zrpTQ9BgxQvPXd7u0Qn4NndyUfhARPHjcl6Ui0XLSTChfdJ2BXytF0GaQ
Py/iM6gHRT7wQN6F9ZzmJVe66CdLzPZBA74UA/4kedlwwejxpI9yGrJna3fB0in7EmL1
NwU1lR9yzmEEPWE0lpgZx4Oh1qFQDYcwFNTbtObA0Eudlt/rn8CE1lTLCC/eNb9n0zbb
fyVlf777YeehdGmMXp4AbqxtCtOePvxgQXM43hNI9SqF5KFJ1P1TKilSOAXQbtzLwCue
0ycg==
MIME-Version: 1.0
X-Received: by 10.68.92.100 with SMTP id cl4mr26624008pbb.130.1367857212572;
Mon, 06 May 2013 09:20:12 -0700 (PDT)
Received: by 10.68.240.106 with HTTP; Mon, 6 May 2013 09:20:12 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <20130506161216.GA5193@petertodd.org>
References: <CANEZrP1YFCLmasOrdxdKDP1=x8nKuy06kGRqZwpnmnhe3-AroA@mail.gmail.com>
<20130506161216.GA5193@petertodd.org>
Date: Mon, 6 May 2013 12:20:12 -0400
Message-ID: <CA+8xBpfdY7GsQiyrHuOG-MqXon0RGShpg2Yv-KeAXQ-503kAsA@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkcAbW+xcAhwPJ2arOzRp9k/sdmo8aIvzap3VqjNTEO4e6sc7LeibwzClKFchHePawzNqtO
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 [209.85.192.170 listed in list.dnswl.org]
X-Headers-End: 1UZO9C-0007IE-FT
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Discovery/addr packets (was: 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: Mon, 06 May 2013 16:20:20 -0000
On Mon, May 6, 2013 at 12:12 PM, Peter Todd <pete@petertodd.org> wrote:
> I've noticed on my Android phone how it often takes quite awhile to find
> a peer that will actually accept an incoming connection, which isn't
> surprising really: why should a regular node care about responding to
> SPV nodes quickly?
>
> For fast startup you would be better served with dedicated nodes that
> are backed by fast hardware and high bandwidth internet connections.
> You can discourage non-SPV use by refusing to relay full blocks.
>
> You can have trusted individuals vouch for these special servers with
> SSL certificates so you run less of a risk of connecting to a malicious
> one trying to limit what information you see. For the initial
> implementation, maybe just make a quick SSL accessible service with HTTP
> GET so you don't have to integrate SSL into the network protocol and
> have a couple of these HTTP GETable servers running. (IE, the trust is
> actually that the SPV seed is honest)
>
> Security will be no worse than before - if any one server/seed is honest
> you're ok - and hopefully better due to the accountability. Obviously
Indeed, the DNS seeds are just servers run by trusted individuals anyway.
In either case, bitcoinj definitely wants fixing for its over-reliance
on DNS seeds. This has been noted as a problem for a while.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
