Return-Path: <jl2012@xbt.hk> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 546C25A7 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 14 Dec 2016 11:02:13 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B4BE413E for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 14 Dec 2016 11:02:12 +0000 (UTC) Received: from [172.21.35.100] (223.197.116.5 [223.197.116.5]) by mx.zohomail.com with SMTPS id 1481713323266783.7370202144289; Wed, 14 Dec 2016 03:02:03 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Johnson Lau <jl2012@xbt.hk> In-Reply-To: <22457494.p1MjVfM24j@cherry> Date: Wed, 14 Dec 2016 19:01:58 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8690A056-F1F9-480A-8C95-E1BF3D8417B2@xbt.hk> References: <FB8593E6-3CD7-46D5-8FC8-A73A0EF1AE9A@xbt.hk> <CAKEeUhjYPL+kO6RCc8UDZWeAEmFuX1NRfkv22uqR4K+FiGosDA@mail.gmail.com> <CAFMkqK-4jATqTsbFmS5GDPHhXW8X+6m+dBvc3nqknmea-fz_YA@mail.gmail.com> <22457494.p1MjVfM24j@cherry> To: Tom Zander <tomz@freedommail.ch>, bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> X-Mailer: Apple Mail (2.3124) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,MIME_QP_LONG_LINE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Forcenet: an experimental network with a new header format X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Wed, 14 Dec 2016 11:02:13 -0000 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=E2=80=99= s just dead. > On 5 Dec 2016, at 19:58, Tom Zander via bitcoin-dev = <bitcoin-dev@lists.linuxfoundation.org> wrote: >=20 > On Sunday, 4 December 2016 21:37:39 CET Hampus Sj=C3=B6berg via = bitcoin-dev=20 > wrote: >>> Also how about making timestamp 8 bytes? 2106 is coming up soon=20 >>=20 >> AFAICT this was fixed in this commit: >> https://github.com/jl2012/bitcoin/commit/ > fa80b48bb4237b110ceffe11edc14c813 >> 0672cd2#diff-499d7ee7998a27095063ed7b4dd7c119R200 >=20 > That commit hacks around it, a new block header fixes it. Subtle = difference. >=20 > --=20 > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev