From: Eric Voskuil <eric@voskuil•org>
To: Sjors Provoost <sjors@sprovoost•nl>
Cc: bitcoindev@googlegroups.com, Ruben Somsen <rsomsen@gmail•com>
Subject: Re: [bitcoindev] The Tragic Tale of BIP30
Date: Mon, 28 Apr 2025 08:39:24 -0400 [thread overview]
Message-ID: <E8225EAC-BED8-4840-8E3D-81A55C365209@voskuil.org> (raw)
In-Reply-To: <86FA0255-1A81-4DA1-9B1A-E57AD4F1DAAD@sprovoost.nl>
> On Apr 28, 2025, at 08:04, Sjors Provoost <sjors@sprovoost•nl> wrote:
>
>> I'm not aware of any compelling argument to hard fork out the existing checkpoints
>
> Bitcoin Core plans to remove checkpoints entirely by v30 this fall. I just started a thread about this.
The thread does not provide or reference any compelling argument (or any argument that I can find) for removing the checkpoints.
One reference states that “assume valid” speeds IBD, but of course it does so by not validating. So this does not provide a comparable offset to the increased validation cost, and even if it did does not provide an argument for hard forking them out.
e
--
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/E8225EAC-BED8-4840-8E3D-81A55C365209%40voskuil.org.
prev parent reply other threads:[~2025-04-28 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 16:45 Ruben Somsen
2025-04-27 18:20 ` Luke Dashjr
2025-04-27 18:30 ` eric
2025-04-27 21:01 ` eric
2025-04-28 11:48 ` Sjors Provoost
2025-04-28 12:39 ` Eric Voskuil [this message]
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=E8225EAC-BED8-4840-8E3D-81A55C365209@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=rsomsen@gmail$(echo .)com \
--cc=sjors@sprovoost$(echo .)nl \
/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