user1171: An unknown major solo miner (currently IP 71.123.170.150), most likely a botnet, is relaying blocks with zero transactions. Two weeks ago this miner constituted ~15% of the network, now it constitutes ~30%. If the growth rate continues, in about two weeks this miner (most likely a botnet) will control more than half of the network, theoretically allowing a 51% attack. It has already orphaned two perfectly valid blocks. (Thread on BitcoinTalk) 
It seems to me we have an imminent threat to Bitcoin itself. Requiring transactions to be included in a block won't work; the miner can just send coins to itself. Blacklisting IPs in the client won't work; the miner can easily switch IPs. How can we stop this? 

user1218: As the mystery miner continues to grow prior to 51%, it will only delay legitimate transactions. Economic factors should limit profitability of zero transaction blocks, as the value of a bitcoin would decline when usage of the network becomes hampered enough to become a deterrent rather than an incentive.
As the exchange value of a bitcoin falls, it wouldn't make sense to commit resources to mining in the first place. Going the other way, a rise in bitcoin prices would encourage network expansion - including mining. That would increase the 51% mark, making it more difficult for the mystery miner to attain the majority.
Also, if the miner is a botnet, ASIC/FPGA mining should make it a transient threat. Halving of the block reward within the next several months will cut profitability of zero transaction mining as well. This is assuming the 51% level is not achieved, allowing economic forces to remain the primary means of limiting this miner.

user323: As the miner is obeying the protocol rules, one can't do much without altering the protocol. You could require the client to reject blocks that don't include some transactions that should be in the blocks, limit mining only to people with some accepted keys to sign a transaction or the like, but in the end this would probably not solve the problem.
If it was later in Bitcoin maturity, it wouldn't be much of an issue - block rewards will be coming mainly from transactions, so someone rejecting all transactions wouldn't be earning much. If this was an attempt at destroying the Bitcoin network, however, it would still be a problem.
What the Bitcoin community can do is get more mining power into the network, for example by raising the price of Bitcoins so they would be more profitable. You could also contact the owner of that IP address (since it links to a web page if typed in the address bar) for explanations.

user575: There are too many issues rolled up into this question, I'll try to address each separately.

The fact that the miner does not include transactions is not a problem. Miners have a right to exclude transactions, even all transactions. Senders can include tx fees if they want to improve the chances of being included quickly (if the miner excludes transactions due to its nature of operation an individual fee won't help much, but if the general fee level increases, 0-tx miners will be much less profitable and thus less influential).
The fact that there is a mining botnet is a problem insomuch as we don't want Bitcoin to be an enabler of harmful activities, but it does not harm Bitcoin itself. It is likely that new FPGA- and ASIC-based mining products will make CPU-based botnets less effective.
Orphaned blocks are a normal occurrence in the functioning of the network, and an occasional orphan by this particular miner is of no concern.
If the miner starts rejecting longer branches (as in a 51% attack) it is a problem, but it is a heavily discussed core problem which is not specific to botnets and is not yet resolved. I am of the opinion that a proof-of-stake system can drastically mitigate the problem (and will probably make botnets less effective miners).
If we want as a matter of principle to discourage blocks that have little or no transactions, we can include some measure of transaction volume in the branch selection criterion. One such measure is Bitcoin days destroyed. It is resistant to manipulation by sending the same coins to oneself again and again, because such coins will only destroy few days each time.


1171: <p>An unknown major solo miner (currently IP 71.123.170.150), most likely a botnet, is relaying blocks with zero transactions. Two weeks ago this miner constituted ~15% of the network, now it constitutes ~30%. If the growth rate continues, in about two weeks this miner (most likely a botnet) will control more than half of the network, theoretically allowing a 51% attack. It has already orphaned two perfectly valid blocks. (<a href="https://bitcointalk.org/index.php?topic=67634.msg828756#msg828756">Thread on BitcoinTalk</a>) </p>

<p>It seems to me we have an imminent threat to Bitcoin itself. Requiring transactions to be included in a block won't work; the miner can just send coins to itself. Blacklisting IPs in the client won't work; the miner can easily switch IPs. How can we stop this? </p>
 1218: <p>As the mystery miner continues to grow prior to 51%, it will only delay legitimate transactions. Economic factors should limit profitability of zero transaction blocks, as the value of a bitcoin would decline when usage of the network becomes hampered enough to become a deterrent rather than an incentive.</p>

<p>As the exchange value of a bitcoin falls, it wouldn't make sense to commit resources to mining in the first place. Going the other way, a rise in bitcoin prices would encourage network expansion - including mining. That would increase the 51% mark, making it more difficult for the mystery miner to attain the majority.</p>

<p>Also, if the miner is a botnet, ASIC/FPGA mining should make it a transient threat. Halving of the block reward within the next several months will cut profitability of zero transaction mining as well. This is assuming the 51% level is not achieved, allowing economic forces to remain the primary means of limiting this miner.</p>
 323: <p>As the miner is obeying the protocol rules, one can't do much without altering the protocol. You could require the client to reject blocks that don't include some transactions that should be in the blocks, limit mining only to people with some accepted keys to sign a transaction or the like, but in the end this would probably not solve the problem.</p>

<p>If it was later in Bitcoin maturity, it wouldn't be much of an issue - block rewards will be coming mainly from transactions, so someone rejecting all transactions wouldn't be earning much. If this was an attempt at destroying the Bitcoin network, however, it would still be a problem.</p>

<p>What the Bitcoin community can do is get more mining power into the network, for example by raising the price of Bitcoins so they would be more profitable. You could also contact the owner of that IP address (since it links to a web page if typed in the address bar) for explanations.</p>
 575: <p>There are too many issues rolled up into this question, I'll try to address each separately.</p>

<ol>
<li><p>The fact that the miner does not include transactions is not a problem. Miners have a right to exclude transactions, even all transactions. Senders can include tx fees if they want to improve the chances of being included quickly (if the miner excludes transactions due to its nature of operation an individual fee won't help much, but if the general fee level increases, 0-tx miners will be much less profitable and thus less influential).</p></li>
<li><p>The fact that there is a mining botnet is a problem insomuch as we don't want Bitcoin to be an enabler of harmful activities, but it does not harm Bitcoin itself. It is likely that new FPGA- and ASIC-based mining products will make CPU-based botnets less effective.</p></li>
<li><p>Orphaned blocks are a normal occurrence in the functioning of the network, and an occasional orphan by this particular miner is of no concern.</p></li>
<li><p>If the miner starts rejecting longer branches (as in a 51% attack) it is a problem, but it is a heavily discussed core problem which is not specific to botnets and is not yet resolved. I am of the opinion that a <a href="https://en.bitcoin.it/wiki/Proof_of_Stake">proof-of-stake</a> system can drastically mitigate the problem (and will probably make botnets less effective miners).</p></li>
<li><p>If we want as a matter of principle to discourage blocks that have little or no transactions, we can include some measure of transaction volume in the branch selection criterion. One such measure is <a href="https://en.bitcoin.it/wiki/Bitcoin_Days_Destroyed">Bitcoin days destroyed</a>. It is resistant to manipulation by sending the same coins to oneself again and again, because such coins will only destroy few days each time.</p></li>
</ol>
