<p dir="ltr">But miners dont want to run full nodes, its better to develop some SPV like that connects to some nodes.</p>
<p dir="ltr">Also I believe that stratum mining protocol improves some performance things that GBT lacks.</p>
<p dir="ltr">If a new protocol that requires blocks created by miners is developed and named in a cool way, miners could ask for protocol support to his favourite pool.</p>
<div class="gmail_quote">El 17/06/2014 20:26, "Karel Bílek" <<a href="mailto:kb@karelbilek.com">kb@karelbilek.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Jun 17, 2014 at 4:20 PM, Christophe Biocca<br>
<<a href="mailto:christophe.biocca@gmail.com">christophe.biocca@gmail.com</a>> wrote:<br>
> <a href="https://en.bitcoin.it/wiki/Getblocktemplate" target="_blank">https://en.bitcoin.it/wiki/Getblocktemplate</a> is supposed to solve most<br>
> of the pooling-centralization problems.<br>
<br>
This. There is no need to create anything new when GBT already exists.<br>
In my opinion.<br>
<br>
> Unfortunately, it is opt-in,<br>
> and GHash.io doesn't support it.<br>
<br>
Yep. As pools in general are not a part of the bitcoin protocol itself<br>
(nobody cares how the work happened), I am not sure how this can be<br>
forced.<br>
<br>
> Also most miners don't care and don't do the work to set it up. To do<br>
> transaction inclusion themselves, they'd need to run a full node,<br>
> which is a bit more work and resources than just pointing hashpower at<br>
> a stratum server.<br>
<br>
Also, yep. If the miners cared about 51% attack, they wouldn't join<br>
ghash in the first place. All the miners willingly accept the risk in<br>
joining the big pool.<br>
<br>
K. B.<br>
<br>
> If you figure out a way to make GBT widely used (>50% hashpower), kudos to you.<br>
><br>
> On Tue, Jun 17, 2014 at 4:57 AM, Raúl Martínez <<a href="mailto:rme@i-rme.es">rme@i-rme.es</a>> wrote:<br>
>> First of all I apologice due to the possible mistakes in my writing below, I<br>
>> am not a Bitcoin developer but I have some knowledge about it.<br>
>><br>
>> ----<br>
>><br>
>> We all know the recent news, Ghash pool controlling 51% of the hashrate.<br>
>> While some consider it a threat others think that is not harmful.<br>
>><br>
>> The thing is that we have to do something to stop this from happening again.<br>
>><br>
>> My proposal is to start thinking about miners that join a pool like<br>
>> independent miners and not slave miners, this includes creating a new mining<br>
>> protocol that does not rely on the pool sending the list of transactions to<br>
>> include in a block. Each individual miner has to collect transactions by his<br>
>> own and mine that, this can be achieved by running a full node or by running<br>
>> a SPV like node that ask other nodes for transactions.<br>
>><br>
>> Once this protocol is developed and standarised we as a community could<br>
>> require all pools to use it (because its better, because is more<br>
>> trustless...), not by imposing it but by recommending it.<br>
>><br>
>> Pool owners could send some instructions using this protocol to the miner<br>
>> about how many transactions to include per block (some pools want small<br>
>> blocks), how many 0 fee transactions to include, how much is the minimum fee<br>
>> per Kb to include transactions and some info about the Coinbase field in the<br>
>> block.<br>
>><br>
>> This way is impossible to perform some of the possible 51% attacks:<br>
>><br>
>> A pool owner cant mine a new chain (selfish mining) (pool clients have a SPV<br>
>> or full node that has checkpoints and ask other peers about the length of<br>
>> the chain)<br>
>> A pool owner can't perform double spends or reverse transactions (pool<br>
>> clients know all the transactions relayed to the network, they know if they<br>
>> are already included on a block)<br>
>> A pool owner cant decide which transactions not to include (but they can<br>
>> configure the minimum fee).<br>
>> A pool owner cant get all the rewards by avoiding other pools from mining<br>
>> blocks (Because the pool client knows the last block independently that is<br>
>> from his pool or other).<br>
>><br>
>><br>
>> The only thing that a 51% pool owner can do is to shut down his pool and<br>
>> drop the hashrate by 51% because he does not control the miners.<br>
>><br>
>> If the pool owner owns all the hardware in the pool my proposal is not<br>
>> valid, if the pool clients dont use this protocol my proposal is not valid.<br>
>><br>
>><br>
>> I want to know if this is possible or its been developed or there is already<br>
>> a working protocol that works like this, also I want to read other people's<br>
>> ways to address this threat, thanks for reading.<br>
>><br>
>> ------------------------------------------------------------------------------<br>
>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions<br>
>> Find What Matters Most in Your Big Data with HPCC Systems<br>
>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.<br>
>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration<br>
>> <a href="http://p.sf.net/sfu/hpccsystems" target="_blank">http://p.sf.net/sfu/hpccsystems</a><br>
>> _______________________________________________<br>
>> Bitcoin-development mailing list<br>
>> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
>> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
>><br>
><br>
> ------------------------------------------------------------------------------<br>
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions<br>
> Find What Matters Most in Your Big Data with HPCC Systems<br>
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.<br>
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration<br>
> <a href="http://p.sf.net/sfu/hpccsystems" target="_blank">http://p.sf.net/sfu/hpccsystems</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</blockquote></div>