From: Eric Voskuil <eric@voskuil.org>
To: Sjors Provoost <sjors@sprovoost.nl>, Ruben Somsen <rsomsen@gmail.com>
Cc: bitcoindev@googlegroups.com, luke@dashjr.org
Subject: Re: [bitcoindev] The Tragic Tale of BIP30
Date: Sat, 10 May 2025 11:39:11 -0400 [thread overview]
Message-ID: <ECE5766B-F902-4CA4-9DFC-7718C1DA4173@voskuil.org> (raw)
In-Reply-To: <035401dbbba6$7ea41790$7bec46b0$@voskuil.org>
This thread seems to have gone silent. Are these pending hard forks no longer interesting?
e
> This ignores the chain splits resulting from the 14 checkpoints that have
> been removed to get to block 1. If the consensus is to not care about these
> hard forks causing chain splits, there is really no reason to care about
> this BIP30 chain split being caused by their removal.
>
> Best,
> Eric
--
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/ECE5766B-F902-4CA4-9DFC-7718C1DA4173%40voskuil.org.
next prev parent reply other threads:[~2025-05-10 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 16:45 [bitcoindev] The Tragic Tale of BIP30 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
2025-04-29 15:11 ` Ruben Somsen
2025-04-29 15:28 ` Sjors Provoost
2025-05-02 21:09 ` eric
2025-05-10 15:39 ` Eric Voskuil [this message]
2025-05-10 16:17 ` Sjors Provoost
2025-05-10 16:55 ` Eric Voskuil
2025-05-02 21:09 ` eric
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=ECE5766B-F902-4CA4-9DFC-7718C1DA4173@voskuil.org \
--to=eric@voskuil.org \
--cc=bitcoindev@googlegroups.com \
--cc=luke@dashjr.org \
--cc=rsomsen@gmail.com \
--cc=sjors@sprovoost.nl \
/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