 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
|
Whilst it's true an increased total hashrate will bring the rewards down, surely (excluding Luck) probability dictates they should be more frequent.
|
|
|
|
|
Seems the problem is with you!
Pinging stratum.bitcoin.cz [54.225.116.221] with 32 bytes of data:
Reply from 54.225.116.221: bytes=32 time=133ms TTL=41
Reply from 54.225.116.221: bytes=32 time=164ms TTL=41
Reply from 54.225.116.221: bytes=32 time=344ms TTL=41
Reply from 54.225.116.221: bytes=32 time=207ms TTL=41
|
|
|
|
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? |
|
|
|
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! |
|
|
|
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. |
|
|
|
|
17995 looks to have finally processed for me that tooka long time, maybe the new hosting is having resource issues?!
|
|
|
|
|
Thing is, besides the recent single block, it seems to be working fine for everyone else ... and that's a lot!
|
|
|
|
|
I agree.
I used the term "sort it out" above meaning when there are problems which there clearly aren't atm.
|
|
|
|
Man slush is never gonna come back...
(at least i wouldn't if i were him)
Well the other day there were 30 blocks discovered. 30 blocks at 2% = 15 BTC 15 BTC roughly = $1700$1700 dollars a day would make me sort it out! |
|
|
|
I have problems with this block. It is impossible that I have this reward from these shares:
17925 2013-05-08 14:13:44 1:27:14 11634278 157 0.00000004 235160 25.21733124 confirmed
I think that might be problems with this other block because it is impossible that I have no one shares in about 2 min.
17924 2013-05-08 12:46:30 0:01:55 251435 none none 235151 25.08370000 confirmed
Can you resolve this?
17925 rewards are screwed, we know that... you would too if you had even glanced at the preceding 5 pages! However, 17925 you submitted 157 shares over 5234 seconds = 0.0299 shares per second 17924 lasted 115 seconds meaning you would have submitted 3 shares ... its not beyond the realms of possibility that they were rejected/not counted etc. |
|
|
|
|
Has anyone noticed block 17941 was worth 28.55 coins.
(Sorry if that's too much of a newb thing to post and will upset some people)
|
|
|
|
Why is everyone only looking at the number of shares they submitted to a particular round and deciding they got screwed? Not all shares are equal - you have to divide your score by the total score for the round to determine your reward, as Slush clearly points out here: https://bitcointalk.org/index.php?topic=1976.msg50002#msg50002reward = user score / total score * 25 The scores for round 17925 probably got reset (normalized) right before it ended, resulting in many people with very low scores and only the few that managed to squeeze in a share or two right at the very end getting most of the reward. If you bothered reading any of the posts you will see that they're not. Using the correct calculations peoples scores are off by a degree of an extra 0.0000 ... thats more than the normal "shares near the block discovery are worth more" debate. |
|
|
|
Regarding that block #17925 I suspect what's the problem . From what I can see it appears that majority of the folks didn't submit any shares in the last X minutes while others did continue to submit shares. The most reasonable explanation to this is that there was some network issue (routing or clogged traffic) and something happened to **some** of the pool's endpoints but not to **all** of them. In other words - a few of the IPs listed below may have been DDoS-ed, and those that were connected to them suffered as they were unable to submit their shares, while the unaffected IPs worked just fine and those people connected to them did get their (at that point) fair share: that's from a few days ago: C:\Users\me>nslookup stratum.bitcoin.cz
Server: rdns-lb-01.orange.rr.com
Address: 66.75.160.63
Non-authoritative answer:
Name: stratum.bitcoin.cz
Addresses: 54.225.117.74
54.215.3.100
54.215.3.101
54.215.3.102
54.215.3.103
54.225.68.97
54.225.116.40
54.225.116.174
54.225.116.221
and looking at my currently connected worker - I am currently connected to one of those: TCP 192.168.0.70:54312 54.215.3.103:3333 ESTABLISHED Unfortunately I don't think slush would have any (easy) means to find out which IPs of the pool worked at that time and which didn't. If that's the case then I guess all I have to say to the winning folks - congrats for the bonus!  (that's unless slush wishes to manually recalculate the payout for that block, but the time for this is running out rather quickly too)Thats totally not the case! The submitted shares figure from most people is correct. |
|
|
|
To be honest, the reason slush hasn't been on the board, is because of the all the noob's posting 2 pages a day. Slush doesn't have time to sit here all day to keep up on the posts. And when he finally gets back to the board he has 8 pages to catch up on, which he just can't do.
If we could keep all the repeat, and useless posts off the thread it would work the way it was supposed to work. But for now, someone will likely have to pm him (already been done) to get his attention.
There appear to be 4 posts from yourself discussing the recent incorrect block   Exactly. Which is looking like a problem with the pool. Which is exactly what this thread is for, pertinent pool related conversation. I didn't repeat a question that has been answered 50 times already. And I didn't make a random comment about something completely unrelated. I used the thread for what it was designed for. Sorry mate, I thought you'd take the comment as "tongue-in-cheek" as it was intended. Looking back now, I can laugh at the irony that posting about posts that are not what the thread was for is in itself not what the thread is for. I'm sure you can. |
|
|
|
To be honest, the reason slush hasn't been on the board, is because of the all the noob's posting 2 pages a day. Slush doesn't have time to sit here all day to keep up on the posts. And when he finally gets back to the board he has 8 pages to catch up on, which he just can't do.
If we could keep all the repeat, and useless posts off the thread it would work the way it was supposed to work. But for now, someone will likely have to pm him (already been done) to get his attention.
There appear to be 4 posts from yourself discussing the recent incorrect block |
|
|
|
Hi there I am only permitted to post in this section so would some kind soul pass this on to the Slush thread for me I normally get round about 0.01 BTC per block, but block 17925 seems screwed a little ... 0.00000123 and should be 0.01 # Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity 17925 2013-05-08 14:13:44 1:27:14 11634278 4629 0.00000123 235160 25.21733124 97 confirmations left 17924 2013-05-08 12:46:30 0:01:55 251435 107 0.01052650 235151 25.08370000 88 confirmations left 17923 2013-05-08 12:44:35 0:36:37 4874601 1873 0.00984750 235150 25.09740000 87 confirmations left 17922 2013-05-08 12:07:58 0:18:52 2558082 999 0.00935872 235145 25.37765000 82 confirmations left Cheers |
|
|
|
|
Yeah I've read lots of guides and these are my outstanding questions that I can't seem to get an answer to.
As far as waiting, I test graphics cards so am going to use mining as part of the tests and there's usually a fair bit going on at once ...
Right now on test there are:
6 x 7970 on 3 test rigs.
4 x 7950 on 2 test rigs.
1 x 6990
1 x 5970
1 x 6970
6 other cards hardly worth mentioning 5770 etc
Cheers
|
|
|
|
|
Sorry I'm not sure what the correct terminology is but I mean mining to my own own instance of "bitcoin-qt -server" i.e. not connected to a pool.
I thought it was solo mining.
rpcuser is the account user you set in the bitcoin.conf.
|
|
|
|
|
