Yes, all part of details left out of my general overview.
Time increment rollover is an issue even if clocks are synced perfectly. This is due to an uncontrollable human factor --- delay from the time the code is generated until it is input and submitted.
To account for this, most receivers will check the provided hash code against both the current and the previous time increment.
Comments
Yes, all part of details left out of my general overview.
Time increment rollover is an issue even if clocks are synced perfectly. This is due to an uncontrollable human factor --- delay from the time the code is generated until it is input and submitted.
To account for this, most receivers will check the provided hash code against both the current and the previous time increment.
Very cool! This makes a lot of sense across the board. Thanks for explaining this!