Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1096. (Read 4382648 times)

thus the .cz tld, right?

I thought Slush's server was in the UK.

Tried the gui front end from another thread, which keeps stats on invalid/stale.  Turns out that either I overestimated the amount of stale blocks before or something was fixed.  Just FYI I got 16,941 accepted and 222 invalid/stale over time which is only about a 1.3% loss, so a liveable number.  Also, between the two mining pools I'm in, the one other than Slush's is a 3% commission rather than Slush's 2%.  So really I am only at a loss of 1/3 of one percent as a result of this problem which, as I've said before, may be on my end or somewhere between me and Slush's server ( in the Czech republic).

Just for the record, I am happy with Slush's service and he's never been anything other than completely honest.  An important fact when shopping around for a mining pool.  I am only temporarily supporting other mining pools as well because I think it it to everyone's benefit to have the ability to shop around and I just wanted to help support others get started.

Just use separate address...

How do you see your total balance you received from the pool?

I see that one pool instance underperform a bit, which may also explain problems of ronaldmaustin reported few hours before. I'll try to fix it tomorrow, but I'm busy right now. Unfortunately there is not any hot fix possible; pool uses sticky sessions, which mean that specific worker is always going to the same instance.

Edit: My apologize to all for the last batch of "Connection timed out", I tried to fix it and had to restart the server. I think I wasn't succesfull , but I will definitely solve ronaldmaustin's and dishwara's problem tomorrow.

This is normal variance. For example, I have two identical miners, both 1.2 ghash/s, running for the same time. One found 19 blocks, second one 34...

Im a lot less lucky, in slush pool found 9 blocks, but my balance is just shy of 300.

Any chance of an indication in the 'my account' screen if the miner for the specific machine is up do date or not?

For the past 1-2 hours getting RPC errors & server down for maintenance...

Listener for "slush's pool": 28/02/2011 14:27:00, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:02, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:04, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:09, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:14, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:15, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:18, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 14:27:19, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:41:59, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:42:04, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:42:09, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:42:10Listener for "slush's pool" shutting down
, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:42:13, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 16:44:34, Problems communicating with bitcoin RPC
Listener for "slush's pool": 28/02/2011 17:40:41, Problems communicating with bitcoin RPC
Listener for "slush's pool": 28/02/2011 17:40:42, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 17:40:47, Problems communicating with bitcoin RPC
Listener for "slush's pool": 28/02/2011 17:40:49, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 17:40:51, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 17:40:55, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 17:40:57, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:00, Problems communicating with bitcoin RPC
Listener for "slush's pool": 28/02/2011 18:11:03, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:05, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:10, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:12, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:14, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:15, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 18:11:17, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:29, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:31, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:32, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:37, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:39, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:41, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:45, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:47, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:20:49, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:42:03, Problems communicating with bitcoin RPC
Listener for "slush's pool": 28/02/2011 19:42:05, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:42:10, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:42:12, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:42:14, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:51:55, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:51:57, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 19:51:59, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:31, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:32, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:34, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:36, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:37, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:21:39, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:17, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:21, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:23, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:24, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:26, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 20:46:28, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:33, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:39, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:44, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:46, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:48, Server temporarily down for maintenance
Listener for "slush's pool": 28/02/2011 21:33:50, Server temporarily down for maintenance
Listener for "slush's pool" shutting down

* slush is searching his pool switching proxy

FairUser, you show again and again, that you completely don't understand the problematics. You are wrong, because this graph shows the oposite that you think, because it shows cheater rewards INCLUDING anti-cheating policies.

The best what cheater can give is +3% in his reward, but with very low probability, because the time to connect to the pool will vary in the future. Simply said, the time from round beginning is not fixed to 2000 second, it is just historical statistics. In the oposite, with share based pool, cheater can give fixed +25% (if I remember the number well) _all_the_time_, because the time to start cheating is well known (it is start of the new round).

By the way, feel free to introduce new pool, but, please, stop trolling here. If you don't like my services, don't use them.

Yes, it is strange, but this is probability. Many people told me that they were lucky with the pool, then they disconnect and didn't find any block in solo for multiplies of average time :-). My advice - choose solo or pool (depends on personality and hashing power) and keep it. Switching from pool, when you feel lucky and connecting to the pool, when you feel unlucky is the road to the hell, you are cutting your reward by bad management :-).

I found 80 blocks (=4000BTC) for the pool and my total payout is 4017 BTC, so I can say it really converge to expected reward distribution :-).

Yeah! I'm at 53.5% luckier than the average person! :^)))

I know it's normal for a random distribution. And its even more normal for a pool in which the strong help the weak. But the strange thing that I with low-end card 5670 @ 80Mhps was sponsor for other miners, and not >=9000 of rich guys with 5970 sponsored me.

I do not leave hopes someday to see the statistics of the distribution Mhps by clients, which we have already talked a long time ago.

I've found 2 blocks and earned about 185 BTC (+10 unconfirmed).

If you got ~expected daily reward, which I hope, then it is normal. This is how pool works; your personal luck is minimized, so if you are lucky, you got less bitcoins :-).

I've cashed out about 54 BTC from the pool and found one block.

According to the Slush's statistics, I found for the pool 8 blocks. And received 194 btc. Given the 2% charged by now, my "sponsorship weak miners" was "(1-194 / (8 * 50)) * 100 +2 = 53.5%". Or, in other words, I got 46.5% of the generated.
So that the last time I left in a pool only useless CPU-miners.

My total payout so far is 68.35 and I have found one block for the pool. I had received about 20 BTC before I found a block.