From: Eric Lombrozo <elombrozo@gmail•com>
To: Matt Corallo <lf-lists@mattcorallo•com>, Peter Todd <pete@petertodd•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP
Date: Mon, 24 Aug 2015 18:15:39 +0000 [thread overview]
Message-ID: <CABr1YTceCUPSwUe9M2zUSXcB1qvtmq5PP6=ZBzaw19=VgO79GQ@mail.gmail.com> (raw)
In-Reply-To: <55DB5D49.4050800@mattcorallo.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2219 bytes --]
next prev parent reply other threads:[~2015-08-24 18:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 4:46 Matt Corallo
2015-08-21 5:38 ` Peter Todd
2015-08-21 5:42 ` Peter Todd
2015-08-21 17:55 ` Matt Corallo
2015-08-21 22:06 ` Peter Todd
2015-08-22 1:08 ` Matt Corallo
2015-08-22 1:48 ` Peter Todd
2015-08-24 15:19 ` Tom Harding
2015-08-24 17:39 ` Matt Corallo
2015-08-22 1:08 ` Matt Corallo
2015-08-21 5:48 ` Jeff Garzik
2015-08-21 5:55 ` Peter Todd
2015-08-21 6:01 ` Jeff Garzik
2015-08-21 6:07 ` Peter Todd
2015-08-21 22:15 ` Chris Pacia
2015-08-21 22:25 ` Peter Todd
2015-08-21 23:08 ` Tom Harding
2015-08-24 15:21 ` Mike Hearn
2015-08-21 8:31 ` Andreas Schildbach
2015-08-21 17:53 ` Matt Corallo
2015-08-24 15:29 ` Wladimir J. van der Laan
2015-08-24 17:37 ` Matt Corallo
2015-08-24 17:41 ` Wladimir J. van der Laan
2015-08-24 17:58 ` Eric Lombrozo
2015-08-24 18:00 ` Peter Todd
2015-08-24 18:07 ` Matt Corallo
2015-08-24 18:15 ` Eric Lombrozo [this message]
2015-08-24 18:28 ` Matt Corallo
2015-08-24 18:30 ` Wladimir J. van der Laan
2015-08-24 18:33 ` Eric Lombrozo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABr1YTceCUPSwUe9M2zUSXcB1qvtmq5PP6=ZBzaw19=VgO79GQ@mail.gmail.com' \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(echo .)com \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox