summaryrefslogtreecommitdiff
path: root/b1/72839e6990836ee8b119b429ad5ce8a9ca6524
blob: ed88d80f333e46965da68c823462b302352908ba (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
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 91857C00
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 18:33:50 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com
	[209.85.213.171])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 258891FF
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 18:33:50 +0000 (UTC)
Received: by igfj19 with SMTP id j19so62958746igf.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 11:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:cc:content-type;
	bh=WPK2I/nQP31XM0x5uYKY8gReqH+QDCcRLFLx4JXdgX4=;
	b=na1qmOjVxq3S/OfxY7u4M8gDp1jMyZLw73bAEBCKpSpwaUEMhKe5yTDDVzpbiUpMV6
	ORN5OnKgN7gz2FxNNOnFQduuhln1oFBX1rb4w4+JaeBMHaKicS9xrvkG+YUhKmpHC3UM
	p+UjDjpZiGQ3Htp8QaspRIh9VVrzpZbjmnF15YWnWaRWLrdok56Id+1hWXwMFwmD8e2i
	t+apy3H6mYlRXz8cpURFmxdttzBwSJ24dLNDuS8kG0ggTXUGtDGKZBffrI47mtfHoaxP
	ktSFXZXWlIF1TEiHMOPGHgyQy+tPbPLakgqqGmg2v88+gFpoKkqqsemtzbrxpAlgXpaf
	2rTw==
X-Received: by 10.50.20.8 with SMTP id j8mr15176042ige.36.1440441229582; Mon,
	24 Aug 2015 11:33:49 -0700 (PDT)
MIME-Version: 1.0
References: <55D6AD19.10305@mattcorallo.com>
	<20150824152955.GA6924@amethyst.visucore.com>
	<55DB566F.1010702@mattcorallo.com> <20150824180044.GA5729@muck>
	<55DB5D49.4050800@mattcorallo.com>
	<CABr1YTceCUPSwUe9M2zUSXcB1qvtmq5PP6=ZBzaw19=VgO79GQ@mail.gmail.com>
	<20150824183050.GB7441@amethyst.visucore.com>
In-Reply-To: <20150824183050.GB7441@amethyst.visucore.com>
From: Eric Lombrozo <elombrozo@gmail.com>
Date: Mon, 24 Aug 2015 18:33:40 +0000
Message-ID: <CABr1YTfLTEH6heGjLXHkBHCjM0v0vGt_TnfskPDJbbJ0w4daZQ@mail.gmail.com>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd75266cf29c5051e12dbf0
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 24 Aug 2015 18:33:50 -0000

--047d7bd75266cf29c5051e12dbf0
Content-Type: text/plain; charset=UTF-8

Indeed, so I don't really have a problem with this proposal.

On Mon, Aug 24, 2015, 11:30 AM Wladimir J. van der Laan <laanwj@gmail.com>
wrote:

> On Mon, Aug 24, 2015 at 06:15:39PM +0000, Eric Lombrozo via bitcoin-dev
> wrote:
> > It would be very useful to not only be able to switch filtering on and
> off
> > globally...but to be able to switch on a per-connection basis. But then
>
> You don't necessarily need to send everyone the same nServices bits.
> E.g. you could give whitelisted peers special privileges.
>
> But only advertize the intersection of your supported services (eg those
> you offer to the general public) in `addr` messages.
>
> Wladimir
>

--047d7bd75266cf29c5051e12dbf0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Indeed, so I don&#39;t really have a problem with this propo=
sal.</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Aug 24, 2015, 11:30=
 AM=C2=A0Wladimir J. van der Laan &lt;<a href=3D"mailto:laanwj@gmail.com">l=
aanwj@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On M=
on, Aug 24, 2015 at 06:15:39PM +0000, Eric Lombrozo via bitcoin-dev wrote:<=
br>
&gt; It would be very useful to not only be able to switch filtering on and=
 off<br>
&gt; globally...but to be able to switch on a per-connection basis. But the=
n<br>
<br>
You don&#39;t necessarily need to send everyone the same nServices bits.<br=
>
E.g. you could give whitelisted peers special privileges.<br>
<br>
But only advertize the intersection of your supported services (eg those yo=
u offer to the general public) in `addr` messages.<br>
<br>
Wladimir<br>
</blockquote></div>

--047d7bd75266cf29c5051e12dbf0--