From: Randi Joseph <randi@codehalo•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] ASIC-proof mining
Date: Fri, 04 Jul 2014 16:55:04 -0400 [thread overview]
Message-ID: <53B714A8.1080603@codehalo.com> (raw)
In-Reply-To: <CAC1+kJOSAoz_BBaFnv4u-Dng7Y4h2tqOHSFRfuKvY87eBR71Gw@mail.gmail.com>
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
next prev parent reply other threads:[~2014-07-04 20:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 10:27 Andy Parkins
2014-07-04 10:53 ` Alan Reiner
2014-07-04 11:08 ` Eugen Leitl
2014-07-04 11:15 ` Andy Parkins
2014-07-04 11:22 ` Alan Reiner
2014-07-04 11:28 ` Andy Parkins
2014-07-04 11:37 ` Gregory Maxwell
2014-07-04 12:01 ` Andy Parkins
2014-07-04 15:20 ` Mike Hearn
2014-07-04 16:50 ` kjj
2014-07-04 18:39 ` Ron Elliott
2014-07-04 19:54 ` Aaron Voisine
2014-07-04 20:21 ` Jorge Timón
2014-07-04 20:38 ` Luke Dashjr
2014-07-04 20:55 ` Randi Joseph [this message]
2014-07-05 8:43 ` Mike Hearn
2014-07-07 0:20 ` Randi Joseph
2014-07-07 6:12 ` Odinn Cyberguerrilla
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=53B714A8.1080603@codehalo.com \
--to=randi@codehalo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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