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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Ve2B0-0005xQ-Oq
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 12:25:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.170 as permitted sender)
client-ip=209.85.192.170; envelope-from=tier.nolan@gmail.com;
helo=mail-pd0-f170.google.com;
Received: from mail-pd0-f170.google.com ([209.85.192.170])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ve2Az-0008Vn-SX
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 12:25:38 +0000
Received: by mail-pd0-f170.google.com with SMTP id v10so10082843pde.15
for <bitcoin-development@lists.sourceforge.net>;
Wed, 06 Nov 2013 04:25:31 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.66.230.233 with SMTP id tb9mr3786607pac.38.1383740731766;
Wed, 06 Nov 2013 04:25:31 -0800 (PST)
Received: by 10.70.61.5 with HTTP; Wed, 6 Nov 2013 04:25:31 -0800 (PST)
In-Reply-To: <5279D89D.5000609@bluematt.me>
References: <5279D89D.5000609@bluematt.me>
Date: Wed, 6 Nov 2013 12:25:31 +0000
Message-ID: <CAE-z3OXQiT-6OXddb9_jpY2Qqbfs+BKAVv3M-rQ4eedwBS2MAg@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b111f3bc73c7104ea813ef7
X-Spam-Score: -0.6 (/)
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]
-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
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bluematt.me]
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Ve2Az-0008Vn-SX
Subject: Re: [Bitcoin-development] [ANN] High-speed Bitcoin Relay Network
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: Wed, 06 Nov 2013 12:25:38 -0000
--047d7b111f3bc73c7104ea813ef7
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo <bitcoin-list@bluematt.me>wrote:
> Relay node details:
> * The relay nodes do some data verification to prevent DoS, but in
> order to keep relay fast, they do not fully verify the data they are
> relaying, thus YOU SHOULD NEVER mine a block building on top of a
> relayed block without fully checking it with your own bitcoin validator
> (as you would any other block relayed from the P2P network).
>
Wouldn't this cause disconnects due to misbehavior?
A standard node connecting to a relay node would receive
blocks/transactions that are not valid in some way and then disconnect.
Have you looked though the official client to find what things are
considered signs that a peer is hostile? I assume things like double
spending checks count as misbehavior and can't be quickly checked by a
relay node.
Maybe another bit could be assigned in the services field as "relay". This
means that the node doesn't do any checking.
Connects to relay nodes could be command line/config file only. Peers
wouldn't connect to them.
--047d7b111f3bc73c7104ea813ef7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo <span dir=3D"ltr"><=
<a href=3D"mailto:bitcoin-list@bluematt.me" target=3D"_blank">bitcoin-list@=
bluematt.me</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Relay node details:<br>
=A0* The relay nodes do some data verification to prevent DoS, but in<br>
order to keep relay fast, they do not fully verify the data they are<br>
relaying, thus YOU SHOULD NEVER mine a block building on top of a<br>
relayed block without fully checking it with your own bitcoin validator<br>
(as you would any other block relayed from the P2P network).<br></blockquot=
e><div><br></div><div>Wouldn't this cause disconnects due to misbehavio=
r?=A0 <br><br>A standard node connecting to a relay node would receive bloc=
ks/transactions that are not valid in some way and then disconnect.<br>
<br></div><div>Have you looked though the official client to find what thin=
gs are considered signs that a peer is hostile?=A0 I assume things like dou=
ble spending checks count as misbehavior and can't be quickly checked b=
y a relay node.<br>
<br></div><div>Maybe another bit could be assigned in the services field as=
"relay".=A0 This means that the node doesn't do any checking=
.=A0 <br><br></div><div>Connects to relay nodes could be command line/confi=
g file only.=A0 Peers wouldn't connect to them.<br>
</div></div></div></div>
--047d7b111f3bc73c7104ea813ef7--
|
