pull down to refresh

0 sats \ 1 reply \ @rijndael 18 Aug 2022 \ parent \ on: "Satoshi used a 32bit uint for nTime that'll require an ugly hard fork"- BTC dev bitcoin

We'll end up fixing it in a hard fork

write
preview
0 sats \ 0 replies \ @Brunswick 18 Aug 2022

I love how this issue was shutdown by a bunch of dickwads rather than addressing the concern.

https://github.com/bitcoin/bitcoin/issues/18182

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.

https://github.com/bitcoin/bitcoin/issues/21356#issuecomment-1126880786

reply