What incentive is there for baking on the test chain during voting period?












5















It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.



As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.



I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.






baking voting







share|improve this question



























    5















    It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.



    As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.



    I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.






    baking voting







    share|improve this question

























      5












      5








      5








      It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.



      As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.



      I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.






      baking voting







      share|improve this question














      It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.



      As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.



      I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.






      baking voting




      baking voting






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 12 hours ago









      xtzbakerxtzbaker

      432216




      432216






















          1 Answer
          1






          active

          oldest

          votes


















          2














          It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.



          For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.



          It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly



          So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase






          share|improve this answer



















          • 1





            Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

            – xtzbaker
            11 hours ago






          • 1





            @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

            – Ezy
            11 hours ago











          • The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

            – xtzbaker
            6 hours ago











          • @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

            – Ezy
            6 hours ago











          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
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f652%2fwhat-incentive-is-there-for-baking-on-the-test-chain-during-voting-period%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.



          For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.



          It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly



          So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase






          share|improve this answer



















          • 1





            Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

            – xtzbaker
            11 hours ago






          • 1





            @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

            – Ezy
            11 hours ago











          • The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

            – xtzbaker
            6 hours ago











          • @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

            – Ezy
            6 hours ago
















          2














          It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.



          For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.



          It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly



          So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase






          share|improve this answer



















          • 1





            Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

            – xtzbaker
            11 hours ago






          • 1





            @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

            – Ezy
            11 hours ago











          • The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

            – xtzbaker
            6 hours ago











          • @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

            – Ezy
            6 hours ago














          2












          2








          2







          It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.



          For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.



          It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly



          So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase






          share|improve this answer













          It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.



          For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.



          It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly



          So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 12 hours ago









          EzyEzy

          2,357428




          2,357428








          • 1





            Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

            – xtzbaker
            11 hours ago






          • 1





            @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

            – Ezy
            11 hours ago











          • The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

            – xtzbaker
            6 hours ago











          • @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

            – Ezy
            6 hours ago














          • 1





            Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

            – xtzbaker
            11 hours ago






          • 1





            @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

            – Ezy
            11 hours ago











          • The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

            – xtzbaker
            6 hours ago











          • @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

            – Ezy
            6 hours ago








          1




          1





          Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

          – xtzbaker
          11 hours ago





          Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain

          – xtzbaker
          11 hours ago




          1




          1





          @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

          – Ezy
          11 hours ago





          @xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.

          – Ezy
          11 hours ago













          The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

          – xtzbaker
          6 hours ago





          The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.

          – xtzbaker
          6 hours ago













          @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

          – Ezy
          6 hours ago





          @xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.

          – Ezy
          6 hours ago


















          draft saved

          draft discarded




















































          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%2f652%2fwhat-incentive-is-there-for-baking-on-the-test-chain-during-voting-period%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

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 2 total noob sorry any help greatly appreciated. I keep getting this "Incorrect syntax near the keyword 'ON'." heres my codes code one CREATE TABLE supplier ( supplierID INT PRIMARY KEY, ISBN INT FOREIGN KEY REFERENCES book(ISBN), price DECIMAL (5,2), ON UPDATE CASCADE, ON DELETE CASCADE, ); code two CREATE TABLE orders ( orderID INT PRIMARY KEY, customerID INT FOREIGN KEY REFERENCES customer(customerID), ISBN INT FOREIGN KEY REFERENCES book(ISBN), orderDate date, ON UPDATE CASCADE, ON DELETE CASCADE, ); Ive run out of stuff to try other than dumbing it down to uselessness. ...
          Read more

          Alcedinidae

          Image
          Alcedinidae Martin-pêcheur à dos bleu ( Alcedo azurea ) Classification (COI) Règne Animalia Embranchement Chordata Sous-embr. Vertebrata Classe Aves Ordre Coraciiformes Famille Alcedinidae Rafinesque, 1815 Les Alcédinidés ou Alcedinidae forment une famille d'oiseaux plus connus sous les noms de martins-pêcheurs et martins-chasseurs. Sommaire 1 Description 2 Répartition et habitat 3 Systématique 3.1 Liste alphabétique des genres 3.2 Liste des espèces 4 Chez les Anciens : l'alcyon 4.1 Étymologie (Littré) 4.2 Oiseau « fabuleux » ? 5 Notes 6 Articles connexes 7 Liens externes 7.1 Bibliographie Description | Ce sont des oiseaux compacts de taille petite à moyenne (10 à 46 cm), au bec droit et long, en forme de poignard. Leurs pattes sont courtes, et ils portent un plumage aux couleurs vives. Répartition et habitat | Cosmopolites, ils fréquentent surtout ...
          Read more

          Origin of the phrase “under your belt”?

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 17 1 Today, I found myself discussing what students should have "under their belts" during a lecture, and I wondered to myself if there was some inappropriate undertone here that I might be unaware of. Question : What is the origin of the phrase "under your belt"? A google search revealed some webpages (e.g. [1]) that assert its origin is related to consumption of food -- once a meal has been eaten, it's under your belt (which is a relief). However, with such websites, I have no way to determine fact from "random guy on the internet making stuff up". etymology idioms ...
          Read more