📅 Original date posted:2018-06-02
📝 Original message:On Sat, Jun 2, 2018 at 10:02 PM, Tamas Blummer via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Years of experience implementing wallets with BIP 37
pretty much us that all these filter things are a total waste of time.
BIP37 use is nearly dead on the network-- monitor your own nodes to
see the actual use of the filters: it's very low. I see under average
of 1 peer per day using it.
Moreover the primary complaint from users about BIP37 vs the
alternatives they're choosing over it (electrum and web wallets) is
that the sync time is too long-- something BIP158 doesn't improve.
So if we were going to go based on history we wouldn't bother with on
P2P at all. But I think the history's lesson here may mostly be an
accident, and that the the non-use of BIP37 is due more to the low
quality and/or abandoned status of most BIP37 implementing software,
rather than a fundamental lack of utility. Though maybe we do find
out that once someone bothers implementing a PIR based scanning
mechanism (as electrum has talked about on and off for a while now)
we'll lose another advantage.
BIP37 also got a number of things wrong-- what went into the filters
was a big element in that (causing massive pollution of matches due to
useless data), along with privacy etc. This kind of approach will
have the best chances if it doesn't repeat the mistakes... but also
it'll have the best chances if it has good security, and getting SPV-
equivalent security will require committing the filters, but
committing them is a big step because then the behaviour becomes
consensus normative-- it's worth spending a few months of extra
iteration getting the design as good as possible before doing that
(which is what we've been seeing lately).
npub1f2…crwet
2023-06-07 20:12:39
in reply to nevent1q…sgdy
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 20:12:39Event JSON
{
"id": "58cb956a28389e5493b2ba2adff60f7ce2718813cb60e94ae0a55743abc6edac",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686161559,
"kind": 1,
"tags": [
[
"e",
"51a146fc69b159388af76f4dbc680a6d56f40357ab923d85aeb4f302294e74e6",
"",
"root"
],
[
"e",
"20c74f67966d0d360e4c9535a77ace4f1ed3ef12bd9e9e727e73a394bd1d159a",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2018-06-02\n📝 Original message:On Sat, Jun 2, 2018 at 10:02 PM, Tamas Blummer via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Years of experience implementing wallets with BIP 37\n\npretty much us that all these filter things are a total waste of time.\nBIP37 use is nearly dead on the network-- monitor your own nodes to\nsee the actual use of the filters: it's very low. I see under average\nof 1 peer per day using it.\n\nMoreover the primary complaint from users about BIP37 vs the\nalternatives they're choosing over it (electrum and web wallets) is\nthat the sync time is too long-- something BIP158 doesn't improve.\n\nSo if we were going to go based on history we wouldn't bother with on\nP2P at all. But I think the history's lesson here may mostly be an\naccident, and that the the non-use of BIP37 is due more to the low\nquality and/or abandoned status of most BIP37 implementing software,\nrather than a fundamental lack of utility. Though maybe we do find\nout that once someone bothers implementing a PIR based scanning\nmechanism (as electrum has talked about on and off for a while now)\nwe'll lose another advantage.\n\nBIP37 also got a number of things wrong-- what went into the filters\nwas a big element in that (causing massive pollution of matches due to\nuseless data), along with privacy etc. This kind of approach will\nhave the best chances if it doesn't repeat the mistakes... but also\nit'll have the best chances if it has good security, and getting SPV-\nequivalent security will require committing the filters, but\ncommitting them is a big step because then the behaviour becomes\nconsensus normative-- it's worth spending a few months of extra\niteration getting the design as good as possible before doing that\n(which is what we've been seeing lately).",
"sig": "4cbeee8788dcc7e90e42f441456d8d4af0a9eb0bd4b2e7f536aae2736c559ca5326ea8c0f54c64be65490ad8f7ae48f4991dcef760543c81dd0bed04549e2443"
}