pull down to refresh
0 sats \ 2 replies \ @Brunswick 18 Aug 2022 \ on: "Satoshi used a 32bit uint for nTime that'll require an ugly hard fork"- BTC dev bitcoin
Two possible outcomes: either humanity learns to get along to fix this small issue, or humanity never adopts bitcoin and we blow ourselves up long before the bug is a problem.
Let's not forget we still have the 32 bit unix timestamp bug in 2038 that lies in wait in computers that likely will never be retired nor updated before then. Hopefully it'll only effect obsolete equipment BlackBerry phones and other QNX based systems
We'll end up fixing it in a hard fork
reply
I love how this issue was shutdown by a bunch of dickwads rather than addressing the concern.
It appears the 32bit problem only applies to a computation and proper casting of types when working with the clock. The nTime variable itself shouldn't require a hard fork because it only stores the differential time over a two week period.
reply