<oembed><type>rich</type><version>1.0</version><author_name>npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn</author_name><author_url>https://nostr.ae/npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-06-13&#xA;🗒️ 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.&#xA;📝 Original message:Hi all.&#xA;&#xA;Just wanted to carry the discussion from the Forum over to the dev-list.&#xA;&#xA;We have quite a few bootstrapping mechanisms, starting with the overly&#xA;complex (IMHO) IRC bootstrapping, which is often suspected as bot-activity.&#xA;Then we have a few hardcoded nodes and some fallback nodes. I was wondering&#xA;why we didn&#39;t adopt BitTorrent tracker bootstrapping until now? It&#39;s&#xA;basically all it does. Given a hash (SHA1 hash of the genesis bloc would be&#xA;nice ^^) it gives you a list of other nodes with the same hash.&#xA;&#xA;Given that there are quite a few open trackers (accepting and tracking any&#xA;hash you throw at them) we could just decide to use 2-3 of those to&#xA;bootstrap.&#xA;&#xA;The downside would be that they return bencoded data, which has to be&#xA;interpreted first, but it&#39;s easier than implementing the IRC stuff, I think.&#xA;&#xA;Any comments?&#xA;&#xA;Regards,&#xA;Chris&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110613/099e3077/attachment.html&gt;</html></oembed>