Bitcoin Forum
September 28, 2016, 10:11:32 PM *
News: Due to DDoS attacks, there may be periodic downtime.
 
   Home   Help Search Donate Login Register  
Poll
Question: What type of pool payouts do you prefer?
Bitcoins - 3151 (80.4%)
Bank transfer / USD - 407 (10.4%)
Gold/silver coins and bars - 359 (9.2%)
Total Voters: 3915

Pages: « 1 ... 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 [440] 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 ... 1104 »
  Print  
Author Topic: [40+ PH] SlushPool (slushpool.com); World's First Mining Pool  (Read 3856848 times)
NoStr0m0
Newbie
*
Offline Offline

Activity: 22


View Profile
May 24, 2013, 05:05:10 AM
 #8781


Let's give it some time - yesterday it took over half an hour to get self-fixed. Mine is off too:
18176    2013-05-23 19:51:28    2:06:53    17624457    1650    0.00108921    none    237567    25.58627000    90 confirmations left

and earlier when I looked (at around 19:05 server time) my score had just reset and showed almost zero (a few microcoins).

Possibly but its been more than an hour and the # of shares looks normal when its updating the shares usually increases.  I also noticed 20 minutes prior to it ending the numbers reset.

It's now been several more hours and at least for me the rewards haven't been recalculated although miner was working non-stop.

18176   2013-05-23 19:51:28   2:06:53   17624457   1837   0.00130912   237567   25.58627000    36 confirmations left

I guess it's just a bout of bad luck. Well, can't complain, with overall good luck yesterday, it's still profitable.


By the way - does anyone else have any issues with this one - I'm quite a bit short on it too:
18179    2013-05-23 20:42:16    0:15:23    1329197    202    0.00287789    none    237575    25.35675211    44 confirmations left


A little short on that too if I calculate the reward per share.

if by some chance someone has made your day better, feel free to pass it forward:
1P8PHirMoc4uZGT48gLnrUCCj7GSgrRynq
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1475100692
Hero Member
*
Offline Offline

Posts: 1475100692

View Profile Personal Message (Offline)

Ignore
1475100692
Reply with quote  #2

1475100692
Report to moderator
1475100692
Hero Member
*
Offline Offline

Posts: 1475100692

View Profile Personal Message (Offline)

Ignore
1475100692
Reply with quote  #2

1475100692
Report to moderator
DryMartini
Jr. Member
*
Offline Offline

Activity: 37



View Profile
May 24, 2013, 05:09:53 AM
 #8782

Slush:
http://blockchain.info/block-index/385234/00000000000000f595dabc67b09229d6cd93224da85c46415f5c782e09ab576f
It's not registered but I think it showed up for a short while just before 237575 was found. Guess we got too lucky for our own good.

This was mentioned a couple of pages back but with the activity here it's easy to miss it. Time for a separate "chat thread" perhaps?
minerapia
Full Member
***
Offline Offline

Activity: 168


View Profile
May 24, 2013, 06:51:39 AM
 #8783

Slush,
one of the stratum servers seems to have some sort of connection problems with database. Even tho my miner is sending hashes, which are accepted allright, workers "Last share at" increases upto around 15 minutes. then (I presume the connection gets restored) all the sudden "Last share at" decreases back to zero. Refreshing web pages shows "Last share at" going 15->13->9->7->3->0 in less than a minute.

donations -> btc: 1M6yf45NskQxWXknkMTzQ8o6wShQcSY4EC
                   ltc: LeTpCd6cQL26Q1vjc9kJrTjjFMrPhrpv6j
Lucko
Hero Member
*****
Offline Offline

Activity: 714



View Profile
May 24, 2013, 08:05:51 AM
 #8784

Slush,
one of the stratum servers seems to have some sort of connection problems with database. Even tho my miner is sending hashes, which are accepted allright, workers "Last share at" increases upto around 15 minutes. then (I presume the connection gets restored) all the sudden "Last share at" decreases back to zero. Refreshing web pages shows "Last share at" going 15->13->9->7->3->0 in less than a minute.
Jp that is why I'm still afraid to move any big miner back and waiting for conformation from slush that he solved this problem. I lost on too many rounds because of this... Slush did report that it is problem with Amazon EC2 Instances...
TiborB
Member
**
Offline Offline

Activity: 83


View Profile
May 24, 2013, 09:17:06 AM
 #8785


Let's give it some time - yesterday it took over half an hour to get self-fixed. Mine is off too:
18176    2013-05-23 19:51:28    2:06:53    17624457    1650    0.00108921    none    237567    25.58627000    90 confirmations left

and earlier when I looked (at around 19:05 server time) my score had just reset and showed almost zero (a few microcoins).

Possibly but its been more than an hour and the # of shares looks normal when its updating the shares usually increases.  I also noticed 20 minutes prior to it ending the numbers reset.

It's now been several more hours and at least for me the rewards haven't been recalculated although miner was working non-stop.

18176   2013-05-23 19:51:28   2:06:53   17624457   1837   0.00130912   237567   25.58627000    36 confirmations left

I guess it's just a bout of bad luck. Well, can't complain, with overall good luck yesterday, it's still profitable.


By the way - does anyone else have any issues with this one - I'm quite a bit short on it too:
18179    2013-05-23 20:42:16    0:15:23    1329197    202    0.00287789    none    237575    25.35675211    44 confirmations left


A little short on that too if I calculate the reward per share.

Block 18176 is off for many of us. Have been waiting for the rewards to get recalculated, then sent a message to Slush at the time when there were only 12 confirmations left.
The block just got confirmed, no adjustments. Obviously, it would be chaotic and unmanagable if everyone cries about blocks, and there should be a proper way to escalate these issues and get them addressed on time. In many cases Slush is able to intervene, but on few occasions the issue does not get fixed.

What would be the preferred way of bringing attention to these issues - especially given that the spam-rate on this thread is rather high so Slush might not be able to notice/catch posts.

Cheers,
   T

PS: dear trolls, I am not complaining about the quality of service Slush provides, but seek a way how he could be notified of pool related issues is a smart way - without highly redundant communication -  in the future. This topic would have been the proper communication channel but given the white noise...
BTCIgnatious
Newbie
*
Offline Offline

Activity: 8



View Profile
May 24, 2013, 09:42:36 AM
 #8786

I am unable to receive e-mail from info@bitcoin.cz ...

Could you activate my account ?  Here is the line
from Exim's reject log:

2013-05-24 05:33:30 1UfoNO-0003HV-OF H=mt.chemispol.cz (fik.chemispol.cz) [80.92.250.103] F=<info@bitcoin.cz> rejected after DATA: syntax error in 'From:' header when scanning for sender: malformed address: <info@bitcoin.cz> may not follow info@bitcoin.cz  in "info@bitcoin.cz <info@bitcoin.cz>"
Envelope-from: <info@bitcoin.cz>
        (envelope-from <info@bitcoin.cz>)
        (envelope-from <info@bitcoin.cz>)
        (envelope-from <info@bitcoin.cz>)
  Subject: [mining.bitcoin.cz] New account confirmation
F From: info@bitcoin.cz <info@bitcoin.cz>
  X-DKIM-Status: none [(bitcoin.cz) - 80.92.250.103]
ewitte
Member
**
Offline Offline

Activity: 98


View Profile
May 24, 2013, 10:02:00 AM
 #8787

Slush,
one of the stratum servers seems to have some sort of connection problems with database. Even tho my miner is sending hashes, which are accepted allright, workers "Last share at" increases upto around 15 minutes. then (I presume the connection gets restored) all the sudden "Last share at" decreases back to zero. Refreshing web pages shows "Last share at" going 15->13->9->7->3->0 in less than a minute.

If you use cgminer you can specify failover pools you can do api2.bitcoin,cz, stratum.bitcion,cz, stratum2.bitcoin.cz, etc all at the same time.  This seemed to have stopped these for me.

Eric

Donations
BTC - 13Lgy6fb4d3nSYEf2nkgBgyBkkhPw8zkPd
LTC - LegzRwyc2Xhu8cqvaW2jwRrqSnhyaYU6gZ
Kruncha
Sr. Member
****
Offline Offline

Activity: 420


Winter is coming...


View Profile
May 24, 2013, 10:07:36 AM
 #8788

18179 is about to be confirmed as well Embarrassed

Nevermind...

K.
ewitte
Member
**
Offline Offline

Activity: 98


View Profile
May 24, 2013, 10:50:17 AM
 #8789

It evens out sometimes I get on the good end of the bad blocks.  IE 3-4 times the normal payment.

Donations
BTC - 13Lgy6fb4d3nSYEf2nkgBgyBkkhPw8zkPd
LTC - LegzRwyc2Xhu8cqvaW2jwRrqSnhyaYU6gZ
hasher87
Hero Member
*****
Offline Offline

Activity: 490



View Profile
May 24, 2013, 12:08:33 PM
 #8790

so i went on to try eclipse mining pool for the first time

oh dear me, 2 days of mining and i only got 0.009btc?Huh

Compare to slush's pool, i got an average of 0.01btc - 0.012btc per day

I'll never leave you again slushie!!  Grin

goddammit nad
DryMartini
Jr. Member
*
Offline Offline

Activity: 37



View Profile
May 24, 2013, 12:17:02 PM
 #8791

OK so 237573 and 237575 are now confirmed. My reward for 237575 went from 0.002-ish to 0.0003-ish. 237574 which was mined at almost the same time is still not listed ( http://blockchain.info/block-index/385234/00000000000000f595dabc67b09229d6cd93224da85c46415f5c782e09ab576f )

Luck has been with us, no doubt. I just wish technology were too.
pikeadz
Full Member
***
Offline Offline

Activity: 238


View Profile
May 24, 2013, 12:20:36 PM
 #8792

18184 is showing a small return for me.  That's 3 in 24 hours.  I am pretty new here but something doesn't seem right.
mikesheadroom
Member
**
Offline Offline

Activity: 69



View Profile
May 24, 2013, 12:25:39 PM
 #8793

OK so 237573 and 237575 are now confirmed. My reward for 237575 went from 0.002-ish to 0.0003-ish. 237574 which was mined at almost the same time is still not listed ( http://blockchain.info/block-index/385234/00000000000000f595dabc67b09229d6cd93224da85c46415f5c782e09ab576f )

Luck has been with us, no doubt. I just wish technology were too.

I also experienced a near 80% rewards drop for block 237575.
Until Slush chimes in, we can only speculate that some sort of hardware error occurred during that window of time including blocks 237573 and 237574.
It's a shame to see BTC just vanish into oblivion.
rsbriggs
Full Member
***
Offline Offline

Activity: 183


Russian:: UID 0


View Profile
May 24, 2013, 12:45:29 PM
 #8794

I also experienced a near 80% rewards drop for block 237575.
Until Slush chimes in, we can only speculate that some sort of hardware error occurred during that window of time including blocks 237573 and 237574.
It's a shame to see BTC just vanish into oblivion.

Am also having big drop - almost 2 orders magnitude - for 237575.  Average reward being .0045  
Reward for 237575 being  .000084421.
 
Similar situation blocks 237642 and 237540.

Work for 237574 gone disappeared.

Rewards on before and after sides of problem blocks seeming normal.

Це́рковь бли́зко, да идти́ скли́зко, каба́к далеко́, да идти́ легко́.
mb
Newbie
*
Offline Offline

Activity: 12


View Profile
May 24, 2013, 12:52:25 PM
 #8795

Whoa. Finally got through the hoops to be able to post here..

I've been observing the reward calculation and seen some weirdness too. Including the estimated reward for the current block.

Maybe it's not just a matter of databases not being updated correctly, but some data type overflow. Miscalculation seems to happen when pool score passes 4G. If some intermediates are calculated as 32-bit values, bad things can happen to the outcome.

Just hope that Slush can look into this and possibly confirm this bug that has been biting us. More or less since the move to EC2, which could explain different compilers/platforms when compared to the ovh hosted machines.

bspurloc
Hero Member
*****
Offline Offline

Activity: 569


View Profile
May 24, 2013, 01:24:32 PM
 #8796

I also experienced a near 80% rewards drop for block 237575.
Until Slush chimes in, we can only speculate that some sort of hardware error occurred during that window of time including blocks 237573 and 237574.
It's a shame to see BTC just vanish into oblivion.

Am also having big drop - almost 2 orders magnitude - for 237575.  Average reward being .0045  
Reward for 237575 being  .000084421.
 
Similar situation blocks 237642 and 237540.

Work for 237574 gone disappeared.

Rewards on before and after sides of problem blocks seeming normal.


What happened is Slush must have adjusted it, but fixed it wrong not realizing 237574 was skipped.
when it got confirmed the Shares that mined 237574 were applied to block 237575 and since 237574 was a very short block we got a very low pay out on 237575. Before that adjustment my pay out for 237575 was too high but not high enough to make up for missing block 237574.
 With block 237574 being completely skipped with no pay outs.
TheUnk
Newbie
*
Offline Offline

Activity: 17


View Profile
May 24, 2013, 01:36:43 PM
 #8797

Doesn't this scoring method encourage pool hopping?

I mean, what is to stop someone for creating a tool to mine this pool for only the first 15mins or so of each new round and then jump over to another pool, a PPS perhaps.

Lets say your payout average is .25 a block on Slush and .20/hr on a PPS. Lets also say that out of 20 rounds, Slush has 5 10min blocks and 15 2hr blocks . The hopper spends 4hrs or so on the pool and gets full payment for 5 blocks in addition to a consistent rate from their PPS pool in between.

Over the 30 hours:
The hopper gets 1.25 from Slush, + 5.2 from their PPS. Earning 6.47 BTC.
Loyal slush miners get full payment for 20 blocks. Earning 5 BTC.


If slush had 20 rounds all 2+ hours:
The hopper would get nothing for their 5 hours, and they only spend 5 hours even if some of those rounds are 4+ hours, but the other 35+ hours spent on a PPS they earn at least 7 BTC.
Loyal miners would earn 5 BTC over the 40+ hours.
TomKeddie
Full Member
***
Offline Offline

Activity: 176


View Profile
May 24, 2013, 01:41:49 PM
 #8798

Doesn't this scoring method encourage pool hopping?

I mean, what is to stop someone for creating a tool to mine this pool for only the first 15mins or so of each new round and then jump over to another pool, a PPS perhaps.

Lets say your payout average is .25 a block on Slush and .20/hr on a PPS. Lets also say that out of 20 rounds, Slush has 5 10min blocks and 15 2hr blocks . The hopper spends 4hrs or so on the pool and gets full payment for 5 blocks in addition to a consistent rate from their PPS pool in between.

Over the 30 hours:
The hopper gets 1.25 from Slush, + 5.2 from their PPS. Earning 6.47 BTC.
Loyal slush miners get full payment for 20 blocks. Earning 5 BTC.


If slush had 20 rounds all 2+ hours:
The hopper would get nothing for their 5 hours, and they only spend 5 hours even if some of those rounds are 4+ hours, but the other 35+ hours spent on a PPS they earn at least 7 BTC.
Loyal miners would earn 5 BTC over the 40+ hours.


You need to read more of this thread to understand the scoring.  The scores are weighted towards the end of the round to stop this.  A hopper doing what you describe would get little or nothing from most rounds.
TheUnk
Newbie
*
Offline Offline

Activity: 17


View Profile
May 24, 2013, 01:49:06 PM
 #8799

Doesn't this scoring method encourage pool hopping?

I mean, what is to stop someone for creating a tool to mine this pool for only the first 15mins or so of each new round and then jump over to another pool, a PPS perhaps.

Lets say your payout average is .25 a block on Slush and .20/hr on a PPS. Lets also say that out of 20 rounds, Slush has 5 10min blocks and 15 2hr blocks . The hopper spends 4hrs or so on the pool and gets full payment for 5 blocks in addition to a consistent rate from their PPS pool in between.

Over the 30 hours:
The hopper gets 1.25 from Slush, + 5.2 from their PPS. Earning 6.47 BTC.
Loyal slush miners get full payment for 20 blocks. Earning 5 BTC.


If slush had 20 rounds all 2+ hours:
The hopper would get nothing for their 5 hours, and they only spend 5 hours even if some of those rounds are 4+ hours, but the other 35+ hours spent on a PPS they earn at least 7 BTC.
Loyal miners would earn 5 BTC over the 40+ hours.


You need to read more of this thread to understand the scoring.  The scores are weighted towards the end of the round to stop this.  A hopper doing what you describe would get little or nothing from most rounds.

What part did I not understand?  They get full pmt for the short rounds they were part of entirely and nothing for the long rounds they left on.
DryMartini
Jr. Member
*
Offline Offline

Activity: 37



View Profile
May 24, 2013, 01:51:40 PM
 #8800

Oh well. I'll go back to 50btc and mine my regular 0.04 a day. The 10-50% extra I can make here just aren't worth being on call 24/7. It's a shame though, cause this has always been my first choice.

The bottom line is a business critical system, which this actually is, can not be this unstable. I'm a developer myself and I would be without work if I shipped applications with bugs of this magnitude. I'm not just talking about the last 24 hours, but the last month at least. As far as I know this is totally unprecedented in other pools, and we shouldn't be expected to put up with it.

My advice to you Slush is:
Take the pool offline and fix all problems with disappearing blocks and flucturing rewards. I'm sure you can do it again.
Pages: « 1 ... 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 [440] 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 ... 1104 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!