From: Peter Todd <pete@petertodd•org>
To: Tao Effect <contact@taoeffect•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Network partition recovery
Date: Fri, 21 Jun 2024 01:30:12 +0000 [thread overview]
Message-ID: <ZnTXpNIPIeCwHSvx@petertodd.org> (raw)
In-Reply-To: <CC066457-A396-4680-8F11-F013E5EFDD1E@taoeffect.com>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Fri, Jun 14, 2024 at 02:31:42PM -0700, Tao Effect wrote:
> What work has been done on recovering from a network partition?
>
> The day is fast approaching when Bitcoin could be split in two not by a purposeful fork, but because the Internet is split in two.
>
> Have Bitcoiners gamed this out? What happens when the Internet reconnects? Do we throw out half of the transactions? Or is a merge possible? Can it be done automatically?
Given how little bandwidth it takes to synchronize blocks, and the enormous
financial incentives to solve this problem, it's unlikely that an internet
split would result in a long term network partition. It's just too easy to fix
the split through technologies like satellite internet, amateur radio,
Blockstream satellite, pigeons, etc. If the event leading to the split manages
to defeat all these mechanisms on a large scale, there's a good chance that
Bitcoin is the least of our worries...
Anyway, transactions in blocks that have been reorged out can be mined in
subsequent blocks so long as there are no conflicts. In practice, this will
happen automatically.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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 on the web visit https://groups.google.com/d/msgid/bitcoindev/ZnTXpNIPIeCwHSvx%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-21 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:31 Tao Effect
2024-06-16 20:30 ` Ethan Heilman
2024-06-21 1:30 ` Peter Todd [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=ZnTXpNIPIeCwHSvx@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=contact@taoeffect$(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