How does NOW work?












8















Say a contract has a condition based on NOW being after a time. Is NOW UTC, and is this validated by each node before being added to the chain? Let's say you want ensure a function is called during a 1 hour window, will this be possible to enforce?



For example:



current stack state: NOW - 15 minutes :: NOW + 45 minutes //pseudocode

code: NOW; SUB; GT; SWAP;

      NOW; SWAP; SUB;

      AND;

      IF { send transaction... } { FAIL; };


This should check that it's greater than NOW - 15 minutes and less than NOW + 45 minutes, which are both true so it can execute the transaction.



It might also be important to understand how the network gets consensus on a block time across the network?






michelson







share|improve this question



























    8















    Say a contract has a condition based on NOW being after a time. Is NOW UTC, and is this validated by each node before being added to the chain? Let's say you want ensure a function is called during a 1 hour window, will this be possible to enforce?



    For example:



    current stack state: NOW - 15 minutes :: NOW + 45 minutes //pseudocode
    
code: NOW; SUB; GT; SWAP;
    
      NOW; SWAP; SUB;
    
      AND;
    
      IF { send transaction... } { FAIL; };


    This should check that it's greater than NOW - 15 minutes and less than NOW + 45 minutes, which are both true so it can execute the transaction.



    It might also be important to understand how the network gets consensus on a block time across the network?






    michelson







    share|improve this question

























      8












      8








      8


      1






      Say a contract has a condition based on NOW being after a time. Is NOW UTC, and is this validated by each node before being added to the chain? Let's say you want ensure a function is called during a 1 hour window, will this be possible to enforce?



      For example:



      current stack state: NOW - 15 minutes :: NOW + 45 minutes //pseudocode
      
code: NOW; SUB; GT; SWAP;
      
      NOW; SWAP; SUB;
      
      AND;
      
      IF { send transaction... } { FAIL; };


      This should check that it's greater than NOW - 15 minutes and less than NOW + 45 minutes, which are both true so it can execute the transaction.



      It might also be important to understand how the network gets consensus on a block time across the network?






      michelson







      share|improve this question














      Say a contract has a condition based on NOW being after a time. Is NOW UTC, and is this validated by each node before being added to the chain? Let's say you want ensure a function is called during a 1 hour window, will this be possible to enforce?



      For example:



      current stack state: NOW - 15 minutes :: NOW + 45 minutes //pseudocode
      
code: NOW; SUB; GT; SWAP;
      
      NOW; SWAP; SUB;
      
      AND;
      
      IF { send transaction... } { FAIL; };


      This should check that it's greater than NOW - 15 minutes and less than NOW + 45 minutes, which are both true so it can execute the transaction.



      It might also be important to understand how the network gets consensus on a block time across the network?






      michelson




      michelson






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 17 hours ago









      RobRob

      2835




      2835






















          3 Answers
          3






          active

          oldest

          votes


















          4














          There is an assumption that all Tezos nodes are synchronized, otherwise the consensus with 1-minute slots would not work. Of course, some delay is ok, but more than a few seconds might prevent a baker from baking.



          NOW is the time at which the block, containing the transaction, should be baked. So, the baker knows the last block time, he knows his slot, so he can compute the time at which he should bake the block. It then uses that time to execute the transactions.






          share|improve this answer































            2














            Nodes time being synchronized is only part of the picture: bakers can always be offline for their own reasons, the network can be stalled, many other transactions could be competing to get selected by bakers, etc. so people need to be very cautious and give plenty of time for an event to occur.



            I would say that a few minutes or even hours is not enough today.
            Is one day enough ? I would tend to think so but I'm not even certain.






            share|improve this answer
























            • If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

              – Rob
              8 hours ago






            • 2





              Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

              – FFF
              7 hours ago



















            2














            The baker chooses the value of NOW. I am aware of these two constraints:



            The protocol enforces that the timestamp is at least the minimal timestamp at which the baker was supposed to bake (some delay after the previous block's timestamp): baking.ml.



            The shell will also ignore a block whose timestamp is too far in the future (more than 15s) relative to the system clock: distributed_db.ml.






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


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f735%2fhow-does-now-work%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              4














              There is an assumption that all Tezos nodes are synchronized, otherwise the consensus with 1-minute slots would not work. Of course, some delay is ok, but more than a few seconds might prevent a baker from baking.



              NOW is the time at which the block, containing the transaction, should be baked. So, the baker knows the last block time, he knows his slot, so he can compute the time at which he should bake the block. It then uses that time to execute the transactions.






              share|improve this answer




























                4














                There is an assumption that all Tezos nodes are synchronized, otherwise the consensus with 1-minute slots would not work. Of course, some delay is ok, but more than a few seconds might prevent a baker from baking.



                NOW is the time at which the block, containing the transaction, should be baked. So, the baker knows the last block time, he knows his slot, so he can compute the time at which he should bake the block. It then uses that time to execute the transactions.






                share|improve this answer


























                  4












                  4








                  4







                  There is an assumption that all Tezos nodes are synchronized, otherwise the consensus with 1-minute slots would not work. Of course, some delay is ok, but more than a few seconds might prevent a baker from baking.



                  NOW is the time at which the block, containing the transaction, should be baked. So, the baker knows the last block time, he knows his slot, so he can compute the time at which he should bake the block. It then uses that time to execute the transactions.






                  share|improve this answer













                  There is an assumption that all Tezos nodes are synchronized, otherwise the consensus with 1-minute slots would not work. Of course, some delay is ok, but more than a few seconds might prevent a baker from baking.



                  NOW is the time at which the block, containing the transaction, should be baked. So, the baker knows the last block time, he knows his slot, so he can compute the time at which he should bake the block. It then uses that time to execute the transactions.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 12 hours ago









                  lefessanlefessan

                  2,557522




                  2,557522























                      2














                      Nodes time being synchronized is only part of the picture: bakers can always be offline for their own reasons, the network can be stalled, many other transactions could be competing to get selected by bakers, etc. so people need to be very cautious and give plenty of time for an event to occur.



                      I would say that a few minutes or even hours is not enough today.
                      Is one day enough ? I would tend to think so but I'm not even certain.






                      share|improve this answer
























                      • If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                        – Rob
                        8 hours ago






                      • 2





                        Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                        – FFF
                        7 hours ago
















                      2














                      Nodes time being synchronized is only part of the picture: bakers can always be offline for their own reasons, the network can be stalled, many other transactions could be competing to get selected by bakers, etc. so people need to be very cautious and give plenty of time for an event to occur.



                      I would say that a few minutes or even hours is not enough today.
                      Is one day enough ? I would tend to think so but I'm not even certain.






                      share|improve this answer
























                      • If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                        – Rob
                        8 hours ago






                      • 2





                        Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                        – FFF
                        7 hours ago














                      2












                      2








                      2







                      Nodes time being synchronized is only part of the picture: bakers can always be offline for their own reasons, the network can be stalled, many other transactions could be competing to get selected by bakers, etc. so people need to be very cautious and give plenty of time for an event to occur.



                      I would say that a few minutes or even hours is not enough today.
                      Is one day enough ? I would tend to think so but I'm not even certain.






                      share|improve this answer













                      Nodes time being synchronized is only part of the picture: bakers can always be offline for their own reasons, the network can be stalled, many other transactions could be competing to get selected by bakers, etc. so people need to be very cautious and give plenty of time for an event to occur.



                      I would say that a few minutes or even hours is not enough today.
                      Is one day enough ? I would tend to think so but I'm not even certain.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 10 hours ago









                      FFFFFF

                      621212




                      621212













                      • If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                        – Rob
                        8 hours ago






                      • 2





                        Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                        – FFF
                        7 hours ago



















                      • If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                        – Rob
                        8 hours ago






                      • 2





                        Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                        – FFF
                        7 hours ago

















                      If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                      – Rob
                      8 hours ago





                      If I'm experimenting with building something that can hit milestones during smaller ranges. Kind of curious how close those milestones can be.

                      – Rob
                      8 hours ago




                      2




                      2





                      Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                      – FFF
                      7 hours ago





                      Understood but let's all remember Fomo3d medium.com/coinmonks/… on Ethereum before requiring milestones too fast.

                      – FFF
                      7 hours ago











                      2














                      The baker chooses the value of NOW. I am aware of these two constraints:



                      The protocol enforces that the timestamp is at least the minimal timestamp at which the baker was supposed to bake (some delay after the previous block's timestamp): baking.ml.



                      The shell will also ignore a block whose timestamp is too far in the future (more than 15s) relative to the system clock: distributed_db.ml.






                      share|improve this answer




























                        2














                        The baker chooses the value of NOW. I am aware of these two constraints:



                        The protocol enforces that the timestamp is at least the minimal timestamp at which the baker was supposed to bake (some delay after the previous block's timestamp): baking.ml.



                        The shell will also ignore a block whose timestamp is too far in the future (more than 15s) relative to the system clock: distributed_db.ml.






                        share|improve this answer


























                          2












                          2








                          2







                          The baker chooses the value of NOW. I am aware of these two constraints:



                          The protocol enforces that the timestamp is at least the minimal timestamp at which the baker was supposed to bake (some delay after the previous block's timestamp): baking.ml.



                          The shell will also ignore a block whose timestamp is too far in the future (more than 15s) relative to the system clock: distributed_db.ml.






                          share|improve this answer













                          The baker chooses the value of NOW. I am aware of these two constraints:



                          The protocol enforces that the timestamp is at least the minimal timestamp at which the baker was supposed to bake (some delay after the previous block's timestamp): baking.ml.



                          The shell will also ignore a block whose timestamp is too far in the future (more than 15s) relative to the system clock: distributed_db.ml.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 6 hours ago









                          TomTom

                          87327




                          87327






























                              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%2f735%2fhow-does-now-work%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

                              Loup dans la culture

                              Image
                              Loups sur une enluminure du Bestiaire d'Aberdeen Le loup est l'animal le plus emblématique de l'histoire de l'Eurasie, il était à l'honneur durant l'Antiquité chez la totalité des anciens peuples européens [ 1 ] . Sommaire 1 Le loup dans la mythologie 2 Les loups dans le folklore 2.1 L'évolution des mentalités 2.2 Le loup dans la psychanalyse 3 Le loup dans les œuvres culturelles 3.1 Le loup dans la littérature 3.1.1 Fables 3.1.2 Poésie 3.1.3 Romans 3.1.4 Littérature jeunesse 3.1.4.1 Quelques titres d'albums contemporains 3.1.5 Bande dessinée 3.2 Le loup à l'écran 3.2.1 Le cinéma et la télévision 3.2.2 Documentaires 3.2.3 Dessins animés 3.2.4 Jeux vidéo 3.3 Le loup en peinture et en sculpture 3.4 Le loup dans les œuvres musicales 4 Le loup et les noms propres 5 Bibliographie 6 Notes et références 7 Voir aussi 7.1 Articles connexes ...
                              Read more

                              How to solve the problem of ntp “Unable to contact time server” from KDE?

                              Image
                              1 0 I want to set date and time automatically but this error appears when I try to .. I'm using openSUSE, I tried different servers but it didn't work either, help please! It doesn't seem to be a network problem: $ ping pool.ntp.org 64 bytes from 41.78.128.17: icmp_seq=1 ttl=41 time=260 ms To the question of whether ntpd is installed and running: $ ps -C ntpd PID TTY TIME CMD i.e. there's no ntpd process running. $ rpm -qa | grep ntp yast2-ntp-client-3.1.12-1.7.noarch ntp-4.2.6p5-25.2.1.i586 Further information from the comments: $ sudo ntpdate pool.ntp.org 25 Sep 19:41:51 ntpdate[3162]: no server suitable for synchronization found networking kde opensuse ntp ntpd sh...
                              Read more

                              ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux

                              Image
                              0 1 I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture 1). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved? EDIT1: I have had a look at the official Windows drivers for the UX433FA TouchPad, but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited. ...
                              Read more