{"type":"rich","version":"1.0","author_name":"npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","author_url":"https://nostr.ae/npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-12-14\n📝 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.\n\n\u003e On 5 Dec 2016, at 19:58, Tom Zander via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e On Sunday, 4 December 2016 21:37:39 CET Hampus Sjöberg via bitcoin-dev \n\u003e wrote:\n\u003e\u003e\u003e Also how about making timestamp 8 bytes?  2106 is coming up soon \n\u003e\u003e \n\u003e\u003e AFAICT this was fixed in this commit:\n\u003e\u003e https://github.com/jl2012/bitcoin/commit/\n\u003e fa80b48bb4237b110ceffe11edc14c813\n\u003e\u003e 0672cd2#diff-499d7ee7998a27095063ed7b4dd7c119R200\n\u003e \n\u003e That commit hacks around it, a new block header fixes it. Subtle difference.\n\u003e \n\u003e -- \n\u003e Tom Zander\n\u003e Blog: https://zander.github.io\n\u003e Vlog: https://vimeo.com/channels/tomscryptochannel\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"}