From: Nathan Cook <nathan.cook@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
Date: Tue, 2 Jun 2015 14:43:29 +0300 [thread overview]
Message-ID: <CAGNXQMR-Huhjai-hKvu_4jgTLzdmXqmNCz0U-wyn3hoM_NmN_Q@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3W97oqqHLMu2i3y6ogp5YPCJ_vhNHTcQ9zN8f4mLGqAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On 2 June 2015 at 14:26, Mike Hearn <mike@plan99•net> wrote:
> But the majority of the hashrate can now perform double spends on your
>> chain! They can send bitcoins to exchanges, sell it, extract the money and
>> build a new longer chain to get their bitcoins back.
>>
> Obviously if the majority of the mining hash rate is doing double spending
> attacks on exchanges then the Bitcoin experiment is resolved as a failure
> and it will become abandoned. This has been known since day one: it's in
> the white paper. The basic assumption behind Bitcoin is that only a
> minority of actors are dishonest - if the majority are then Satoshi's
> scheme does not work.
>
> So you are not stating anything new here.
>
It's both consistent and credible for an agent to commit to honesty on a
chain that it openly supports and dishonesty on a chain that it openly
opposes. (Moral? Legal? Perhaps not.) That said, majority hashpower doesn't
need to be dishonest to stop a change to large blocks. It just needs to
refuse to build on blocks that it doesn't like. The minority isn't going to
mine blocks larger than 1MB if it knows they'll be orphaned.
[-- Attachment #2: Type: text/html, Size: 2225 bytes --]
prev parent reply other threads:[~2015-06-02 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 11:19 cipher anthem
2015-06-02 11:26 ` Mike Hearn
2015-06-02 11:43 ` Nathan Cook [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=CAGNXQMR-Huhjai-hKvu_4jgTLzdmXqmNCz0U-wyn3hoM_NmN_Q@mail.gmail.com \
--to=nathan.cook@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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