rich1.0npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58njumphttps://nostr.ae📅 Original date posted:2011-06-13 🗒️ Summary of this message: Using BitTorrent trackers, even HTTP-based ones, could help scale Bitcoin and make it harder for attackers to compromise clients. However, discovering HTTP trackers presents challenges. 📝 Original message:On Mon, Jun 13, 2011 at 5:38 AM, Christian Decker <decker.christian at gmail.com> wrote: > BitTorrent trackers are used to handle several thousands of requests, so > they would probably scale well enough. I'm not even talking about using the > DHT trackers, but using old fashioned HTTP based trackers. The fact that > each bitcoin client would contact the tracker would make it very hard for an > attacker to get bootstrapping clients to exclusively connect to his > compromised clients. I would say that using a tracker such as OpenBittorrent > provides the same advantages as using an IRC channel. And how does the client discover HTTP trackers? You're either hardcoding -those- into the client, or adding an additional bootstrap step to discover them. Either way, it has the same problems as other current methods. The history and experience of gnutella's web caches vs. UDP host caches seems highly relevant here. -- Jeff Garzik exMULTI, Inc. jgarzik at exmulti.com