From: Kate Salazar <mercedes.catherine.salazar@gmail•com>
To: James Lu <jamtlu@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Year 2038 problem and year 2106 chain halting
Date: Sun, 17 Oct 2021 10:19:07 +0200 [thread overview]
Message-ID: <CAHiDt8Arc6yBobY82KrqfF5-e+wCdGpCN_7okUVgf=9s58kcvQ@mail.gmail.com> (raw)
In-Reply-To: <CANQHGB2Vm31Y8aGsrx3qNitRWh4y950LxxjzHqrD=qzwN=FmVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2699 bytes --]
next prev parent reply other threads:[~2021-10-17 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 19:16 vjudeu
2021-10-15 15:27 ` James Lu
2021-10-17 8:19 ` Kate Salazar [this message]
2021-10-17 22:38 ` damian
2021-10-15 15:44 ` yanmaani
2021-10-15 22:22 ` vjudeu
2021-10-17 15:14 ` yanmaani
2021-10-17 15:46 ` Kate Salazar
2021-10-18 2:55 ` yanmaani
2021-10-15 23:01 ` ZmnSCPxj
2021-10-16 9:06 ` vjudeu
2021-10-16 20:37 ` David Bakin
2021-10-16 21:34 ` Kate Salazar
2021-10-16 23:23 ` ZmnSCPxj
2021-10-17 7:24 vjudeu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHiDt8Arc6yBobY82KrqfF5-e+wCdGpCN_7okUVgf=9s58kcvQ@mail.gmail.com' \
--to=mercedes.catherine.salazar@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jamtlu@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox