Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 381E7C000D for ; Fri, 15 Oct 2021 15:28:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 19B2583B77 for ; Fri, 15 Oct 2021 15:28:21 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uxUUl7btBBgA for ; Fri, 15 Oct 2021 15:28:19 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by smtp1.osuosl.org (Postfix) with ESMTPS id DD82D83B72 for ; Fri, 15 Oct 2021 15:28:19 +0000 (UTC) Received: by mail-pf1-x42e.google.com with SMTP id v8so4518122pfu.11 for ; Fri, 15 Oct 2021 08:28:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Fe588tpLivanOZqIj7/9ghzB8OJxiihUdboxEqnM1+A=; b=MKDbAYJhl4URysbrHVBm+lSihDpd1Y5ejUk9d2ecWQzUfpLHPUjUjTSaebr90c979m RdFfiReahHQZhU+rpiADsvBFRq3aCedLRjiLJ/rGDXmov6kSIwmlgK1mYR07Uw1qgho4 5VsEWzpqX34PLhyD829VyHvHbgkfYuoXUwTL8jVke8wTRyVS49PdwaxZ1e9ttCP81ndd vKG5R6YQTQYPiv7eClZ+Cq/fjsRiJbez1NiycANg7ooUrJLJoUZONUppYlyRXk2RChQo MvzY+oChwZuSG4HUAyWouMdeD4P00TmnmYQTEitqAR6CSBYQboggRpWmalGD9yK01tqO hStA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Fe588tpLivanOZqIj7/9ghzB8OJxiihUdboxEqnM1+A=; b=lYuSykeH5mHLKse9+/E3YwuXI5c0WdaKgBpye/cCa1HztLANWmm3RfxDcYgn32bt1W b6vyTlW3y5a+8iXvNcdHY/PIS5IssJ5UJNwBIczjB3SMnrnJ4dJEURqdQjSDqVcDde4O R+kcLW89aBvNBD/togh7BXbemxqHXzxkLgvOuucXsg49i9hDfcDHmu2tSbI5RF0Pr8fr UScjamvEJpZItGSQ4xn+bpbm9QYpFWRs1Kdmaywfc+XnsXOZ35whdT/XrrOUgkbLTGY0 FgXZ36g9nIDl6lhJHmg4hirkjUDfOKDhfjTVKi+eLl+wCTq5nro/oPn1dJ7ALp2VutEf +rag== X-Gm-Message-State: AOAM530ydSz+F882RA/C0xtZ+YdS2pJCaLqzIinXxdwGk+d42WgRvK64 JdJbG4eALMGny7c0R8hel+iapkHPb/uBtQlg5jw= X-Google-Smtp-Source: ABdhPJxb8WUDP95Brc3szeyZGVqK1fHdupnd6y+QZ+GNtBpw4k7S1Red2ZqPORVXzo9A/lhSjQhlhbDhwpC1tIt3kXA= X-Received: by 2002:a65:4209:: with SMTP id c9mr9442639pgq.399.1634311699124; Fri, 15 Oct 2021 08:28:19 -0700 (PDT) MIME-Version: 1.0 References: <50769965-423dd279413d4dba11ba459cbd98387b@pmq6v.m5r2.onet> In-Reply-To: <50769965-423dd279413d4dba11ba459cbd98387b@pmq6v.m5r2.onet> From: James Lu Date: Fri, 15 Oct 2021 11:27:42 -0400 Message-ID: To: vjudeu@gazeta.pl, Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000047593905ce65d83a" X-Mailman-Approved-At: Fri, 15 Oct 2021 22:48:22 +0000 Subject: Re: [bitcoin-dev] Year 2038 problem and year 2106 chain halting X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2021 15:28:21 -0000 --00000000000047593905ce65d83a Content-Type: text/plain; charset="UTF-8" Making Bitcoin function after 2038 is by definition a hard fork I feel if we do HF, we should bundle other HF changes with it... On Wed, Oct 13, 2021 at 5:19 PM vjudeu via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > It seems that Bitcoin Core will stop working in 2038 because of assertion > checking if the current time is non-negative. Also, the whole chain will > halt after reaching median time 0xffffffff in 2106. More information: > https://bitcointalk.org/index.php?topic=5365359.0 > > I wonder if that kind of issues are possible to fix in a soft-fork way. > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --00000000000047593905ce65d83a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Making Bitcoin function a= fter 2038 is by definition a hard fork

I feel if we do HF, we should = bundle other HF changes with it...

On Wed, Oct 13, 2021 at 5:19 PM vju= deu via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
It seems that Bitcoin Core = will stop working in 2038 because of assertion checking if the current time= is non-negative. Also, the whole chain will halt after reaching median tim= e 0xffffffff in 2106. More information: https://bitcointalk.org/inde= x.php?topic=3D5365359.0

I wonder if that kind of issues are poss= ible to fix in a soft-fork way.
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--00000000000047593905ce65d83a--