Recompensas de cozimento como operações

As recompensas acontecem comoparte doprotocoloe estátudoem cadeia. Maselesnão são uma "transação"no sentidonormal dapalavra,comogeralmente umatransação requer algumaintervenção do usuário. Mas hámovimentosfundamentais defundos do "freezer"para os delegados. Conceitualmente,ofreezermantémtemporariamentetodas as ligaçõese recompensaspara assare endossar.

Paraencontrarestainformação sobre corrente,temos que olharpara o últimobloco do ciclo queesperávamos a recompensa.

blockNumForRewards = (rewardedCycleNum + 6) * numOfBlocksInCycle

Porexemplo,para o ciclo 93,as recompensaspara o ciclo 93 são desbloqueadasno últimobloco de ciclo 98,porissoprecisamos olharpara onúmero dobloco (93 + 6) * 4096 = 405,504.

Após sabermos onúmero dobloco,podemos consultapara obloco Com onossonópor Obtendo o hash de umblocoexplorador comotzscan. Neste caso,BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf é onosso hashblock:

 /chains/main/blocks/BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf
 

Obviamente,hámuitasinformações aqui,mas vamosnos concentrarno caminho que lida com as alterações deequilíbrio,especificamente metadata > balance_updates. Exemplo:

 {
  "protocol": "PsddFKi32cMJ2qPjf43Qv5GDWLDPZb3T3bF6fLKiF5HtvHNU7aP",
  "chain_id": "NetXdQprcVkpaWU",
  "hash": "BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf",
  "metadata": {
    ...
    "balance_updates": [
      // this is what we care about
    ]
  }
  ...
}
 

Estaparte dobloco é as atualizações debalanço quemantêmpara o que oprotocoloprecisapara aplicar,independentemente dasintervenções do usuário. Emmuitosblocos,essaporçãoincluirá apenas opadeiro debloco atual com suas recompensase títulosbloqueados. No últimobloco do ciclo,balance_updatestambémincluitodas as recompensase obrigações destravadaspara cadapadeiro queparticiparam do ciclo 93.

De qualquerforma,vamos cavar asespecificidades de umpadeiroparaentendermais. Parailustração,eufiltrou astransaçõespara um determinadopadeiro tz1ivoFE...TD.

     "balance_updates": [
      ...
      {
        "kind": "freezer",
        "category": "deposits",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-10368000000"
      },
      {
        "kind": "freezer",
        "category": "fees",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-9362"
      },
      {
        "kind": "freezer",
        "category": "rewards",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-321000000"
      },
      {
        "kind": "contract",
        "contract": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "change": "10689009362"
      },
      ...
 

Dentro de balance_updatesmatriz,eleincluirátodas as "transações" queprecisam ser ajustadasparatodosessesendereços,incluindo o "freezer". Cadatransaçãotambém dá algumaspistas sobre o que são.

O acima ébem típico o que veremosporpadeiro. Existem 3transações relacionadas ao "freezer"e um "contrato". Atransação "freezer" é diferentepor sua categoria category (deposits,feese rewards). As categorias sãobastante auto-explicativas. Apenasno caso de você ser admirado,os depósitose recompensasincluirãotítulose recompensas de cozedurae endossos. Observe queessas operações do congelador são valoresnegativose elesimplicam queesses saldos sejam subtraídos do congelador category.

Atransação "contrato" é o quemuda o saldopara opadeiroem questão. Isso émuitoparecido com umatransaçãoiniciadapelo usuário. Se somarmos os 3 saldos da categoria dofreezer,eles somariam o saldo demudançapara opadeiro.

The rewards happen as part of the protocol and it's all on chain. But they are not a "transaction" in the normal sense of the word, as usually a transaction requires some user intervention. But there is fundamental movements of funds from the "freezer" to the delegates. Conceptually, the freezer temporarily holds all the bonds and rewards for baking and endorsing.

To find this information on chain, we have to look at the very last block of the cycle we'd expect the reward.

blockNumForRewards = (rewardedCycleNum + 6) * numOfBlocksInCycle

For example, for cycle 93, the rewards for cycle 93 gets unlocked at the last block of cycle 98, so we need to look at block number (93 + 6) * 4096 = 405,504.

After we knowing the block number, We can query for the block with our node by getting the hash from a block explorer like tzscan. In this case, BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf is our block hash:

/chains/main/blocks/BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf

Obviously there is a lot of information in here, but let's focus on the path that handles the balance changes, specifically metadata > balance_updates. Example:

{
  "protocol": "PsddFKi32cMJ2qPjf43Qv5GDWLDPZb3T3bF6fLKiF5HtvHNU7aP",
  "chain_id": "NetXdQprcVkpaWU",
  "hash": "BLdha4dMeWYxYkuP46eCgYwsgBYiKPNFLvgiu5NqgdxPLhkgzUf",
  "metadata": {
    ...
    "balance_updates": [
      // this is what we care about
    ]
  }
  ...
}

This portion of the block is the balance updates that retains to what the protocol needs to apply regardless of the user interventions. In a lot of the blocks, this portion will just include the current block baker with its locked rewards and bonds. In the last block of the cycle, balance_updates also includes all the rewards and bonds unlocks for every baker that participated in cycle 93.

Anyhow, let's dig into the specifics of one baker to understand further. For illustration, I've filtered out transactions for one particular baker tz1ivoFE...TD.

    "balance_updates": [
      ...
      {
        "kind": "freezer",
        "category": "deposits",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-10368000000"
      },
      {
        "kind": "freezer",
        "category": "fees",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-9362"
      },
      {
        "kind": "freezer",
        "category": "rewards",
        "delegate": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "level": 93,
        "change": "-321000000"
      },
      {
        "kind": "contract",
        "contract": "tz1ivoFEvbfbUNav5FwLvmxzMGcNXWxY9qTD",
        "change": "10689009362"
      },
      ...

Inside of balance_updates array, it will include every "transaction" that needs to be adjusted for all these addresses including the "freezer". Each transaction also gives some clues on what they are for.

The above is pretty typical what we'll see per baker. There are 3 "freezer" related transactions and one "contract". The "freezer" transaction are different by their category (deposits, fees and rewards). The categories are pretty self explanatory. Just in case you are wonder, deposits and rewards will include both baking and endorsements bonds and rewards. Notice that those freezer operations are negative values and they imply that these balances are subtracted from freezer.

The "contract" transaction is what changes the balance to the baker in question. This is pretty similar to a user initiated transaction. If we add up the 3 freezer category's balances, they would add up to the change balance for the baker.

A resposta "versão curta" é queisso é realizado através de consensus,que é um conceitoextremamenteimportanteem blocos que são usadospara criptoCurrency.Infelizmentemuitaspessoas simplesmentenãoentendem;Neste aspectoessencialmente otermo "consenso" resume-se a:

(Eesta é realmente uma descriçãomuito simplificada aqui,não levandoem conta recompensas ou depósitos,etc) O códigopara oprotocolo Tezos dita que quando uma conta assenta umbloco,esseequilíbrio de conta simplesmente sobepor ꜩ16.Comotodosestãoexecutando omesmoprotocolo,todos concordam que quando uma conta assenta umbloco,esse saldo da conta sobepor ꜩ16.Isso é consenso.

The "short version" answer is that this is accomplished through consensus, which is an extremely important concept in blockchains that are used for cryptocurrency. Unfortunately many people just dont really understand it; in this aspect essentially the term "consensus" boils down to:

(and this really is a very simplified description here, not taking into account freezing rewards or deposits, etc) The code for the Tezos protocol dictates that when an account bakes a block, that account's balance simply goes up by ꜩ16. Since everyone is running the same protocol, everyone agrees that when an account bakes a block, that account's balance goes up by ꜩ16. Thats consensus.