but say you have 10 block erupters going at 3.333Ghz in 1 CGminer client. Do i tell my slush worker account that I have a 3Ghz miner so i get higher difficulty or will my 10 erupters choke individually on higher difficulty shares ? Same question regarding a Blade, should it run at difficulty 8 or just 1 since its all little workers linked together ?

but say you have 10 block erupters going at 3.333Ghz in 1 CGminer client. Do i tell my slush worker account that I have a 3Ghz miner so i get higher difficulty or will my 10 erupters choke individually on higher difficulty shares ? Same question regarding a Blade, should it run at difficulty 8 or just 1 since its all little workers linked together ?

Thanks

One 3 GH/s miner oder ten with 0,3 GH/s is no difference.No miner will choke on anything, they always do exactly the same work, no matter how you set your worker diff.

Only thing happening is with higher diff, cgminer will send less shares to the pool server (cause all calculated hashes with diff lower than what you did set get dropped), and your shares will get you more score. So, set the diff higher for less network load but higher variance.

One 3 GH/s miner oder ten with 0,3 GH/s is no difference.No miner will choke on anything, they always do exactly the same work, no matter how you set your worker diff.

Only thing happening is with higher diff, cgminer will send less shares to the pool server (cause all calculated hashes with diff lower than what you did set get dropped), and your shares will get you more score. So, set the diff higher for less network load but higher variance.

What happened is: We found a block nearly at the same time as someone else, and they were lucky enough to have the next block found based upon their block instead of ours.So our blocks are orphaned (not part of the main chain) and thus invalid.Its bad luck, but happens from time to time, because the info that some block was found does not appear at instant speed at all nodes.The time needed for the block to propagate through the network leaves a small time window for another block with same block # to be found.

I know what orphaned blocks are, but when I used to mine at Slush, they were very, very rare - you'd hardly see one per month. They seem to be a lot more common here on Slush these days - sometimes multiples in the same day... Has Slush not updated his Bitcoind nodes?

I know what invalid blocks are, but when I used to mine at Slush, they were very, very rare - you'd hardly see one per month. They seem to be a lot more common here on Slush these days - sometimes multiples in the same day...

Well, besides bad luck and the usual variance, the probability for an orphaned block is higher if the average rate to find blocks for the whole network is higher. Maybe the rise in total network hash-rate wasnt that high back then? Could be a combination of slightly higher average orphan rate plus a little bad luck which makes it appear as if this happens way more often atm

wouldn't it stand to reason that when the hashrate goes up rapidly that the orphan rate would too. Maybe this is a horse race and the pools are neck & neck. Slush'e luck is good right now so it is time for people to move to other pools and trash our luck.

*singing* The luck goes up, the luck goes down, and the toilet water goes round and Round.

What happened is: We found a block nearly at the same time as someone else, and they were lucky enough to have the next block found based upon their block instead of ours.So our blocks are orphaned (not part of the main chain) and thus invalid.Its bad luck, but happens from time to time, because the info that some block was found does not appear at instant speed at all nodes.The time needed for the block to propagate through the network leaves a small time window for another block with same block # to be found.

Then the 6 blocks after I get none. All the while, my cockroaches are silently churning hashes. I restarted the nest and things appear to be working okay now.

Any ideas what would cause that?

you probably went on backup pool at the end of the block, and since slush is using score system the last shares of the block has more value than thge prev. for example if you are hashing 2 hours but missed the last 12minutes from that block - this would happen

Then the 6 blocks after I get none. All the while, my cockroaches are silently churning hashes. I restarted the nest and things appear to be working okay now.

Any ideas what would cause that?

you probably went on backup pool at the end of the block, and since slush is using score system the last shares of the block has more value than thge prev. for example if you are hashing 2 hours but missed the last 12minutes from that block - this would happen

How on earth would that happen? For all intents and purposes I missed out on 7 full blocks while I was away. No power outage. No ISP interuptions. It gave me not.