public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sjors Provoost <sjors@sprovoost.nl>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] The Tragic Tale of BIP30
Date: Sat, 10 May 2025 18:17:34 +0200	[thread overview]
Message-ID: <4AC2B1A6-23F3-4A06-808F-448D9DD58FE2@sprovoost.nl> (raw)
In-Reply-To: <ECE5766B-F902-4CA4-9DFC-7718C1DA4173@voskuil.org>

Hi Eric,

I agree that deep-reorg BIP30 handling is not important. Although it _is_ an interesting exercise which helps to better understand consensus code. I think people got distracted a bit by recent drama. 

The Bitcoin Core project "decided" many years ago to not prioritise the graceful handling of extremely deep reorgs. You already stated your disagreement with that approach back then. The dropping of checkpoints is a continuation of that.

The only thing that would motivate me to bring back checkpoints (i.e. undo the PR that dropped them) is an attack that doesn't involve alien technology.

At the same time I don't object to, and might even review, changes that:

1. are simple enough, like Solution C earlier in the thread; or
2. someone writes a thorough BIP that goes though all the ways different (versions of) implementations handle extreme reorgs, and comes up with simple mitigations that make the handling consistent

As long as they don't bring checkpoints back. I think they've outlived their usefulness as consensus training wheels and now they're just an invitation for legal attacks (or future developer laziness).

- Sjors

> Op 10 mei 2025, om 17:39 heeft Eric Voskuil <eric@voskuil.org> het volgende geschreven:
> 
> 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/4AC2B1A6-23F3-4A06-808F-448D9DD58FE2%40sprovoost.nl.


  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
2025-05-10 16:17             ` Sjors Provoost [this message]
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=4AC2B1A6-23F3-4A06-808F-448D9DD58FE2@sprovoost.nl \
    --to=sjors@sprovoost.nl \
    --cc=bitcoindev@googlegroups.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