From: Peter Todd <pete@petertodd•org>
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP
Date: Thu, 20 Aug 2015 23:07:17 -0700 [thread overview]
Message-ID: <20150821060716.GA31674@muck> (raw)
In-Reply-To: <CADm_WcanqF7oHn7huKuYP8iFWmY4XE58tG01M_Nqg9qx6YFu9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Fri, Aug 21, 2015 at 02:01:06AM -0400, Jeff Garzik wrote:
> I don't see any link to data backing up "Bloom filter usage has declined
> significantly"
>
> Is there actual data showing this feature's use is declining or
> non-existent?
I run a number of high speed nodes and while I don't have historical
logs handy over time, I've noticed a drop from about %5-%10 SPV clients
at any one time to closer to %1 (Matt: you have a few TB of logs saved
don't you?)
Also, as I mentioned, just look at the popularity of wallets such as
Mycelium that are not adopting bloom filters, but going with SPV
verification of block headers w/ lookup servers.
Anyway, look at the analogous implementation of NODE_GETUTXO's, which
helpfully has provided the infrastructure for wallets that need bloom
filters to find appropriate nodes to connect too - we certainely aren't
seeing any shortages of nodes for those wallets to use.
--
'peter'[:-1]@petertodd.org
00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-08-21 6:07 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 [this message]
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
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=20150821060716.GA31674@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jgarzik@gmail$(echo .)com \
/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