Why transactions/contracts aren't priced/tracked based on computer running time












1















Amazon AWS and Google Cloud all base their pricing off of, among a few other things, the amount of compute and storage used. For compute, it's based on time, how much time the computer runs. This is very general and abstracts away the need to, for example, count how many times each Assembly instruction is invoked and with which operands. This would significantly interrupt performance if they did it that way, but it seems that the blockchain technologies all went the path of monitoring the individual actions/operations either through transactions directly or Smart Contracts in the case of Ethereum.



So basically I'm wondering why this is, why it wasn't decided to just base everything off compute time and storage (and bandwidth I guess, but mainly focusing on compute time here). This way a transaction would just have to have a start and end timestamp and wouldn't have to really serialize anything, which would mean you could monitor everything in detail pretty much. Wondering why it was done differently.










share|improve this question



























    1















    Amazon AWS and Google Cloud all base their pricing off of, among a few other things, the amount of compute and storage used. For compute, it's based on time, how much time the computer runs. This is very general and abstracts away the need to, for example, count how many times each Assembly instruction is invoked and with which operands. This would significantly interrupt performance if they did it that way, but it seems that the blockchain technologies all went the path of monitoring the individual actions/operations either through transactions directly or Smart Contracts in the case of Ethereum.



    So basically I'm wondering why this is, why it wasn't decided to just base everything off compute time and storage (and bandwidth I guess, but mainly focusing on compute time here). This way a transaction would just have to have a start and end timestamp and wouldn't have to really serialize anything, which would mean you could monitor everything in detail pretty much. Wondering why it was done differently.










    share|improve this question

























      1












      1








      1








      Amazon AWS and Google Cloud all base their pricing off of, among a few other things, the amount of compute and storage used. For compute, it's based on time, how much time the computer runs. This is very general and abstracts away the need to, for example, count how many times each Assembly instruction is invoked and with which operands. This would significantly interrupt performance if they did it that way, but it seems that the blockchain technologies all went the path of monitoring the individual actions/operations either through transactions directly or Smart Contracts in the case of Ethereum.



      So basically I'm wondering why this is, why it wasn't decided to just base everything off compute time and storage (and bandwidth I guess, but mainly focusing on compute time here). This way a transaction would just have to have a start and end timestamp and wouldn't have to really serialize anything, which would mean you could monitor everything in detail pretty much. Wondering why it was done differently.










      share|improve this question














      Amazon AWS and Google Cloud all base their pricing off of, among a few other things, the amount of compute and storage used. For compute, it's based on time, how much time the computer runs. This is very general and abstracts away the need to, for example, count how many times each Assembly instruction is invoked and with which operands. This would significantly interrupt performance if they did it that way, but it seems that the blockchain technologies all went the path of monitoring the individual actions/operations either through transactions directly or Smart Contracts in the case of Ethereum.



      So basically I'm wondering why this is, why it wasn't decided to just base everything off compute time and storage (and bandwidth I guess, but mainly focusing on compute time here). This way a transaction would just have to have a start and end timestamp and wouldn't have to really serialize anything, which would mean you could monitor everything in detail pretty much. Wondering why it was done differently.







      transactions contract-design database






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 7 hours ago









      Lance PollardLance Pollard

      1235




      1235






















          1 Answer
          1






          active

          oldest

          votes


















          2














          Ethereum basically does base its pricing on computing time and storage costs. Plus bandwidth (transaction cost). All instructions have an associated gas cost. So, as I see it, Ethereum is more precise in its calculations but it's basically based on very similar principles.



          As to the why Ethereum does it this way... I can think of at least a few reasons:



          1) If it was simply based on computing time different nodes would have different gas costs. A faster node would compute everything faster. So could a faster node include more transaction in a block? This would all lead to centralization - a faster node would gain more gas rewards and therefore it'd be more beneficial to have a fast node. Slower nodes would slowly die out.



          2) Who would measure the compute time and how? The network itself has no idea how long it takes for a node to compute something. It would obviously not be a good idea to simply let the node tell how long the processing took (and get paid accordingly). It would be easy for nodes to cheat in various ways.



          3) There are still the other costs, such as storage and bandwidth (transactions). They are priced based on known static instructor costs. It would probably get difficult to combine different calculation methods.



          All in all, different pricing models might easily lead to centralization in different ways. One of the main ideas of Ethereum is to allow different nodes to participate in a fair way. The more the system favors certain types of nodes, the less secure it would get.






          share|improve this answer
























          • Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

            – Lance Pollard
            6 hours ago













          • Good point on (1), same with (2).

            – Lance Pollard
            5 hours ago













          • Sorry, I'm not familiar with the code so can't point you forward with that.

            – Lauri Peltonen
            5 hours ago











          • Here we go.

            – Lance Pollard
            5 hours ago











          • This say's it's not based on compute time but is instead based on individual instructions' evaluation.

            – Lance Pollard
            5 hours ago













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "642"
          };
          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
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fethereum.stackexchange.com%2fquestions%2f67199%2fwhy-transactions-contracts-arent-priced-tracked-based-on-computer-running-time%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














          Ethereum basically does base its pricing on computing time and storage costs. Plus bandwidth (transaction cost). All instructions have an associated gas cost. So, as I see it, Ethereum is more precise in its calculations but it's basically based on very similar principles.



          As to the why Ethereum does it this way... I can think of at least a few reasons:



          1) If it was simply based on computing time different nodes would have different gas costs. A faster node would compute everything faster. So could a faster node include more transaction in a block? This would all lead to centralization - a faster node would gain more gas rewards and therefore it'd be more beneficial to have a fast node. Slower nodes would slowly die out.



          2) Who would measure the compute time and how? The network itself has no idea how long it takes for a node to compute something. It would obviously not be a good idea to simply let the node tell how long the processing took (and get paid accordingly). It would be easy for nodes to cheat in various ways.



          3) There are still the other costs, such as storage and bandwidth (transactions). They are priced based on known static instructor costs. It would probably get difficult to combine different calculation methods.



          All in all, different pricing models might easily lead to centralization in different ways. One of the main ideas of Ethereum is to allow different nodes to participate in a fair way. The more the system favors certain types of nodes, the less secure it would get.






          share|improve this answer
























          • Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

            – Lance Pollard
            6 hours ago













          • Good point on (1), same with (2).

            – Lance Pollard
            5 hours ago













          • Sorry, I'm not familiar with the code so can't point you forward with that.

            – Lauri Peltonen
            5 hours ago











          • Here we go.

            – Lance Pollard
            5 hours ago











          • This say's it's not based on compute time but is instead based on individual instructions' evaluation.

            – Lance Pollard
            5 hours ago


















          2














          Ethereum basically does base its pricing on computing time and storage costs. Plus bandwidth (transaction cost). All instructions have an associated gas cost. So, as I see it, Ethereum is more precise in its calculations but it's basically based on very similar principles.



          As to the why Ethereum does it this way... I can think of at least a few reasons:



          1) If it was simply based on computing time different nodes would have different gas costs. A faster node would compute everything faster. So could a faster node include more transaction in a block? This would all lead to centralization - a faster node would gain more gas rewards and therefore it'd be more beneficial to have a fast node. Slower nodes would slowly die out.



          2) Who would measure the compute time and how? The network itself has no idea how long it takes for a node to compute something. It would obviously not be a good idea to simply let the node tell how long the processing took (and get paid accordingly). It would be easy for nodes to cheat in various ways.



          3) There are still the other costs, such as storage and bandwidth (transactions). They are priced based on known static instructor costs. It would probably get difficult to combine different calculation methods.



          All in all, different pricing models might easily lead to centralization in different ways. One of the main ideas of Ethereum is to allow different nodes to participate in a fair way. The more the system favors certain types of nodes, the less secure it would get.






          share|improve this answer
























          • Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

            – Lance Pollard
            6 hours ago













          • Good point on (1), same with (2).

            – Lance Pollard
            5 hours ago













          • Sorry, I'm not familiar with the code so can't point you forward with that.

            – Lauri Peltonen
            5 hours ago











          • Here we go.

            – Lance Pollard
            5 hours ago











          • This say's it's not based on compute time but is instead based on individual instructions' evaluation.

            – Lance Pollard
            5 hours ago
















          2












          2








          2







          Ethereum basically does base its pricing on computing time and storage costs. Plus bandwidth (transaction cost). All instructions have an associated gas cost. So, as I see it, Ethereum is more precise in its calculations but it's basically based on very similar principles.



          As to the why Ethereum does it this way... I can think of at least a few reasons:



          1) If it was simply based on computing time different nodes would have different gas costs. A faster node would compute everything faster. So could a faster node include more transaction in a block? This would all lead to centralization - a faster node would gain more gas rewards and therefore it'd be more beneficial to have a fast node. Slower nodes would slowly die out.



          2) Who would measure the compute time and how? The network itself has no idea how long it takes for a node to compute something. It would obviously not be a good idea to simply let the node tell how long the processing took (and get paid accordingly). It would be easy for nodes to cheat in various ways.



          3) There are still the other costs, such as storage and bandwidth (transactions). They are priced based on known static instructor costs. It would probably get difficult to combine different calculation methods.



          All in all, different pricing models might easily lead to centralization in different ways. One of the main ideas of Ethereum is to allow different nodes to participate in a fair way. The more the system favors certain types of nodes, the less secure it would get.






          share|improve this answer













          Ethereum basically does base its pricing on computing time and storage costs. Plus bandwidth (transaction cost). All instructions have an associated gas cost. So, as I see it, Ethereum is more precise in its calculations but it's basically based on very similar principles.



          As to the why Ethereum does it this way... I can think of at least a few reasons:



          1) If it was simply based on computing time different nodes would have different gas costs. A faster node would compute everything faster. So could a faster node include more transaction in a block? This would all lead to centralization - a faster node would gain more gas rewards and therefore it'd be more beneficial to have a fast node. Slower nodes would slowly die out.



          2) Who would measure the compute time and how? The network itself has no idea how long it takes for a node to compute something. It would obviously not be a good idea to simply let the node tell how long the processing took (and get paid accordingly). It would be easy for nodes to cheat in various ways.



          3) There are still the other costs, such as storage and bandwidth (transactions). They are priced based on known static instructor costs. It would probably get difficult to combine different calculation methods.



          All in all, different pricing models might easily lead to centralization in different ways. One of the main ideas of Ethereum is to allow different nodes to participate in a fair way. The more the system favors certain types of nodes, the less secure it would get.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 6 hours ago









          Lauri PeltonenLauri Peltonen

          5,4742524




          5,4742524













          • Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

            – Lance Pollard
            6 hours ago













          • Good point on (1), same with (2).

            – Lance Pollard
            5 hours ago













          • Sorry, I'm not familiar with the code so can't point you forward with that.

            – Lauri Peltonen
            5 hours ago











          • Here we go.

            – Lance Pollard
            5 hours ago











          • This say's it's not based on compute time but is instead based on individual instructions' evaluation.

            – Lance Pollard
            5 hours ago





















          • Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

            – Lance Pollard
            6 hours ago













          • Good point on (1), same with (2).

            – Lance Pollard
            5 hours ago













          • Sorry, I'm not familiar with the code so can't point you forward with that.

            – Lauri Peltonen
            5 hours ago











          • Here we go.

            – Lance Pollard
            5 hours ago











          • This say's it's not based on compute time but is instead based on individual instructions' evaluation.

            – Lance Pollard
            5 hours ago



















          Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

          – Lance Pollard
          6 hours ago







          Awesome, good to know! I thought it would come as a performance hit to do it this way. Wondering if you could point me to the source code for Ethereum that invokes a contract's functions one by one, and then does the charge. That would be really interesting to see!

          – Lance Pollard
          6 hours ago















          Good point on (1), same with (2).

          – Lance Pollard
          5 hours ago







          Good point on (1), same with (2).

          – Lance Pollard
          5 hours ago















          Sorry, I'm not familiar with the code so can't point you forward with that.

          – Lauri Peltonen
          5 hours ago





          Sorry, I'm not familiar with the code so can't point you forward with that.

          – Lauri Peltonen
          5 hours ago













          Here we go.

          – Lance Pollard
          5 hours ago





          Here we go.

          – Lance Pollard
          5 hours ago













          This say's it's not based on compute time but is instead based on individual instructions' evaluation.

          – Lance Pollard
          5 hours ago







          This say's it's not based on compute time but is instead based on individual instructions' evaluation.

          – Lance Pollard
          5 hours ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ethereum 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%2fethereum.stackexchange.com%2fquestions%2f67199%2fwhy-transactions-contracts-arent-priced-tracked-based-on-computer-running-time%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

          How to label and detect the document text images

          Vallis Paradisi

          Tabula Rosettana