From: Adam Back <adam@cypherspace•org>
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: Thu, 7 May 2015 19:16:12 -0700 [thread overview]
Message-ID: <CALqxMTGNc1NrXNBE8kbSs9t2bfWi=i4MpyKpvPvSmSyjHseRvA@mail.gmail.com> (raw)
In-Reply-To: <20150507220848.GK63100@giles.gnomon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 4116 bytes --]
Well this is all very extreme circumstances, and you'd have to assume no
rational player with an interest in bitcoin would go there, but to play
your analysis forward: users are also not powerless at the extreme: they
could change the hash function rendering current deployed ASICs useless in
reaction for example, and reset difficulty at the same time, or freeze
transactions until some minimum hashrate is reached. People would figure
out what is the least bad way forward.
Adam
On May 7, 2015 3:09 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.
>
> >
> > A hardfork is safe when 100% of (economically relevant) users upgrade. If
> > miners don't upgrade at that point, they just lose money.
> >
> > This is why a hashrate-triggered hardfork does not make sense. Either you
> > believe everyone will upgrade anyway, and the hashrate doesn't matter. Or
> > you are not certain, and the fork is risky, independent of what hashrate
> > upgrades.
>
> Beliefs are all very well, but they can be wrong. Of course we should
> not go ahead with a fork that we believe to be dangerous, but
> requiring a supermajority of miners is surely a wise precaution. I
> fail to see any realistic scenario where 99% of miners vote for the
> hard fork to go ahead, and the econonomic majority votes to stay on
> the blockchain whose hashrate has just dropped two orders of magnitude
> - so low that the mean time between blocks is now over 16 hours.
>
> >
> > And the march 2013 fork showed that miners upgrade at a different
> schedule
> > than the rest of the network.
> > On May 7, 2015 5:44 PM, "Roy Badami" <roy@gnomon•org.uk> wrote:
> >
> > >
> > > > On the other hand, if 99.99% of the miners updated and only 75% of
> > > > merchants and 75% of users updated, then that would be a serioud
> split of
> > > > the network.
> > >
> > > But is that a plausible scenario? Certainly *if* the concensus rules
> > > required a 99% supermajority of miners for the hard fork to go ahead,
> > > then there would be absoltely no rational reason for merchants and
> > > users to refuse to upgrade, even if they don't support the changes
> > > introduces by the hard fork. Their only choice, if the fork succeeds,
> > > is between the active chain and the one that is effectively stalled -
> > > and, of course, they can make that choice ahead of time.
> > >
> > > roy
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > One dashboard for servers and applications across
> Physical-Virtual-Cloud
> > > Widest out-of-the-box monitoring support with 50+ applications
> > > Performance metrics, stats and reports that give you Actionable
> Insights
> > > Deep dive visibility with transaction tracing using APM Insight.
> > > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> > > _______________________________________________
> > > Bitcoin-development mailing list
> > > Bitcoin-development@lists•sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> > >
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 5358 bytes --]
next prev parent reply other threads:[~2015-05-08 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 20:00 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 [this message]
2015-05-08 2:35 ` Pieter Wuille
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='CALqxMTGNc1NrXNBE8kbSs9t2bfWi=i4MpyKpvPvSmSyjHseRvA@mail.gmail.com' \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=roy@gnomon$(echo .)org.uk \
/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