回复：关于 IRC 引导启动
原始发布页
打开来源页面查看 1 个交叉存档
比特币使用“addr”消息维护自己的分布式地址目录。是时候把当前长期运行的静态节点列表写入代码，用作种子来源了。我可以加入代码，让新节点不优先保持与种子节点的连接，只连接并获取列表，这样就不会给它们造成负担。
你们觉得怎么样，我应该直接加入这些种子吗？
它仍会先尝试 IRC。IRC 的优势是会列出当前在线的节点，因为它们必须保持连接才能留在列表中，但缺点是它是单点故障。“addr”系统没有单点故障，但只能告诉你最近见到过哪些节点，所以连接需要稍长一些，因为你尝试连接的一些节点已经离线。两者结合能让我们兼得二者之长，并获得更高的整体稳健性。
有没有人愿意自告奋勇运行一个 IRC 服务器，以防 freenode 受够了我们？
英文原文
展开英文原文
Bitcoin has its own distributed address directory using the "addr" message. It's about time we coded in a list of the current long running static nodes to seed from. I can add code so new nodes do not preferentially stay connected to the seed nodes, just connect and get the list, so it won't be a burden on them.
What do you think, should I go ahead with adding the seeds?
It'll still try IRC first. The IRC has the advantage that it lists nodes that are currently online, since they have to stay connected to stay on the list, but the disadvantage that it's a single point of failure. The "addr" system has no single point of failure, but can only tell you what nodes have recently been seen, so it takes a little longer to get connected since some of the nodes you try have gone offline. The combination of the two gets us the best of both worlds and more total robustness.
Is there anyone who wants to volunteer to run an IRC server in case freenode gets tired of us?