package octez-libs
A package that contains multiple base libraries used by the Octez suite
Install
Dune Dependency
Authors
Maintainers
Sources
octez-19.0.tar.gz
sha256=c6df840ebbf115e454db949028c595bec558a59a66cade73b52a6d099d6fa4d4
sha512=d8aee903b9fe130d73176bc8ec38b78c9ff65317da3cb4f3415f09af0c625b4384e7498201fdb61aa39086a7d5d409d0ab3423f9bc3ab989a680cf444a79bc13
doc/octez-libs.base/Tezos_base/Time/index.html
Module Tezos_base.Time
Source
Time management
This module supports two distinct notions of time. The first notion of time is the time as handled by the protocol. This is the time that appears in the header of blocks, the time that baking slots are specified on, etc. It only has second-level precision.
The second notion of time is the time as handled by the system. This is the time as returned by the processor clock, the time that network timeouts are specified on, etc. In has sub-second precision.
The distinction between the two notions of time is important for multiple reasons:
- Protocol time and system time may evolve independently. E.g., if a protocol update changes the notion of time.
- Protocol time and system time have different levels of precision.
- Protocol time and system time have different end-of-times. Respectively that's int64 end-of-time (some time in the year 292277026596) and RFC3339 end-of-time (end of the year 9999).
Note that while Protocol time has the int64 range, many of its functions do not work outside of the RFC3339 range, namely:
- all
xx_notation_xx
functions (will be renamed and moved to an RFC submodule later) rfc_encoding
pp_hum
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>