Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z54RG-0003BZ-Mr for bitcoin-development@lists.sourceforge.net; Wed, 17 Jun 2015 03:54:58 +0000 X-ACL-Warn: Received: from nl.grid.coop ([50.7.166.116]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Z54RF-0008Pr-E9 for bitcoin-development@lists.sourceforge.net; Wed, 17 Jun 2015 03:54:58 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by nl.grid.coop with local; Tue, 16 Jun 2015 22:52:42 -0500 id 00000000000613CD.000000005580EF0A.00003521 Date: Tue, 16 Jun 2015 22:52:42 -0500 From: Troy Benjegerdes To: Adam Back Message-ID: <20150617035242.GV27932@nl.grid.coop> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Z54RF-0008Pr-E9 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 03:54:58 -0000 > - 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