{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-06-13\n🗒️ Summary of this message: A proposal to adopt BitTorrent tracker bootstrapping for Bitcoin nodes was discussed, but concerns were raised about potential vulnerabilities and Sybil attacks on DHTs.\n📝 Original message:On Mon, Jun 13, 2011 at 4:55 AM, Christian Decker\n\u003cdecker.christian at gmail.com\u003e wrote:\n\u003e We have quite a few bootstrapping mechanisms, starting with the overly\n\u003e complex (IMHO) IRC bootstrapping, which is often suspected as bot-activity.\n\u003e Then we have a few hardcoded nodes and some fallback nodes. I was wondering\n\u003e why we didn't adopt BitTorrent tracker bootstrapping until now? It's\n\u003e basically all it does. Given a hash (SHA1 hash of the genesis bloc would be\n\u003e nice ^^) it gives you a list of other nodes with the same hash.\n\nIt seems to offer few benefits over DNS seeding, while potentially\npotentially creating a vulnerable hot spot in the DHT.  Sybil attacks\non DHTs are well documented.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com"}