Baking rewards as operations Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Baking eligibility and start timeHow to calculate projected vs actual rewards for delegators using Tzscan API?What does it cost to make a contract through Tezos?When is baking rewards counted to the staking balance?How do rewards for revelations work?When are Tezos Rewards Unfrozen?How to manage rewards for small delegators?Only 60% of the rewards made by a baker are distributed to its delegators?Are bakers not paying promised rewards?smart contract for automatic baking/endorsement rewards to delegators

What are some likely causes to domain member PC losing contact to domain controller?

Vertical ranges of Column Plots in 12

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

How to make an animal which can only breed for a certain number of generations?

"Destructive power" carried by a B-52?

Why can't fire hurt Daenerys but it did to Jon Snow in season 1?

Was the pager message from Nick Fury to Captain Marvel unnecessary?

Why not use the yoke to control yaw, as well as pitch and roll?

Keep at all times, the minus sign above aligned with minus sign below

What is "Lambda" in Heston's original paper on stochastic volatility models?

3D Masyu - A Die

Where did Ptolemy compare the Earth to the distance of fixed stars?

Determine whether an integer is a palindrome

Why complex landing gears are used instead of simple, reliable and light weight muscle wire or shape memory alloys?

Inverse square law not accurate for non-point masses?

Pointing to problems without suggesting solutions

Did John Wesley plagiarize Matthew Henry...?

How do I say "this must not happen"?

How many time has Arya actually used Needle?

Fit odd number of triplets in a measure?

Does the main washing effect of soap come from foam?

Twin's vs. Twins'

How does TikZ render an arc?

Any stored/leased 737s that could substitute for grounded MAXs?



Baking rewards as operations



Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Baking eligibility and start timeHow to calculate projected vs actual rewards for delegators using Tzscan API?What does it cost to make a contract through Tezos?When is baking rewards counted to the staking balance?How do rewards for revelations work?When are Tezos Rewards Unfrozen?How to manage rewards for small delegators?Only 60% of the rewards made by a baker are distributed to its delegators?Are bakers not paying promised rewards?smart contract for automatic baking/endorsement rewards to delegators










1















How do making rewards appear on the chain when they are credited to the baker? Is it a 'transaction' operation? How do I go about identifying them?



Thanks!










share|improve this question







New contributor




Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
























    1















    How do making rewards appear on the chain when they are credited to the baker? Is it a 'transaction' operation? How do I go about identifying them?



    Thanks!










    share|improve this question







    New contributor




    Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      1












      1








      1








      How do making rewards appear on the chain when they are credited to the baker? Is it a 'transaction' operation? How do I go about identifying them?



      Thanks!










      share|improve this question







      New contributor




      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      How do making rewards appear on the chain when they are credited to the baker? Is it a 'transaction' operation? How do I go about identifying them?



      Thanks!







      baking rewards






      share|improve this question







      New contributor




      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 3 hours ago









      Crypto MikeCrypto Mike

      61




      61




      New contributor




      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Crypto Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          2 Answers
          2






          active

          oldest

          votes


















          1














          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.






          share|improve this answer
































            0














            Currently rewards are done manually and off-chain. You manually (or via a script) need to transfer the rewards to delegators.



            When you transfer the rewards it will create transactions with operation ids which will be on-chain.



            You could write a tool to connect the dots and create your own reporting, or use some of the existing tools (eg: bakerei, tezos-reward-distributor, etc...)






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "698"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              noCode: true, onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );






              Crypto Mike is a new contributor. Be nice, and check out our Code of Conduct.









              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f1125%2fbaking-rewards-as-operations%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              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.






              share|improve this answer





























                1














                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.






                share|improve this answer



























                  1












                  1








                  1







                  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.






                  share|improve this answer















                  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.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 32 mins ago

























                  answered 2 hours ago









                  FrankFrank

                  1,297418




                  1,297418





















                      0














                      Currently rewards are done manually and off-chain. You manually (or via a script) need to transfer the rewards to delegators.



                      When you transfer the rewards it will create transactions with operation ids which will be on-chain.



                      You could write a tool to connect the dots and create your own reporting, or use some of the existing tools (eg: bakerei, tezos-reward-distributor, etc...)






                      share|improve this answer



























                        0














                        Currently rewards are done manually and off-chain. You manually (or via a script) need to transfer the rewards to delegators.



                        When you transfer the rewards it will create transactions with operation ids which will be on-chain.



                        You could write a tool to connect the dots and create your own reporting, or use some of the existing tools (eg: bakerei, tezos-reward-distributor, etc...)






                        share|improve this answer

























                          0












                          0








                          0







                          Currently rewards are done manually and off-chain. You manually (or via a script) need to transfer the rewards to delegators.



                          When you transfer the rewards it will create transactions with operation ids which will be on-chain.



                          You could write a tool to connect the dots and create your own reporting, or use some of the existing tools (eg: bakerei, tezos-reward-distributor, etc...)






                          share|improve this answer













                          Currently rewards are done manually and off-chain. You manually (or via a script) need to transfer the rewards to delegators.



                          When you transfer the rewards it will create transactions with operation ids which will be on-chain.



                          You could write a tool to connect the dots and create your own reporting, or use some of the existing tools (eg: bakerei, tezos-reward-distributor, etc...)







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 3 hours ago









                          lostdorjelostdorje

                          4659




                          4659




















                              Crypto Mike is a new contributor. Be nice, and check out our Code of Conduct.









                              draft saved

                              draft discarded


















                              Crypto Mike is a new contributor. Be nice, and check out our Code of Conduct.












                              Crypto Mike is a new contributor. Be nice, and check out our Code of Conduct.











                              Crypto Mike is a new contributor. Be nice, and check out our Code of Conduct.














                              Thanks for contributing an answer to Tezos Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f1125%2fbaking-rewards-as-operations%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Disable / Remove link to Product Items in Cart Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How can I limit products that can be bought / added to cart?Remove item from cartHide “Add to Cart” button if specific products are already in cart“Prettifying” the custom options in cart pageCreate link in cart sidebar to view all added items After limit reachedLink products together in checkout/cartHow to Get product from cart and add it againHide action-edit on cart page if simple productRemoving Cart items - ObserverRemove wishlist items when added to cart

                              Helsingin valtaus Sisällysluettelo Taustaa | Yleistä sotatoimista | Osapuolet | Taistelut Helsingin ympäristössä | Punaisten antautumissuunnitelma | Taistelujen kulku Helsingissä | Valtauksen jälkeen | Tappiot | Muistaminen | Kirjallisuutta | Lähteet | Aiheesta muualla | NavigointivalikkoTeoksen verkkoversioTeoksen verkkoversioGoogle BooksSisällissota Helsingissä päättyi tasan 95 vuotta sittenSaksalaisten ylivoima jyräsi punaisen HelsinginSuomalaiset kuvaavat sotien jälkiä kaupungeissa – katso kuvat ja tarinat tutuilta kulmiltaHelsingin valtaus 90 vuotta sittenSaksalaiset valtasivat HelsinginHyökkäys HelsinkiinHelsingin valtaus 12.–13.4. 1918Saksalaiset käyttivät ihmiskilpiä Helsingin valtauksessa 1918Teoksen verkkoversioTeoksen verkkoversioSaksalaiset hyökkäävät Etelä-SuomeenTaistelut LeppävaarassaSotilaat ja taistelutLeppävaara 1918 huhtikuussa. KapinatarinaHelsingin taistelut 1918Saksalaisten voitonparaati HelsingissäHelsingin valtausta juhlittiinSaksalaisten Helsinki vuonna 1918Helsingin taistelussa kaatuneet valkokaartilaisetHelsinkiin haudatut taisteluissa kaatuneet punaiset12.4.1918 Helsingin valtauksessa saksalaiset apujoukot vapauttavat kaupunginVapaussodan muistomerkkejä Helsingissä ja pääkaupunkiseudullaCrescendo / Vuoden 1918 Kansalaissodan uhrien muistomerkkim

                              Adjektiivitarina Tarinan tekeminen | Esimerkki: ennen | Esimerkki: jälkeen | Navigointivalikko