https://dyscour.se/post/12679668746/using-tai64-for-logging https://dyscour.se/post/12679668746/using-tai64-for-logging > This means that the date is stored as

https://dyscour.se/post/12679668746/using-tai64-for-logging https://dyscour.se/post/12679668746/using-tai64-for-logging > This means that the date is stored as a 64-bit number, the bottom 63 bits being the number of seconds since 1970-01-01 in TAI, offset by 2^62. In essence, this makes the value quite similar to time_t (which uses UTC), except for two things: > There are 63 bits to play with, not just 32 (no year-2038 problems!). > The timestamp is always monotonic, counting all leap seconds. TAI time seems to be just UTC unix timestamps but accounting for leap seconds. Since leap seconds are slated to be retired after 2035, I’m guessing TAI time and Unix time won’t be so different after that.