Quote from: keystroke on April 30, 2013, 03:00:34 AM

Check out this latest change to 0.8.2:
https://github.com/bitcoin/bitcoin/pull/2577

This pull defines 'uneconomic dust' as 54.3 uBTC (5430 satoshis, about $0.007 at current prices), and treats any transaction with outputs less than 5430 satoshis as non-standard (won't be relayed, won't be mined). 5430 satoshis is derived from the cost (in fees) to spend a TxOut/TxIn. See https://people.xiph.org/~greg/txouts2.png for proportion of recent outputs this will (eventually) affect.

Will this make the initial Satoshis sent on dividends no longer relay/get mined?

I believe this only means that the border where one has to pay a minimum fee was set down from 0.01 to 0.00005430. Im not sure about this, but it sounds this way.

Quote from: organofcorti on April 30, 2013, 09:16:59 AM

Variance will only remain a non-issue if they keep adding hashrate so that they remain at a constant proportion (or increased proportion) of the network. As soon as the their proportion decreases, variance will increase.

But will it matter? You have the chance to earn more or less in a week, but mostly its an average. Because it is more or less you wont lose anything in the long run. Of course you can earn less in the first week and more in the next week when the difficulty raised but it can be the opposite way too, so i dont see that this is a big problem.

What i wonder is if this ip is attackable then. It would be good to have some more ips to chose from or a pool to switch too in case of an attack.

The transparency isnt a problem for me too because we have to trust friedcat and co anyway. We would not be able to see if they throw some hashpower to another pool or solo mine. The numbers shown at a pool are in no way safer than solomining. And if its about the general hashingpower... i wonder if it would be hard to make a website that is showing the complete asicminer-datacenter-hashrate. I mean in the datacentre theres probably a software that has a overview about all the blades to see if one is failing. So this software probably has the hashrates too. It wouldnt be a border to implement this into a website then.

Only saying...