Post
Topic
Board Pools
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
by
Lucko
on 29/05/2013, 20:16:51 UTC
So if Slush can't find a way to fix his pool even when he knows it has issues

Have you ever tried to find someone to take care for something very specific, which only you know? Guess what it take longer than for yourself to fix it. If he can't trust his (ex) hosting provider (OVH) how do you expect he can give to someone all the passwords/keys and etc for the pool?

Pool was working on the wrong block for x amount of time for y blocks. Block could be found in x*y amount of time... So in one case it is 100% loss in other could be anywhere from 0% to infinity(but probably average out to 100% long term)...

And this will always be the case for each and every pool ... and once again:

18264   2013-05-28 17:55:43   238386

and from blockchain:

Height   238386 (Main Chain)
Received Time   2013-05-28 17:55:41

We have found it 3 seconds later, but didn't know ... our x time is 3sec and for each and every block and for each and every pool or host on the network there is such time. I would agree if x is 1 minute or so, but come on 3 sec is nothing
Well that is bad planing... You have to have a backup plan... Or find one asap or 30 days. It is 1300$ per day he is not monitoring... For that money I would have a plan what to do in case that I would have to be with my parents that are on death bed. But then again I would also have time to look at my 1300$ moneymaker... So I really have no idea what Slush problems can be that he can't do anything... He was always able to fix it and protect his pool.

Invalids again? OK last time we figure it out when someone posted that data that blockchan info and timestemp doesn't help anything so don't use them as an example... Blockchan receive time can be up to 2 minutes wrong. Look at stratum detected new block in cgminer... Blockchan is not pool. It doesn't need to be updated ASAP... So x can be up to 2 minutes and 3 seconds... And if it would be just one I wouldn't care but there were 2. So just saying everything is fine nothing to see when others pools admins are upgrading there systems to 0.8.2 to remove invalid problem is stupid. But since only Slush can do that it is also pointless to explain what needs to be done to someone who is determent that everything is fine... Even when there are posts from Slush saying yes there is a problem... This is one and as far as I know was not solved since I did see this problem in a log about 4 days ago(look back, I have posted logs since I was told that this can't be). But do fell free to think otherwise.

Also when you are sure that this is fixed can you then please look at the stratums. I think there is also something wrong with them.

I'm experiencing performance problems with some EC2 instances and I'm solving this as well. Sometimes I need to restart pool software on EC2, which causes miners hoping to another IP from DNS roundrobin.