回复：工作量证明难度上升
原始发布页
打开来源页面查看 1 个交叉存档
引用自：Sabunir，2010 年 2 月 16 日 08:51:51 AM
. 也许这与我的连接延迟非常高有关（平均 2000ms 或更高）
双向 2 秒的延迟会使你成功生成的概率降低不到 1%。
引用自：Sabunir，2010 年 2 月 16 日 08:51:51 AM
以及／或者我的丢包率很高（有时高达 10%）？
应该没问题，但我不确定。协议的设计是从下一条消息重新同步，而且在收到消息之前，会不断向你连接的所有其他节点重新请求。如果你漏掉了一个区块，那么每当另一个区块传来、发现中间有缺口时，它也会继续请求那个区块。在最初发布之前，我做过一项测试：在高负载下随机丢弃四分之一的消息，直到可以让它运行一整夜而没有任何节点卡住。
英文原文
展开英文原文
Quote from: Sabunir on February 16, 2010, 08:51:51 AM
. Perhaps it has to do with my connection's very high latency (2000ms or more on average)
2 seconds of latency in both directions should reduce your generation success by less than 1%.
Quote from: Sabunir on February 16, 2010, 08:51:51 AM
and/or my high packet loss (sometimes up to 10% loss)?
Probably OK, but I'm not sure. The protocol is designed to resync to the next message, and messages get re-requested from all the other nodes you're connected to until received. If you miss a block, it'll also keep requesting it every time another blocks comes in and it sees there's a gap. Before the original release I did a test dropping 1 out of 4 random messages under heavy load until I could run it overnight without any nodes getting stuck.