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>
In-Reply-To: <55DB5D49.4050800@mattcorallo.com>
From: Eric Lombrozo <elombrozo@gmail.com>
Date: Mon, 24 Aug 2015 18:15:39 +0000
Message-ID: <CABr1YTceCUPSwUe9M2zUSXcB1qvtmq5PP6=ZBzaw19=VgO79GQ@mail.gmail.com>
To: Matt Corallo <lf-lists@mattcorallo.com>, Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=089e01536c1062914e051e129b5e
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP
Precedence: list

--089e01536c1062914e051e129b5e
Content-Type: text/plain; charset=UTF-8

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
again, perhaps it would be smarter to ditch the whole bloom filter thing in
favor of an actual client/server architecture with proper authentication
and access controls.

The RPC was supposed to be this client/server architecture...but in
practice it sucks so bad for doing anything beyond administering a node
instance you fully control yourself that I eschewed it entirely in my
wallet design.

On Mon, Aug 24, 2015, 11:07 AM Matt Corallo via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> BIP 111 was assigned, pull request (with the proposed changes) available
> at https://github.com/bitcoin/bips/pull/183
>
> Matt
>
> On 08/24/15 18:00, Peter Todd wrote:
> > On Mon, Aug 24, 2015 at 05:37:51PM +0000, Matt Corallo via bitcoin-dev
> wrote:
> >> Its more of a statement of "in the future, we expect things to happen
> >> which would make this an interesting thing to do, so we state here that
> >> it is not against spec to do so". Could reword it as "NODE_BLOOM is
> >> distinct from NODE_NETWORK, and it is legal to advertise NODE_BLOOM but
> >> not NODE_NETWORK (though there is little reason to do so now, some
> >> proposals may make this more useful in the future)"?
> >
> > ACK
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<p dir=3D"ltr">It would be very useful to not only be able to switch filter=
ing on and off globally...but to be able to switch on a per-connection basi=
s. But then again, perhaps it would be smarter to ditch the whole bloom fil=
ter thing in favor of an actual client/server architecture with proper auth=
entication and access controls.</p>
<p dir=3D"ltr">The RPC was supposed to be this client/server architecture..=
.but in practice it sucks so bad for doing anything beyond administering a =
node instance you fully control yourself that I eschewed it entirely in my =
wallet design.<br>
</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Aug 24, 2015, 11:07=
 AM=C2=A0Matt Corallo via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lis=
ts.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">BIP 111 was assigned, pull reques=
t (with the proposed changes) available<br>
at <a href=3D"https://github.com/bitcoin/bips/pull/183" rel=3D"noreferrer" =
target=3D"_blank">https://github.com/bitcoin/bips/pull/183</a><br>
<br>
Matt<br>
<br>
On 08/24/15 18:00, Peter Todd wrote:<br>
&gt; On Mon, Aug 24, 2015 at 05:37:51PM +0000, Matt Corallo via bitcoin-dev=
 wrote:<br>
&gt;&gt; Its more of a statement of &quot;in the future, we expect things t=
o happen<br>
&gt;&gt; which would make this an interesting thing to do, so we state here=
 that<br>
&gt;&gt; it is not against spec to do so&quot;. Could reword it as &quot;NO=
DE_BLOOM is<br>
&gt;&gt; distinct from NODE_NETWORK, and it is legal to advertise NODE_BLOO=
M but<br>
&gt;&gt; not NODE_NETWORK (though there is little reason to do so now, some=
<br>
&gt;&gt; proposals may make this more useful in the future)&quot;?<br>
&gt;<br>
&gt; ACK<br>
&gt;<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--089e01536c1062914e051e129b5e--