From: Allen Piscitello <allen.piscitello@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is it possible for there to be two chains after a hard fork?
Date: Tue, 29 Sep 2015 12:43:55 -0500 [thread overview]
Message-ID: <CAJfRnm5=yrWE95T3+fzM_PxGxWJ38OnJMVxynTOKK1X9BTrgCg@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0YEm7mFYosRVbcG_XgtSi8BbUraGoixy4e2=nyCBeFaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
>If you start with the premise that more than half of Bitcoin miners would
do something crazy that would either destroy Bitcoin or would be completely
unacceptable to you, personally... then maybe you should look for some
other system that you might trust more, because Bitcoin's basic security
assumption is that a supermajority of miners are 'honest.'
Miners not being crazy does not mean they are infallible. They may
misjudge the market and change their minds about what is the most
reasonable action based on new information. Their commitment to one fork
or another is very dynamic, and is a huge assumption missing. They may
overestimate their influence, support of the economy. Other factors may
come into play that no one thought of, and they can revert back at any
point.
Labeling things as insane or crazy is not productive.
>because Bitcoin's basic security assumption is that a supermajority of
miners are 'honest.'
Only if you rely on SPV.
On Tue, Sep 29, 2015 at 12:35 PM, Gavin Andresen <gavinandresen@gmail•com>
wrote:
> On Tue, Sep 29, 2015 at 1:24 PM, Allen Piscitello <
> allen.piscitello@gmail•com> wrote:
>
>> I fail to see how always following a majority of miners no matter what
>> their actions somehow equates to insanity.
>
>
> Ok, I have a hidden assumption: I assume most miners are also not
> completely insane.
>
> I have met a fair number of them, and while they are often a little bit
> crazy (all entrepreneurs are a little bit crazy), I am confident that the
> vast majority of them are economically rational, and most of them are also
> meta-rational: they want Bitcoin to succeed. We've seen them demonstrate
> that meta-rationality when we've had accidental consensus forks.
>
> If you start with the premise that more than half of Bitcoin miners would
> do something crazy that would either destroy Bitcoin or would be completely
> unacceptable to you, personally... then maybe you should look for some
> other system that you might trust more, because Bitcoin's basic security
> assumption is that a supermajority of miners are 'honest.'
>
> --
> --
> Gavin Andresen
>
>
[-- Attachment #2: Type: text/html, Size: 3483 bytes --]
next prev parent reply other threads:[~2015-09-29 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 14:04 Gavin Andresen
2015-09-29 14:17 ` Jonathan Toomim (Toomim Bros)
2015-09-29 14:59 ` Mark Friedenbach
2015-09-29 17:24 ` Allen Piscitello
2015-09-29 17:35 ` Gavin Andresen
2015-09-29 17:43 ` Allen Piscitello [this message]
2015-09-29 17:51 ` Mike Hearn
2015-09-29 17:55 ` Allen Piscitello
2015-09-29 18:01 ` Gavin Andresen
2015-09-29 18:23 ` Allen Piscitello
2015-09-30 16:14 ` Jorge Timón
2015-09-29 18:02 ` Mike Hearn
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='CAJfRnm5=yrWE95T3+fzM_PxGxWJ38OnJMVxynTOKK1X9BTrgCg@mail.gmail.com' \
--to=allen.piscitello@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gavinandresen@gmail$(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