Re: [450 TH] Slush's Pool (mining.bitcoin.cz); TX FEES + VarDiff
Hi ya all,
It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.
Salute all Slusher's.
It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.
Salute all Slusher's.
It's not a hardware issue on Slush's end. During long rounds, many people will hop to other pools. You'll see a drop in hashing power which means that there's less chance to find a block compounding the problem. Also, the hash rate is fluid meaning it can vary even if no miners came or went. Hardware errors, vardiff, etc. play a factor in determining the hash rate the pool recognizes.
Sorry, but, answering to your assumption about "factors". I am a systems engineer certified in a lot of technologies (and updated my certs) and what your are talking and assuming is "Coincidence". Which with time and experience your know that coincidence does not exist anymore talking about computering. It is like talking about "magic, or how the small men inside the server trick you", and yes sure you can "fix up a server hitting it enough times with your hand".
People, please. Think.
EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.
PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"
What about the other one hundred questions?