rich1.0npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9https://nostr.ae/npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9njumphttps://nostr.ae📅 Original date posted:2016-12-14 📝 Original message:There is no reason to use a timestamp beyond 4 bytes. Just let it overflow. If a blockchain is stopped for more than 2^31 seconds, it’s just dead. > On 5 Dec 2016, at 19:58, Tom Zander via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote: > > On Sunday, 4 December 2016 21:37:39 CET Hampus Sjöberg via bitcoin-dev > wrote: >>> Also how about making timestamp 8 bytes? 2106 is coming up soon >> >> AFAICT this was fixed in this commit: >> https://github.com/jl2012/bitcoin/commit/ > fa80b48bb4237b110ceffe11edc14c813 >> 0672cd2#diff-499d7ee7998a27095063ed7b4dd7c119R200 > > That commit hacks around it, a new block header fixes it. Subtle difference. > > -- > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev