{"type":"rich","version":"1.0","author_name":"npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn","author_url":"https://nostr.ae/npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-06-13\n🗒️ Summary of this message: The Bitcoin community is discussing the adoption of BitTorrent tracker bootstrapping as a simpler alternative to the current IRC bootstrapping mechanism.\n📝 Original message:Hi all.\n\nJust wanted to carry the discussion from the Forum over to the dev-list.\n\nWe have quite a few bootstrapping mechanisms, starting with the overly\ncomplex (IMHO) IRC bootstrapping, which is often suspected as bot-activity.\nThen we have a few hardcoded nodes and some fallback nodes. I was wondering\nwhy we didn't adopt BitTorrent tracker bootstrapping until now? It's\nbasically all it does. Given a hash (SHA1 hash of the genesis bloc would be\nnice ^^) it gives you a list of other nodes with the same hash.\n\nGiven that there are quite a few open trackers (accepting and tracking any\nhash you throw at them) we could just decide to use 2-3 of those to\nbootstrap.\n\nThe downside would be that they return bencoded data, which has to be\ninterpreted first, but it's easier than implementing the IRC stuff, I think.\n\nAny comments?\n\nRegards,\nChris\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110613/099e3077/attachment.html\u003e"}
