public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@hozed.org>
To: Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork
Date: Tue, 16 Jun 2015 22:52:42 -0500	[thread overview]
Message-ID: <20150617035242.GV27932@nl.grid.coop> (raw)
In-Reply-To: <CALqxMTGBt7MNs5YWf8QzKe+4Fr-uKVimf8=VbytBANEDm=s50g@mail.gmail.com>

> - How do you propose to deal with the extra risks that come from
> non-consensus hard-forks?  Hard-forks themselves are quite risky, but
> non-consensus ones are extremely dangerous for consensus.

This is a non-issue.

If the hard-fork is not a consensus, then those of us that don't consent
ignore the fool that tried to hard-fork.

If a fool attempting a non-consensus hard-fork actually breaks something,
then you have a fragile system that needs some serious re-thinking.

I think a non-consensus hard-fork would be the best thing that could 
happen to the bitcoin ecosystem long-term, because it would force some
re-examination of some very bad assumptions.

-- 
----------------------------------------------------------------------------
Troy Benjegerdes                 'da hozer'                  hozer@hozed.org
7 elements      earth::water::air::fire::mind::spirit::soul        grid.coop

      Never pick a fight with someone who buys ink by the barrel,
         nor try buy a hacker who makes money by the megahash




      parent reply	other threads:[~2015-06-17  3:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  0:04 [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Adam Back
2015-06-15  9:56 ` Mike Hearn
2015-06-15 18:03   ` Adam Back
2015-06-15 20:55     ` Mike Hearn
2015-06-15 21:56       ` Bryan Bishop
2015-06-15 22:17         ` Faiz Khan
2015-06-15 22:56           ` Brian Hoffman
2015-06-15 23:05             ` [Bitcoin-development] questions about bitcoin-XT code fork &non-consensus hard-fork Raystonn .
2015-06-16  0:08             ` [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Aaron Voisine
2015-06-16  0:41               ` Mark Friedenbach
2015-06-16  1:17               ` Alex Morcos
2015-06-16  4:00                 ` Aaron Voisine
2015-06-17  3:54                   ` Peter Todd
2015-06-18 15:23               ` Jorge Timón
2015-06-16 11:29           ` Mike Hearn
2015-06-16 11:20         ` Mike Hearn
2015-06-16 12:33     ` Pindar Wong
2015-06-16 13:33       ` Peter Todd
2015-06-16 13:55         ` Pindar Wong
2015-06-17  3:59           ` Peter Todd
2015-06-25  6:43             ` [bitcoin-dev] " Pindar Wong
2015-06-26 19:30               ` Peter Todd
2015-06-15 22:54   ` odinn
2015-06-16  1:20     ` Eric Lombrozo
2015-06-16  5:18   ` Venzen
2015-06-16  6:09     ` Marcel Jamin
2015-06-16  9:21       ` Benjamin
2015-06-16 11:01     ` Tier Nolan
2015-06-17  3:52 ` Troy Benjegerdes [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=20150617035242.GV27932@nl.grid.coop \
    --to=hozer@hozed.org \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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