From: "'Russell O'Connor' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: Henry Romp <151henry151@gmail.com>
Subject: Re: [bitcoindev] [Discussion] Year 2106 Timestamp Overflow - Proposal for uint64 Migration
Date: Sun, 14 Dec 2025 08:59:26 -0500 [thread overview]
Message-ID: <CAMZUoKkXQv+LO_3iWf1_PnPMR7ocO0ddHZhfZo63Umst=pVCPg@mail.gmail.com> (raw)
In-Reply-To: <CAPnXYtNWr33O4aNCpKb_zQ+g0x14ZFLQQjMP===rvi3KF_amuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Sat, Dec 13, 2025 at 5:05 AM Henry Romp <151henry151@gmail.com> wrote:
> The blockchain won't "halt" at overflow, it will have validation problems.
> The overflow doesn't automatically stop the chain. Nodes would continue
> with wrapped-around timestamps (though this would cause some problems).
>
Yes the blockchain halts.
The timestamps are required to eventually increase; more specifically each
new timestamp is required to be strictly greater than the MTP timestamp.
Assuming these timestamps stay reasonably accurate up to the end then at
best you can squeeze out a few more blocks by lying about the time, but
eventually the MTP timestamp will reach its maximum value. At that point
there are no more valid blocks that can be appended to the chain.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMZUoKkXQv%2BLO_3iWf1_PnPMR7ocO0ddHZhfZo63Umst%3DpVCPg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1853 bytes --]
next prev parent reply other threads:[~2025-12-14 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 18:43 אושר חיים גליק
2025-12-12 12:25 ` Possibly
2025-12-12 13:40 ` Ethan Heilman
[not found] ` <CAPnXYtNWr33O4aNCpKb_zQ+g0x14ZFLQQjMP===rvi3KF_amuQ@mail.gmail.com>
2025-12-14 13:59 ` 'Russell O'Connor' via Bitcoin Development Mailing List [this message]
2025-12-15 9:59 ` Garlo Nicon
2025-12-15 19:09 ` Henry Romp
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='CAMZUoKkXQv+LO_3iWf1_PnPMR7ocO0ddHZhfZo63Umst=pVCPg@mail.gmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=151henry151@gmail.com \
--cc=roconnor@blockstream.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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