public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Roy Badami <roy@gnomon.org.uk>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mechanics of a hard fork
Date: Fri, 8 May 2015 04:35:00 +0200	[thread overview]
Message-ID: <CAPg+sBg4+Hj9z6NfHMyqv=PPKpYxCGP-5RcxJFfocfUajgYGxA@mail.gmail.com> (raw)
In-Reply-To: <20150507220848.GK63100@giles.gnomon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

On May 7, 2015 3:08 PM, "Roy Badami" <roy@gnomon.org.uk> wrote:
>
> On Thu, May 07, 2015 at 11:49:28PM +0200, Pieter Wuille wrote:
> > I would not modify my node if the change introduced a perpetual 100 BTC
> > subsidy per block, even if 99% of miners went along with it.
>
> Surely, in that scenario Bitcoin is dead.  If the fork you prefer has
> only 1% of the hash power it is trivially vulnerably not just to a 51%
> attack but to a 501% attack, not to mention the fact that you'd only
> be getting one block every 16 hours.

Yes, indeed, Bitcoin would be dead if this actually happens. But that is
still where the power lies: before anyone (miners or others) would think
about trying such a change, they would need to convince people and be sure
they will effectively modify their code.

-- 
Pieter

[-- Attachment #2: Type: text/html, Size: 1010 bytes --]

  parent reply	other threads:[~2015-05-08  2:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 20:00 [Bitcoin-development] Mechanics of a hard fork Roy Badami
2015-05-07 21:24 ` Tier Nolan
2015-05-07 21:42   ` Roy Badami
2015-05-07 21:49     ` Pieter Wuille
2015-05-07 22:08       ` Roy Badami
2015-05-08  2:16         ` Adam Back
2015-05-08  2:35         ` Pieter Wuille [this message]
2015-05-08  3:12           ` Cameron Garnham

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='CAPg+sBg4+Hj9z6NfHMyqv=PPKpYxCGP-5RcxJFfocfUajgYGxA@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=roy@gnomon.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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