[150+ PH] SlushPool (slushpool.com); World's First Mining Pool

[-ck]

I just tested connecting to your pool:
 
[2011-12-24 08:00:33] Pool 0 http://api.bitcoin.cz:8332 active                   
[2011-12-24 08:00:33] Long-polling activated for http://api.bitcoin.cz:8401                   

Then I waited for a longpoll which worked.
Seems to work fine as far as I can tell.

Yes, that looks fine. Great that it works!

Indeed, but it doesn't explain the bug report occurring in the first place, unless they entered the pool details wrongly into cgminer.

[1508281496]

1508281496

[1508281496]

1508281496

[slush]

Indeed, but it doesn't explain the bug report occurring in the first place, unless they entered the pool details wrongly into cgminer.

What is the original bug report? Maybe I can help to track it...

[-ck]

Indeed, but it doesn't explain the bug report occurring in the first place, unless they entered the pool details wrongly into cgminer.

What is the original bug report? Maybe I can help to track it...

https://bitcointalk.org/index.php?topic=1976.msg634585#msg634585

[BinoX]

Just noticed on the stats page that the last 3 blocks have been "Processing..." for quite a long time, is there some kind of issue, or should I just be more patient?

[Idzy]

Yeah and my average mhs is wrong too, I'm pushsing close to 300mhs with my 2 miners and the site is showing 156mhs.

[Littleshop]

Just noticed on the stats page that the last 3 blocks have been "Processing..." for quite a long time, is there some kind of issue, or should I just be more patient?

Also my confirmed balance stopped rising even though a few blocks have been confirmed. 

[jonathan]

seems there is a problem here too. I've been stuck on a confirmed reward of 0.96934018 BTC since this morning--it's now 6PM here. I'm watching confirmations roll past 120, one after the other. My GPU is whirring away, and my stats page at bitcoin.cz is showing my shares, but there's no change to the reward. I gotta go now, unfortunately :-O

Update: All good now. Thanks Slush :-)

[Littleshop]

And now it appears fixed! My confirmed has rose and a payment processed.   Thanks Slush!

[bz]

From BTC stats:

9665    2011-12-28 15:04:18    1:02:26    1025518    0.16221904    0.76167915    159551    53 confirmations left
9664    2011-12-28 14:01:48    2:32:25    2379799    0.17081438    none    159547    49 confirmations left
9663    2011-12-28 11:29:19    0:03:35    60187    0.13084748    0.19946604    159534    36 confirmations left

Given NMC stats:

6923    2011-12-28 14:01:48    0:01:53    35286    41 confirmations left
6922    2011-12-28 13:59:53    0:00:50    35285    40 confirmations left
6921    2011-12-28 13:59:01    0:12:07    35284    39 confirmations left
6920    2011-12-28 13:46:52    0:19:17    35283    38 confirmations left
6919    2011-12-28 13:27:33    1:58:09    35280    35 confirmations left
6918    2011-12-28 11:29:19    0:03:34    35265    20 confirmations left

Should namecoins for BTC 9664 be none?

[BinoX]

Mine is also none for namecoins on the same block, so it's possible that it's how it's supposed to be...

0.1+ bitcoins a round? What kinda hashrate you got?

[slush]

I'm sorry for today issue with block rewards, everything is fixed now.

[bz]

I'm sorry for today issue with block rewards, everything is fixed now.

Looks good now, thanks!

[bz]

Mine is also none for namecoins on the same block, so it's possible that it's how it's supposed to be...

0.1+ bitcoins a round? What kinda hashrate you got?

3.9GH (a mix of 13 GPUs in 5 systems, wish I could justify FPGAs)

[mb300sd]

slush: did you get my PM? Would it be possible for you to send me the IP address of my miner? I'd prefer to avoid driving 100 miles round trip just to get it and can provide whatever you need to prove the account is mine.

Thanks.

[Foon]

Hi folks,

I'm wondering why I'm seeing severely reduced performance from my 5-GPU miner when connecting to this pool?  I get a constant 1650MH/s reported by Diablo when I'm on DeepBit (although DeepBit reports slightly less) but anywhere from 700-1300 on Slush, with a current 10-round hashrate of only 1161 (that's confirmed by submitted shares as well as Diablo reported hashrate).  LOTS of fluctuation in hashing speed, peaking well below what I know the miner can do (and no, it's not stales, which are currently ~0.3%).  If it helps my username is the same over there as here; PM me if you need more info than that.

Thanks!

[ensign_lee]

Does the "blocks found" counter still work? Just wondering, since it says that none of my miners have found any in basically the last several months. This could be true, but it seems like I'm several standard deviations away from normal when I've only officially found one block for the pool, but have received like 188 in payouts. Mining at like 1.7 Ghash here.

[a2offrb]

Hi Slush!
I think you have little error calculating namecoin reward.
This block
9694   2011-12-30 11:23:21   4:18:40   4211228   0.00000036   0.00000411   159805     97 confirmations left
I have turned off miner after about 3 hour mining(this block),  while hashing this bitcoin block - 6 namecoin blocks was found...
Just cannot believe that for 3 hour namecoin reward was only 0.00000411.

[slush]

Does the "blocks found" counter still work?

Yes, it works. And it's nice example that without pool mining, a lot of users won't find a block in months, even with significant hashrate. Btw some of my cards didn't find a block for months, too.

[slush]

I think you have little error calculating namecoin reward.

Pool is calculating only one score for both chains, using BTC as main currency. When bitcoin block is found, pool calculate user's scores and calculate bitcoin rewards. Then it pick all namecoin blocks found during Bitcoin round and split them between users using BTC score. The overall efect for block rewards in long term is the same, however if you stop or start mining in the middle of bitcoin round, your namecoin reward can be affected significantly.

[digital]

Something just went down...

Everything just got real quiet all of a sudden.  

Let's hope it's not another ddos.