I propose a setting that prevent mining pools AND reduce payoff variance
which requires two changes: increasing the block-rate and changing the
Bitcoin PoW (but still allowing current Bitcoin ASICs to work (as far as
I know)). The block rate must be increased at least 20 times and block
must still
On 6/19/2014 12:58 PM, Sergio Lerner wrote:
I propose a setting that prevent mining pools AND reduce payoff
variance which requires two changes: increasing the block-rate and
changing the Bitcoin PoW (but still allowing current Bitcoin ASICs to
work (as far as I know)). The block rate must
Sergio, why is preventing mining pools a good thing? The issue is not
mining pools, which provide a needed service in greatly reducing
variance beyond what any proposal like this can do.
The issue is centralized transaction selection policies, which is
entirely orthogonal. And the solution
The issue is centralized transaction selection policies, which is
entirely orthogonal. And the solution already exists: getblocktemplate.
My (fresh!) understanding is that the reason we don't see people using
getblocktemplate to decentralise pools is because libblkmaker and other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/19/2014 05:11 PM, Kevin wrote:
Why do you want to punish pools?
It's part of a general trend wherein people look at all the things
that can be accomplished in an economy that has a division of labor*,
and see some misbehavior at the edges, and
Do you need to do full validation? There's an economic cost to mining
invalid blocks, and even if that were acceptable there's really no
reason to perform such an attack. The result would be similar to a block
withholding attack, but unlike block withholding it would be trivially
detectable
On Thu, Jun 19, 2014 at 7:35 PM, Mike Hearn m...@plan99.net wrote:
My (fresh!) understanding is that the reason we don't see people using
getblocktemplate to decentralise pools is because libblkmaker and other
implementations don't actually support connecting your own node to the
miners and
Miner issues are just one thing what came to my mind. What about validating
transactions? How the pool can be sure that miner is running up to date
bitcoind which do full validation of transactions? Not talking that if
every miner takes his own set of transaction, pool need to calculate merkle
8 matches
Mail list logo
