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 1WScLC-00063A-K6 for bitcoin-development@lists.sourceforge.net; Wed, 26 Mar 2014 01:09:14 +0000 X-ACL-Warn: Received: from serv.jerviss.org ([12.47.47.47] helo=inana.jerviss.org) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WScLB-0006Zz-KQ for bitcoin-development@lists.sourceforge.net; Wed, 26 Mar 2014 01:09:14 +0000 Received: from [10.8.2.254] ([192.151.168.151]) (username: kjj authenticated by PLAIN symmetric_key_bits=0) by inana.jerviss.org (8.13.6/8.12.11) with ESMTP id s2Q192rP014270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Mar 2014 20:09:06 -0500 Message-ID: <533228AD.6090909@jerviss.org> Date: Tue, 25 Mar 2014 20:09:01 -0500 From: kjj User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:28.0) Gecko/20100101 SeaMonkey/2.25 MIME-Version: 1.0 To: Mark Friedenbach References: <20140322084702.GA13436@savin> <20140322193435.GC6047@savin> <20140323231737.GM3180@nl.grid.coop> <532F740C.9010800@monetize.io> <20140324203403.GR3180@nl.grid.coop> <53309C2A.4040406@monetize.io> <20140325221054.GA3180@nl.grid.coop> In-Reply-To: <20140325221054.GA3180@nl.grid.coop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (inana.jerviss.org: 192.151.168.151 is authenticated by a trusted mechanism) X-Spam-Score: -1.9 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WScLB-0006Zz-KQ Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Handling miner adoption gracefully for embedded consensus systems via double-spending/replace-by-fee 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, 26 Mar 2014 01:09:14 -0000 Troy Benjegerdes wrote: > Mark Friedenbach wrote: >> Bitcoin is not a centralized system, and neither is its development. I >> don't even know how to respond to that. Bringing up altchains is a total >> red herring. >> >> This is *bitcoin*-development. Please don't make it have to become a >> moderated mailing list. > When I can pick up a miner at Best Buy and pay it off in 9 months I'll > agree with you that bitcoin *might* be decentralized. Maybe there's a > chance this *will* happen eventually, but right now we have a couple of > mining cartels that control most of the hashrate. > > There are plenty of interesting alt-hash-chains for which mass produced, > general purpose (or gpgpu-purpose) hardware exists and is in high volume > mass production. Decentralized doesn't mean "everyone is doing it", it means "no one can stop you from doing it". Observe bitcoin development. A few people do the bulk of the work, a bunch more people (like me) do work ranging from minor to trivial, and millions do nothing. And yet, it is still totally decentralized because no one can stop anyone from making whatever changes they want. So it is also with mining. The world overall may make it impractical, perhaps even foolish, for you to fire up your CPU and mine solo, but no one is stopping you, and more to the point, no one is capable of stopping you. There is no center from which you must ask permission. On moderation, I note that moderation can also be done in a decentralized fashion. I offer this long overdue example: :0 * ^From.*hozer@hozed.org /dev/null