Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X3AVk-0000DY-Lf for bitcoin-development@lists.sourceforge.net; Fri, 04 Jul 2014 20:55:12 +0000 X-ACL-Warn: Received: from smtp156.dfw.emailsrvr.com ([67.192.241.156]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1X3AVi-0004kQ-MF for bitcoin-development@lists.sourceforge.net; Fri, 04 Jul 2014 20:55:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp12.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 404C58039F for ; Fri, 4 Jul 2014 16:55:05 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp12.relay.dfw1a.emailsrvr.com (Authenticated sender: randi-AT-codehalo.com) with ESMTPSA id 081028039E for ; Fri, 4 Jul 2014 16:55:04 -0400 (EDT) Message-ID: <53B714A8.1080603@codehalo.com> Date: Fri, 04 Jul 2014 16:55:04 -0400 From: Randi Joseph User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <10566815.3CllqoMfON@momentum> <53B6DB38.7010709@jerviss.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1X3AVi-0004kQ-MF Subject: Re: [Bitcoin-development] ASIC-proof mining 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: Fri, 04 Jul 2014 20:55:12 -0000 Hi All, This is a bit tangential to the conversation, but since the genesis of this conversation is Mike's decentralization blog post, I decided to post here. Perhaps the solution to the mining problem lies in the reward structure rather than in the proof of work/asics. Is it possible instead to allocate a portion of the reward to " a # of runner up(s)" even though the runner-up(s) block will be orphaned? For example, X% of the block reward goes to Y number of runner-ups based on some type of criteria? This will appear to be a bit like a tax on the winner, but it could potentially solve the problem, since a large pool would not want to split the pool up to solve multiple blocks. There are some possible downsides, like probably having to keep those orphaned blocks around in the future, etc. If this is possible, the question that remains then, what would be the criteria for the X% payout/allocation? -Randi