Por que a rede ignorou meu bloco assado?

Aquiestá comofunciona: Apenasparamanter as coisas simples,digamos que a cadeia (todos osblocosincluídos até agora)tem uma aptidão de 100. Em outraspalavras,100endossostotaisforamincluídosem todos osblocosno corrente. Seu Baker agoratem direitos deprioridade 0para assar opróximobloco (bloco # 5),e vocêtem 30endossosem seumempoolpara obloco anterior (bloco # 4).

Você vaiem frentee asse umblocona altura 5,quetem uma aptidãototal de 130 (ototal de aptidão anterior +todos osnovosendossos que você conseguiuincluir).

Aprioridade 1 Bakertem 32endossospara obloco anteriorem seumempool,talvezporqueelestêmmelhor conectividade depares,outalvez aprendido demais 2endossos do que você.

Aprioridade 1 Baker vê seubloco chegae percebe quetem 130fitness. Em T + 15 segundos (otempo que você assou suaprioridade 0bloco + 15 segundos),o Priority 1 Bakerpercebe quepode construir umbloco quetenha 132 aptidão,incluindo os 2endossos que vocênãofez,entãoeles vêmem frentee injetar obloco.

O resto da rede vê que obloco deprioridade 1tem aptidão de 132,e seubloco deprioridade sótem fitness 130,para que a redemuda a ramificaçãoparafazer aprioridade 1bloquear anova cabeça da cadeia.

Então,para resumir,há algunsequívocos comuns aqui:

• se ospadeirosendossam seubloco determina seele é aceito ounão. Endossosnunca chegam até que seubloco seja assado,e só aumente a aptidão da cadeia que você adicionou seubloco,não oblocoem si.
• Umaprioridade 1 Bakertem queesperarmais 30 segundos antes depoder assar umbloco que setorna onovo chefe da cadeia. Eles realmenteprecisamesperar 15 segundos antes quepossaminjetar umbloco quetenha uma aptidãomais alta do que a sua.

Here is how it works: Just to keep things simple, let's say that the chain (all the blocks included up to now) has a fitness of 100. In other words, 100 total endorsements were included on all the blocks in the chain. Your baker now has priority 0 rights to bake the next block (block #5), and you have 30 endorsements in your mempool for the previous block (block #4).

You go ahead and bake a block at height 5 which has a total fitness of 130 (the total of previous fitness + all new endorsements you were able to include).

The priority 1 baker has 32 endorsements for the previous block in their mempool, maybe because they have better peer connectivity, or perhaps learned of 2 more endorsements than you did.

The priority 1 baker sees your block arrive and notices it has 130 fitness. At T+15 seconds (the time you baked your priority 0 block + 15 seconds), the priority 1 baker realizes that it can construct a block that has 132 fitness by including the 2 endorsements that you didn't, so they go ahead and inject the block.

The rest of the network sees that the priority 1 block has fitness of 132, and your priority 0 block only has fitness 130, so the network changes branch to make the priority 1 block the new head of the chain.

So, to summarize, there are a couple common misconceptions here:

• Whether bakers endorse your block determines whether it gets accepted or not. Endorsements never arrive until after your block is baked, and only increase the fitness of the chain you added your block to, not the block itself.
• A priority 1 baker has to wait an additional 30 seconds before they can bake a block that becomes the new head of the chain. They really only need to wait 15 seconds before they can inject a block that has a higher fitness than yours.

a casca atualmente ignora umanova cabeça Seestivermenos apto do que a hipotéticapróxima cabeça - assada comtodos osendossosnomempool.Estapróxima aptidão hipotética é chamada context_fitnessno código lá.

The shell currently ignores a new head if it is less fit than the hypothetical next head -- baked with all the endorsements in the mempool. This hypothetical next fitness is called context_fitness in the code there.

This means that if your baked block includes fewer endorsements than endorsers see in their mempool, they will ignore your block and wait for the priority 1 block.

Provavelmentepobre conexão a colegas,oupelomenos as queimportavamnopontonotempo (osendosseirospara o seubloco,e padeiro dopróximo).

Endossadoresendossarão obloco com a aptidãomais alta,maselesnãopodemendossar.Isso significa que,seeles vissem seublocoe endossassem,elesnãopodemmudar deidéia quando obloco P1 veio (mesmo quetivesse umnível de aptidãomaior).

No seu caso,osendossadoresnunca receberam seubloco rápido o suficientepermitindo opotencial deendossar obloco P1.Que obloco P1tinha uma aptidãomaior,então osendossadoresendossavamessebloco.

Por queendossadoresiriam com umbloco deprioridademais alto?Porquetem uma chancemaior de ser obloco canônico,e endossadores só sãopagos se oblocoendossadoforbem sucedido.

Most likely poor connection to peers, or at least the ones that mattered at the point in time (the endorsers for your block, and baker of the next).

Endorsers will endorse the block with the higher fitness, but they can't double endorse. That means if they saw your block and endorsed it, they can't change their mind when the p1 block came along (even if it had a higher fitness level).

In your case, the endorsers never received your block fast enough allowing the potential of endorsing the p1 block. That p1 block had a higher fitness, so the endorsers endorsed that block.

Why would endorsers go with a higher priority block? Because it has a higher chance of being the canonical block, and endorsers only get paid if the block the endorse succeeds.