Perdeu meu endosso

Postar a resposta REDDITpor Baketzforme:

.

Infelizmenteeste é umfato da vidaparapadeiros (endossadores) dotempo para otempo. Emgeral,há uma série de causaspossíveispara algo assim acontecendo,incluindo,masnão limitado a:

• O relógio do seunóestáerrado,então,emborapense queendossounotempo correto,eratarde demais ou cedo.

• Sua conexão com a rede Tezosteve um soluço ounãoestavabem conectado,geograficamentefalando,e como resultado vocênão recebeu obloco anteriorem brevepara verificare endossá-lo,e entãotambém propagar seuendosso através da redepara opadeiro quefaria incluí-loem seubloco.

• Seunóestá usando um disco rígidoem vez de SSD,e foimaximizado com o disco IOe nãopôde receber,verificare endossar obloco rápido o suficiente. Isso éespecialmentemaispropenso a acontecernoinício de um novo ciclo.

Observe queessesmesmosproblemaspodemestarnofinal dopadeiro. Em outro palavras,vocêpoderiaterfeitotudobem no seufim,maspara razões além do seu controle,opadeironão recebeu seuendosso atempo deincluí-lonobloco queeles assados.

Neste casoespecífico,eu acho que a questãoestánopadeiro fim.

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.

Esta questãofoi originalmenteperguntada sobre R/Tezos,onde Eu respondi Com o seguinte:

• O relógio do seunóestáerrado,então,emborapenseendossadona hora correta,eratarde demais ou cedo demais.
• sua conexão com a rede Tezostinha um soluço ounãoestavabem conectado,geograficamentefalando,e como resultado vocênão recebeu obloco anteriorem brevepara verificare endossá-loe,em seguida,tambémpropagar seuendosso através do redepara opadeiro que oteriaincluídoem seubloco.
• Seunóestá usando um disco rígidoem vez de SSD,e foimaximizado com o disco IOe nãopôde receber,verificare endossar obloco rápido o suficiente. Isto éespecialmentemaispropenso a acontecernoinício de umnovo ciclo.

Observe queessesmesmosproblemaspodemestarnofinal dopadeiro. Em outraspalavras,vocêpoderiaterfeitotudobem no seufim,maspor razões além do seu controle,opadeironão recebeu seuendosso atempo deincluí-lonobloco queeles assados.

em Este casoespecífico ,eu acho que oproblemaestánofinal dopadeiro.

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.

Emprincípio,esta é uma situaçãonormal quando de vezem quando opadeiropodeperder 1bloco.Se vocêperder alguns seguidos,isso significa que vocêtem umproblema.1blocopode serignorado devido a várias razões,como umafalha de velocidade deinternet de curtoprazo

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