From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Jonas Schnelli <dev@jonasschnelli•ch>
Cc: Andreas Schildbach <andreas@schildbach•de>
Subject: Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default
Date: Mon, 22 Jul 2019 17:17:28 +0000 [thread overview]
Message-ID: <201907221717.30281.luke@dashjr.org> (raw)
In-Reply-To: <122FF05A-8A80-4C13-95D1-BA67B602246A@jonasschnelli.ch>
On Monday 22 July 2019 13:25:25 Jonas Schnelli via bitcoin-dev wrote:
> > I also think as long as we don't have an alternative, we should improve
> > the current filtering for segwit. E.g. testing the scripts themselves
> > and each scriptPubKey spent by any input against the filter would do,
> > and it also fixes the main privacy issue with server-side filtering
> > (wallets have to add two items per address to the filter).
>
> I think the consensus among protocol developers is (please speak up), that
> BIP37 (public server based tx filtering) – in general – was a conceptual
> mistake. Maybe extending it further is the wrong step, especially when
> promising alternatives like BIP158 (neutrino) are around.
Neutrino is very controversial, and NOT less trustful than bloom filters.
It also uses significantly more bandwidth.
It seems a better approach is to add Stratum (Electrum) support, and to limit
usage of all pseudo-SPV protocols to trusted peers.
> The fact that nobody cared about extending it for SW may also underline that
> BIP37 is seen as a conceptual mistake and/or "low interest in further
> extensions“.
Eric Lombrozo added segwit support. While it was never reviewed for Core, it
has been included and supported in Knots since v0.15.1. As I understand it,
his mSIGNA wallet also makes usage of the feature.
Luke
next prev parent reply other threads:[~2019-07-22 17:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 17:46 Matt Corallo
2019-07-21 22:56 ` Andreas Schildbach
2019-07-22 5:01 ` Matt Corallo
2019-07-22 15:58 ` Justus Ranvier
2019-07-26 7:45 ` Tamas Blummer
2019-07-22 8:32 ` Peter Todd
2019-07-22 13:25 ` Jonas Schnelli
2019-07-22 17:17 ` Luke Dashjr [this message]
2019-07-22 17:26 ` Luke Dashjr
2019-07-23 14:47 ` Andreas Schildbach
2019-07-24 13:11 ` Justus Ranvier
2019-07-25 3:04 ` Luke Dashjr
2019-07-26 10:04 ` Jonas Schnelli
2019-07-27 16:10 ` Matt Corallo
2019-07-26 16:48 ` Chris
2019-07-27 19:19 ` Luke Dashjr
2019-07-22 15:04 ` Tom Harding
2019-07-22 15:15 ` Dustin Dettmer
[not found] ` <FF0175BF-1D1F-4AD4-9B13-99D522DBCD83@bridge21.com>
2019-08-14 15:07 ` Matt Corallo
2019-07-22 18:52 Peter
2019-07-22 20:42 ` Greg Sanders
2019-07-22 21:17 ` Luke Dashjr
2019-07-23 20:36 ` Peter Todd
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=201907221717.30281.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dev@jonasschnelli$(echo .)ch \
/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