From: Ethan Heilman <eth3rs@gmail•com>
To: Tao Effect <contact@taoeffect•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Network partition recovery
Date: Sun, 16 Jun 2024 16:30:07 -0400 [thread overview]
Message-ID: <CAEM=y+XzVksuon-bUsc=44UEw0vWVi_QmB5jjtkLp2VdO2QzbQ@mail.gmail.com> (raw)
In-Reply-To: <CC066457-A396-4680-8F11-F013E5EFDD1E@taoeffect.com>
[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]
> Have Bitcoiners gamed this out?
Not that I am aware of.
Short term partitions (10 to 30 minutes) would likely not be noticed by
most users. Long term partitions (1 day to 1 week) would likely cause
relying parties to find non-internet mechanisms to communicate blocks and
transactions.
If say 20% of the mining power was stuck in a partition, the miners in that
partition would likely stop mining once they realized they were partitioned
because they would understand they would lose all their rewards when the
partition stops. Likely people in the partition would no longer respect
confirmations made by miners in the partition because those confirmations
will be reversed when the partition ends.
It seems likely that parties (miners, relying parties) in the partition
will attempt to communicate outside the partition to interact with Bitcoin.
The issue becomes much trickier if the partition, partitions mining power
exactly into 50%. It is unlikely that if the internet has a long term
partition it will exactly split the mining power.
> What happens when the Internet reconnects?
"Longest" chain wins.
> Or is a merge possible? Can it be done automatically?
Some DAG chains do allow to two forks to be merged automatically including
resolving double spends. Adding this functionality in Bitcoin would likely
be the biggest consensus change in the history of Bitcoin.
On Sat, Jun 15, 2024, 6:11 PM Tao Effect <contact@taoeffect•com> 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?
>
> - 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
> .
>
--
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/CAEM%3Dy%2BXzVksuon-bUsc%3D44UEw0vWVi_QmB5jjtkLp2VdO2QzbQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4016 bytes --]
next prev parent reply other threads:[~2024-06-16 20:35 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 [this message]
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='CAEM=y+XzVksuon-bUsc=44UEw0vWVi_QmB5jjtkLp2VdO2QzbQ@mail.gmail.com' \
--to=eth3rs@gmail$(echo .)com \
--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