From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 65BF1C000D for ; Sun, 17 Oct 2021 08:19:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 60BDB4027A for ; Sun, 17 Oct 2021 08:19: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: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 124rarO1A601 for ; Sun, 17 Oct 2021 08:19:20 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) by smtp2.osuosl.org (Postfix) with ESMTPS id 2C0AF40172 for ; Sun, 17 Oct 2021 08:19:20 +0000 (UTC) Received: by mail-yb1-xb2c.google.com with SMTP id a7so1372151yba.6 for ; Sun, 17 Oct 2021 01:19:20 -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 :cc; bh=AFslvqKqjbdCQqRr9D7En1pzal9Krx2xyL3vVmhrZcw=; b=WJ2D3rI+49KsPVS2lhbJFEJr4HiNXsO8KX6GpYv5+Y1KAa3+A81UWFN1nP4gbAHEdX Xcp5HinNsCTScJcpvnjjNTRtm3YytAbCv0+9zHUX7Cc4HgnHu/+UlsE/D2Km87D/ZmgJ WRt8U11SgkwMpvtEx3+oMH9iVeKWc6t/Ae0xODm6BVxHGIprBnamwc8o1I1yscbjNx7l 6vGZYWPxcmyk3OvRJp9+gwf8QQyZV4ujhRFOlrEpAEO8UOBIHjiz8IYFEPIPKikzkIu9 M3hssbAXmvQi10v564FrIW6v1aE6kQ6S4sIDFineU+4xWOrNqwa2dVIEpdAYVMdsBOPC UT3w== 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:cc; bh=AFslvqKqjbdCQqRr9D7En1pzal9Krx2xyL3vVmhrZcw=; b=YOFrIw7XI6U4b4Rrw3qM8Da4IMxr8SYxEc8bXOJeO4xiZWCiLTdyBNJqcTXcxkHA58 195NexJ1pRzMMIcntsrkcHxJ/MT9DXv481ssU8EcIgz/AY+CeSwp9r/tkrQqk/kIray3 qFmNFDqyhp/jz+px/tZxtrm9o6LopHgHxS4+2mqzoos9+T8REcRhIHFZBVO3Tnl+RMES 8bplai+yT1jd4gnNHNzYRSeaQGd2aSSFiDfQDUQ8Hvj+JoAS0RHSVvApR27j6s5OeSts q+43Cx2+QT3+HVPn4JYurSECjomFhgo/fbIeypfk66awou2qz1G2UTAXXh1LBJuJJuCX L3UQ== X-Gm-Message-State: AOAM531wHNX/fEl1ErROhOhPlR0b/bQ1yIuolJrV6SXB0g3b3xR8UVJV BqQkLJ76JBZCZkh9g7EgFOAe5GRm65hOz0YyJLA= X-Google-Smtp-Source: ABdhPJw/LwqELQVgJzXP1+v4KRo8zfHTA2XfHwARU2Qop7TQtb476nmoLAmypWqvG8YoeUX4aNyf/gKorisOVJf3ApA= X-Received: by 2002:a25:1ac6:: with SMTP id a189mr22587402yba.149.1634458759083; Sun, 17 Oct 2021 01:19:19 -0700 (PDT) MIME-Version: 1.0 References: <50769965-423dd279413d4dba11ba459cbd98387b@pmq6v.m5r2.onet> In-Reply-To: From: Kate Salazar Date: Sun, 17 Oct 2021 10:19:07 +0200 Message-ID: To: James Lu , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000bc38f205ce8815d0" X-Mailman-Approved-At: Sun, 17 Oct 2021 08:26:45 +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: Sun, 17 Oct 2021 08:19:21 -0000 --000000000000bc38f205ce8815d0 Content-Type: text/plain; charset="UTF-8" There is a hard fork wishlist: https://en.bitcoin.it/wiki/Hardfork_Wishlist Note last update is somewhat old. Cheers. On Sat, Oct 16, 2021 at 12:49 AM James Lu via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 >> > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000bc38f205ce8815d0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There is a hard fork wishlist:

Note last up= date is somewhat old.

Cheers.

= It seems that Bitcoin Core will stop working in 2038 because of assertion c= hecking if the current time is non-negative. Also, the whole chain will hal= t after reaching median time 0xffffffff in 2106. More information: = https://bitcointalk.org/index.php?topic=3D5365359.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/mail= man/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000bc38f205ce8815d0--