📅 Original date posted:2019-07-22
📝 Original message:On Sunday 21 July 2019 22:56:33 Andreas Schildbach via bitcoin-dev wrote:
> An estimated 10+ million wallets depend on that NODE_BLOOM to be
> updated.
Where do you see this number? I think it would be useful to chart.
> So far, I haven't heard of an alternative, except reading all
> transactions and full blocks.
Electrum has a JSON-based protocol that can provide information much more
efficiently.
Currently, this does require nodes that run additional software and/or
indexes, but there are plenty of them available, and there are steps that can
be taken to improve that situation.
> > It is not anticipated that
> > this will result in a significant lack of availability of
> > NODE_BLOOM-enabled nodes in the coming years
>
> Why don't you anticipate that? People almost never change defaults,
> especially if it's not for their own immediate benefit. At the same
> time, release notes in general recommend updating to the latest version.
> I *do* anticipate this will reduce the number of nodes usable by a large
> enough amount so that the feature will become unstable.
Many users run older versions, and do not update immediately. Today, only 42%
of listening nodes are using 0.18.
(If it helps ease the concern, we can keep bloom enabled by default in Knots
longer.)
> I strongly recommend postponing this change until an alternative exists
> and then give developers enough time to implement, test and roll out.
There will be time to do so, since the functionality won't disappear
overnight.
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 18:19:36
in reply to nevent1q…58hp
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 18:19:36Event JSON
{
"id": "251dfe5167e7e51486a496ab913f68161bcb4f1f536504723e474f236f45442d",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686161976,
"kind": 1,
"tags": [
[
"e",
"9984a06ec701a8f6ac2773e4a62741a4d9d15af90b1fce9ee03180b7fd819eec",
"",
"root"
],
[
"e",
"50ada94a206594a9b7c9f16bf4d98e66f7355a24f12ac15a20766341fafe07d9",
"",
"reply"
],
[
"p",
"5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803"
]
],
"content": "📅 Original date posted:2019-07-22\n📝 Original message:On Sunday 21 July 2019 22:56:33 Andreas Schildbach via bitcoin-dev wrote:\n\u003e An estimated 10+ million wallets depend on that NODE_BLOOM to be\n\u003e updated.\n\nWhere do you see this number? I think it would be useful to chart.\n\n\u003e So far, I haven't heard of an alternative, except reading all \n\u003e transactions and full blocks.\n\nElectrum has a JSON-based protocol that can provide information much more \nefficiently.\n\nCurrently, this does require nodes that run additional software and/or \nindexes, but there are plenty of them available, and there are steps that can \nbe taken to improve that situation.\n\n\u003e \u003e It is not anticipated that\n\u003e \u003e this will result in a significant lack of availability of\n\u003e \u003e NODE_BLOOM-enabled nodes in the coming years\n\u003e\n\u003e Why don't you anticipate that? People almost never change defaults,\n\u003e especially if it's not for their own immediate benefit. At the same\n\u003e time, release notes in general recommend updating to the latest version.\n\u003e I *do* anticipate this will reduce the number of nodes usable by a large\n\u003e enough amount so that the feature will become unstable.\n\nMany users run older versions, and do not update immediately. Today, only 42% \nof listening nodes are using 0.18.\n\n(If it helps ease the concern, we can keep bloom enabled by default in Knots \nlonger.)\n\n\u003e I strongly recommend postponing this change until an alternative exists\n\u003e and then give developers enough time to implement, test and roll out.\n\nThere will be time to do so, since the functionality won't disappear \novernight.\n\nLuke",
"sig": "7523558215ccccd244fac2bb50694d43ad08449e9f1363dbe3cb1a10af12045c308496da9e90a588261832d546ef104aac7cea6571784ef35fe66ff72ab63865"
}