Topic: 32-bit Timestamp in Block Header? (Read 321 times)
That is correct, the timestamp's maximum time is in 2106. After that, a lot of things could break. However this is a known problem and it is known almost a century in advance, so we have a lot of time to plan something to do. A hard fork could be done to expand the field to 64 bits or to some other scheme that does not have a maximum. I believe a soft fork could also be done to handle this.
I'm reading Mastering Bitcoin by Andreas Antonopoulos and it says that a 32-bit timestamp is used in the header (4 bytes), but by my calculation, that means that the timestamp will max out in 2106. What happens after that? Isn't the Unix epoch time usually represented by 64 bits?
Groovy Code:
println Instant.ofEpochSecond(Math.pow(256,4).toLong())
//Gives 2106-02-07T06:28:16Z
Groovy Code:
println Instant.ofEpochSecond(Math.pow(256,4).toLong())
//Gives 2106-02-07T06:28:16Z
Jump to: