[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[jundesirehd]

18008   2013-05-13 05:17:33   2:14:34   18510235   10083   0.00000000   235946   25.34290000    71 confirmations left
18007   2013-05-13 03:02:59   1:59:17   16473280   14479   0.02256364   235925   25.02000000    50 confirmations left

Sigh... 

[1714507902]

1714507902

[1714507902]

1714507902

[1714507902]

1714507902

[1714507902]

1714507902

[1714507902]

1714507902

[1714507902]

1714507902

[irritant]

and the total score is getting better again

[LordTheron]

 over 3 hours round and invalid? whats wrong with the pool?

17983   2013-05-11 15:16:28   3:49:53   33222989   5926   0.00494658   235671    25.51570000    invalid

[sunriselad]

Estimated reward: 0.00000001 BTC

WTF?!?  Score reset?!? Again?!?

NO

Looks to me (besides that first reset block that started all this) like the only thing that is wrong with the scoring system is that it is taking a lot longer to FULLY total and calculate scores, so you are seeing the figure increase slowly as it does it.

People with "missing shares" or whatever I can't comment on 'cos using cgminer on stratum. seems fine to me.

Come on guys, sitting there refreshing the score when it finishes processing and reporting "LOOK ANOTHER ONE" and ultimately "OH! IT'S OK NOW" is as unproductive as I can imagine, in fact it can only serve to put people off the pool.

IMHO, if it's instance stats feedback you "need" then this probs ain't the pool .... at the moment.

[LordTheron]

why slush is not addressing all the issues with the pool? its bee crap since moved to amazon. my rewards are smaller, many problems with connection, site not updating correctly for me. looks like its time to move to different pool. Sorry slush.

[sunriselad]

over 3 hours round and invalid? whats wrong with the pool?

17983   2013-05-11 15:16:28   3:49:53   33222989   5926   0.00494658   235671    25.51570000    invalid

I don't think an invalid block is anything to do with the pool being wrong!

[sunriselad]

why slush is not addressing all the issues with the pool? its bee crap since moved to amazon. my rewards are smaller, many problems with connection, site not updating correctly for me. looks like its time to move to different pool. Sorry slush.

Wouldn't a 3 million difficulty increase mean that it will take longer i.e. more total shares to find blocks.
Wouldn't that surely mean your contributed shares would be worth a lot less per round? .. Unless you have increased you hash power accordingly, which you didn't mention?

The total pool hashrate has also increased meaning more shares per second are being added to the total ... thus making your shares worth even less!

Site not updating  ... see post above.

So what exactly would you move for?

[Lucko]

over 3 hours round and invalid? whats wrong with the pool?

17983   2013-05-11 15:16:28   3:49:53   33222989   5926   0.00494658   235671    25.51570000    invalid

I don't think an invalid block is anything to do with the pool being wrong!

It is pool. This means that is is not connected well enough to detect new block or send it out in time... Slush had 2 or 3 invalids in last 5 days... Pool has real problems... That is why I moved but still looking if it will be fixed. Doesn't look like it will happen.

[PrintMule]

Come on guys, sitting there refreshing the score when it finishes processing and reporting "LOOK ANOTHER ONE" and ultimately "OH! IT'S OK NOW" is as unproductive as I can imagine, in fact it can only serve to put people off the pool.

That

[Lucko]

So what exactly would you move for?

My reasens were:
1. No Slush
2. Missing shares on 11 blocks(maybe more I looked logs only for ones that were off)
3. The block that I only got minimal reword
4. No NMC on stratum
5. Seeing problems increasing not decrising
EDIT: 6. Stop complaining or change the pool guys

[HellDiverUK]

As a GPU miner, I've given up on Slush's pool, and BTC mining in it's entirety.  I'm getting better returns from LTC mining.

[ewitte]

The pool has seemed ok since the move can't fault for difficulty increase or luck.  We had really bad luck shortly after in came back up then really good luck.  Now we are in really bad luck again.  After the current block if we get 1-2 more we are under 60%

[rsbriggs]

Come on guys, sitting there refreshing the score when it finishes processing and reporting "LOOK ANOTHER ONE" and ultimately "OH! IT'S OK NOW" is as unproductive as I can imagine, in fact it can only serve to put people off the pool.

That

OK.  Would you care to explain these results for set of miners doing 1.8Gh/s and connected 24x7 with cgminer???

18011   2013-05-13 11:08:28   1:49:26   15381772   1215   0.00441004   235990   25.32340000    98 confirmations left
18010   2013-05-13 09:19:02   3:23:32   27970291   none   none              235980   25.54710101    88 confirmations left
18009   2013-05-13 05:55:30   0:37:57   5241181    none   none              235954   25.09833800    62 confirmations left
18008   2013-05-13 05:17:33   2:14:34   18510235   2632   0.00000000      235946   25.34290000    54 confirmations left
18007   2013-05-13 03:02:59   1:59:17   16473280   2550   0.00323839      235925   25.02000000    33 confirmations left
18006   2013-05-13 01:03:42   0:04:40   633490        109   0.00437391      235911   25.06273800    19 confirmations left

[GuiltySpark343]

Thanks!   That edit works to fix connection problem.  But code needs work, slush items like estimated reward don't work as is.

I tweaked it a bit on mine to give:

[GuiltySpark343]

OK.  Would you care to explain these results for set of miners doing 1.8Gh/s and connected 24x7 with cgminer???

Can you try a tracert command to the Slush server you are using? Open a Command window, and type tracert ADDRESS and see if it gets stuck anywhere along the line. Maybe you have dropped packets and so have trouble getting work or sending shares back?

[lsvpa]

I just wanted to add to this whole "having problems" trend lately that I have not had any issues with block payouts whatsoever, so i don't think it's a universal problem.

[rsbriggs]

OK.  Would you care to explain these results for set of miners doing 1.8Gh/s and connected 24x7 with cgminer???

Can you try a tracert command to the Slush server you are using? Open a Command window, and type tracert ADDRESS and see if it gets stuck anywhere along the line. Maybe you have dropped packets and so have trouble getting work or sending shares back?

Blocked somehow - other than my local router, all show

  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.

But not a connectivity issue - can ping just fine

C:\Users\Rachael>ping 56.192.78.3

Pinging 56.192.78.3 with 32 bytes of data:
Reply from 56.192.78.3: bytes=32 time=1ms TTL=255
Reply from 56.192.78.3: bytes=32 time=11ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255

Ping statistics for 56.192.78.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 11ms, Average = 3ms

[irritant]

OK.  Would you care to explain these results for set of miners doing 1.8Gh/s and connected 24x7 with cgminer???

Can you try a tracert command to the Slush server you are using? Open a Command window, and type tracert ADDRESS and see if it gets stuck anywhere along the line. Maybe you have dropped packets and so have trouble getting work or sending shares back?

Blocked somehow - other than my local router, all show

  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.

But not a connectivity issue - can ping just fine

C:\Users\Rachael>ping 56.192.78.3

Pinging 56.192.78.3 with 32 bytes of data:
Reply from 56.192.78.3: bytes=32 time=1ms TTL=255
Reply from 56.192.78.3: bytes=32 time=11ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255

Ping statistics for 56.192.78.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 11ms, Average = 3ms

why don't you use stratum.bitcoin.cz ?

[GuiltySpark343]

Odd. You pinged 56.192.78.3

However, when I use the word address

stratum.bitcoin.cz resolves to 54.215.3.100
stratum2.bitcoin.cz resolves to 54.225.116.40

Perhaps you are using older server address? What do other people resolve to?

The other thing I have read, is that because of DDoS attacks the firewall at the server has some routine that can block people from connecting. Contacting Slush with this directly seems to allow him to enter something to let you in (tho Slush seems AWOL).

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

[rsbriggs]

I typo'ed IP address from before - part wrong and part my router.  tracert "stratum.bitcoin.cz" all still blocked.  Ping also blocked.  Yet miners are happily submitting shares.  Maybe whole network paranoid and not responding to ICMP packets due to potential DDOS?

C:\Users\Rachael>ping stratum.bitcoin.cz
Pinging stratum.bitcoin.cz [54.225.116.221] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.225.116.221:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Found blocks   Current shares   Score           Last share at   Mhash/s*   
   0                2114           4979962.7183   0 minutes           1718.312

Maybe I am just shutting up for a few days.  If am still missing more block payouts in next days then sadly I am being move to another pool.  But really like Slush's pool - just right size.