错过了我的认可

通过BakeTzForMe发布reddit答案:

不幸的是,这是面包师(代言人)从一开始就生活的事实 时间.通常,有许多可能的原因导致 发生这种情况,包括但不限于:

• 您节点的时钟是错误的,因此即使它认为它在正确的时间认可,也为时已晚或为时过早.

• 从地理位置上讲,您与Tezos网络的连接出现故障或连接不良,结果您没有收到 前一个区块足够快地进行验证和认可,然后 通过网络向面包师传播您的认可 已将其包含在其块中.

• 您的节点正在使用硬盘驱动器而不是SSD,并且磁盘IO已用光了该节点,因此无法快速接收,验证和认可该块 足够.这尤其可能发生在 新周期.

请注意,这些相同的问题可能在面包师的末尾.其他 话说来,您本来可以做好一切,但对于 贝克无法控制的原因没有得到您的认可 及时将其包含在他们烘焙的块中.

在这种情况下,我想问题出在面包师的 结束.

Posting the reddit answer by BakeTzForMe:

Unfortunately this is a fact of life for bakers (endorsers) from time to time. In general, there are a number of possible causes for something like this happening, including, but not limited to:

• Your node's clock is wrong so even though it thinks it endorsed at the correct time, it was too late or too early.

• Your connection to the Tezos network had a hiccup or wasn't well connected, geographically speaking, and as a result you didn't receive the previous block soon enough to verify and endorse it, and then also propagate your endorsement across the network to the baker who would have included it in their block.

• Your node is using a hard drive instead of SSD, and was maxed out with disk IO and couldn't receive, verify, and endorse the block fast enough. This is especially more likely to happen at the beginning of a new cycle.

Note that these same issues could be on the end of the baker. In other words, you could have done everything right on your end, but for reasons beyond your control the baker didn't receive your endorsement in time to include it in the block they baked.

In this specific case, I would guess that the issue is on the baker's end.

此问题最初是在r/Tezos上问到的我回答:

不幸的是,这是面包师(背书人)不时遇到的现实.通常,发生这种情况的原因可能有很多,包括但不限于:

• 您节点的时钟是错误的,因此即使它认为它是在正确的时间认可的,也为时已晚.
• 从地理上来讲,您与Tezos网络的连接出现故障或连接不畅,结果您没有足够快地收到前一个区块以进行验证和认可,然后在整个网络上传播您的认可与将其包含在其块中的面包师建立网络.
• 您的节点使用的是硬盘驱动器而不是SSD,并且磁盘IO耗尽了该节点,并且无法足够快地接收,验证和认可该块.在新的周期开始时,这种情况尤其可能发生.

请注意,这些相同的问题可能在面包师的末尾.换句话说,您本来可以做好所有事情,但由于无法控制的原因,面包师没有及时得到您的认可,无法将其包括在烘焙块中.

在此特定情况中,我认为问题出在面包师的头上.

This question was originally asked on r/Tezos where I replied with the following:

Unfortunately this is a fact of life for bakers (endorsers) from time to time. In general, there are a number of possible causes for something like this happening, including, but not limited to:

• Your node's clock is wrong so even though it thinks it endorsed at the correct time, it was too late or too early.
• Your connection to the Tezos network had a hiccup or wasn't well connected, geographically speaking, and as a result you didn't receive the previous block soon enough to verify and endorse it, and then also propagate your endorsement across the network to the baker who would have included it in their block.
• Your node is using a hard drive instead of SSD, and was maxed out with disk IO and couldn't receive, verify, and endorse the block fast enough. This is especially more likely to happen at the beginning of a new cycle.

Note that these same issues could be on the end of the baker. In other words, you could have done everything right on your end, but for reasons beyond your control the baker didn't receive your endorsement in time to include it in the block they baked.

In this specific case, I would guess that the issue is on the baker's end.

原则上,这是正常情况,贝克有时会错过1个街区.如果您连续错过几次,则表示您有问题.由于多种原因(例如短期Internet速度故障),可以跳过1个数据块

In principle, this is a normal situation when from time to time the Baker can miss 1 block . If you miss a few in a row it means that you have a problem. 1 block can be skipped due to a number of reasons, such as a short-term Internet speed failure