How does NOW work?2019 Community Moderator ElectionWhat does the DIP opcode in Michelson do?How can I deploy...

Looking for word that is not atheist or agnostic,

What is Earthy controling in the ISS cupola?

What are the practical Opportunty Attack values for a bugbear, holding a reach weapon, with Polearm Mastery?

Why doesn't this Google Translate ad use the word "Translation" instead of "Translate"?

How did Alan Turing break the enigma code using the hint given by the lady in the bar?

What problems would a superhuman have whose skin is constantly hot?

Accepted offer letter, position changed

Are there historical instances of the capital of a colonising country being temporarily or permanently shifted to one of its colonies?

Could you please stop shuffling the deck and play already?

They call me Inspector Morse

Was Luke Skywalker the leader of the Rebel forces on Hoth?

How does NOW work?

Signed and unsigned numbers

Are all players supposed to be able to see each others' character sheets?

In the quantum hamiltonian, why does kinetic energy turn into an operator while potential doesn't?

Do f-stop and exposure time perfectly cancel?

Examples of a statistic that is not independent of sample's distribution?

Having the player face themselves after the mid-game

Do I really need to have a scientific explanation for my premise?

Are babies of evil humanoid species inherently evil?

bad quality map when exporting as PDF

Is it necessary to separate DC power cables and data cables?

IBM PAT Number Sequence

Rewrite the power sum in terms of convolution



How does NOW work?



2019 Community Moderator ElectionWhat does the DIP opcode in Michelson do?How can I deploy a Michelson smart contract?How SET_CAR/SET_CDR macros should be expanded?What is the BigMap container and why does it matter?












7















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?










share|improve this question



























    7















    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?










    share|improve this question

























      7












      7








      7


      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?










      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 12 hours ago









      RobRob

      2635




      2635






















          3 Answers
          3






          active

          oldest

          votes


















          3














          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
              3 hours ago






            • 1





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

              – FFF
              2 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









              3














              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




























                3














                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


























                  3












                  3








                  3







                  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 6 hours ago









                  lefessanlefessan

                  2,547522




                  2,547522























                      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
                        3 hours ago






                      • 1





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

                        – FFF
                        2 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
                        3 hours ago






                      • 1





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

                        – FFF
                        2 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 5 hours ago









                      FFFFFF

                      601212




                      601212













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

                        – Rob
                        3 hours ago






                      • 1





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

                        – FFF
                        2 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
                        3 hours ago






                      • 1





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

                        – FFF
                        2 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
                      3 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
                      3 hours ago




                      1




                      1





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

                      – FFF
                      2 hours ago





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

                      – FFF
                      2 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 1 hour 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

                              Installing LyX: “No textclass is found.”LyX installation error- text class not found- 'Reconfigure' or...

                              (1602) Indiana Índice Designación y nombre Características orbitales Véase...

                              Universidad Autónoma de Occidente Índice Historia Campus Facultades Programas Académicos Medios de...