public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tao Effect <contact@taoeffect•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Network partition recovery
Date: Fri, 14 Jun 2024 14:31:42 -0700	[thread overview]
Message-ID: <CC066457-A396-4680-8F11-F013E5EFDD1E@taoeffect.com> (raw)

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?

- Greg

-- 
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/CC066457-A396-4680-8F11-F013E5EFDD1E%40taoeffect.com.


             reply	other threads:[~2024-06-15 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 21:31 Tao Effect [this message]
2024-06-16 20:30 ` Ethan Heilman
2024-06-21  1:30 ` Peter Todd

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=CC066457-A396-4680-8F11-F013E5EFDD1E@taoeffect.com \
    --to=contact@taoeffect$(echo .)com \
    --cc=bitcoindev@googlegroups.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