📅 Original date posted:2019-07-20
📝 Original message:Just a quick heads-up for those watching the list who may be using it -
in the next Bitcoin Core release bloom filter serving will be turned off
by default. This has been a long time coming, it's been an option for
many releases and has been a well-known DoS vector for some time.
As other DoS vectors have slowly been closed, this has become
increasingly an obvious low-hanging fruit. Those who are using it should
already have long been filtering for NODE_BLOOM-signaling nodes, and I
don't anticipate those being gone any time particularly soon.
See-also PR at https://github.com/bitcoin/bitcoin/pull/16152
The release notes will liekly read:
P2P Changes
-----------
- The default value for the -peerbloomfilters configuration option (and,
thus, NODE_BLOOM support) has been changed to false.
This resolves well-known DoS vectors in Bitcoin Core, especially for
nodes with spinning disks. It is not anticipated that
this will result in a significant lack of availability of
NODE_BLOOM-enabled nodes in the coming years, however, clients
which rely on the availability of NODE_BLOOM-supporting nodes on the
P2P network should consider the process of migrating
to a more modern (and less trustful and privacy-violating) alternative
over the coming years.
Matt
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 18:19:34
in reply to nevent1q…ncgk
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 18:19:34Event JSON
{
"id": "96f450b919bae8403e10de17fb4df7f97875bb2a44ba7a5d85e96fcbac18dcc4",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686161974,
"kind": 1,
"tags": [
[
"e",
"9984a06ec701a8f6ac2773e4a62741a4d9d15af90b1fce9ee03180b7fd819eec",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2019-07-20\n📝 Original message:Just a quick heads-up for those watching the list who may be using it -\nin the next Bitcoin Core release bloom filter serving will be turned off\nby default. This has been a long time coming, it's been an option for\nmany releases and has been a well-known DoS vector for some time.\nAs other DoS vectors have slowly been closed, this has become\nincreasingly an obvious low-hanging fruit. Those who are using it should\nalready have long been filtering for NODE_BLOOM-signaling nodes, and I\ndon't anticipate those being gone any time particularly soon.\n\nSee-also PR at https://github.com/bitcoin/bitcoin/pull/16152\n\nThe release notes will liekly read:\n\nP2P Changes\n-----------\n- The default value for the -peerbloomfilters configuration option (and,\nthus, NODE_BLOOM support) has been changed to false.\n This resolves well-known DoS vectors in Bitcoin Core, especially for\nnodes with spinning disks. It is not anticipated that\n this will result in a significant lack of availability of\nNODE_BLOOM-enabled nodes in the coming years, however, clients\n which rely on the availability of NODE_BLOOM-supporting nodes on the\nP2P network should consider the process of migrating\n to a more modern (and less trustful and privacy-violating) alternative\nover the coming years.\n\nMatt",
"sig": "80af28a9f6253053965049588ca7af0f5a39357efb06413e9d99489e2f5246e29acb1f772cb1aab27224686616e6043eee1bc35439f86e47f4033d78722e64c2"
}