You are paid for the work you did.
This is not quite true. - To be paid for the work you did, you have to go for a PPS pool.
- There's effectively no difference whether your new shares pay more than the old ones or the old ones pay less than the new ones.
- Your score (value of shares) is recalculated from time to time in long rounds. The ratio of the old shares to the new ones is kept, but their absolute value is not.
These are facts to be corrected relating the quoted post. In fact, you are punished for disconnection. You're punished exactly the same way you'd been in PPS in the long run, provided that you disconnect asynchronously, i.e. randomly. At Slush's, you can either lose, when you disconnect near the round end, or you can gain, when you disconnect at some other time. In the latter case, your payout for the round won't be decreased due to the disconnection, although you would deserve some decrease. And as the time constant c is hopefully still 300 seconds and an average round is several times longer, it's greater chance for you to gain a bit than to lose substantial part of the reward. Anyway, in the long run that should even out, as is the popular phrase in this thread for some time already... :-) I meant to say you are paid for the work you did in relation to the work everyone else did at the same time, but I see your point about periodic renormalization affecting the impact of a dc. You're also right about no difference between new paying more and old paying less -- the cup is still half full -- but I have a hard time feeling I'm being punished for my downtime when ... well ... I'm down.
|
|
|
Anyone know if the merged NMC mining is still working? My NMC balance hasn't changed in weeks.
Seems like the same question gets asked 3-4 times a day. NMC is no longer supported by the pool. Slush should update the Web site and post something in News.
|
|
|
Slush has been very reliable regarding keeping their servers online. (Their stratum server is fine compared to Guild's EU stratum.......) In short, everything is fine with Slush except their policy to punish people hopping pools. That's okay, but they also should consider that some people experience problems like the one you mentioned which we have no control over. These people are getting a punished while we don't deserve that. It happened to me several times before, when my isp is doing maintenance etc. It's Summer now and more people will be having hardware failures due to the heat. And the last thing we need is our pool operator kicking us while we're down by cutting our pay. To me, this is injustice.
Ah, I understand your issue now. From the pool's perspective, unintentional disconnects look the same as pool-hopping, but round-based pool like Slush's must have protection against pool-hoppers -- that's why Slush scores each share based on its time submitted -- round.total-score = sum(share.score + exp ((share.time-since-round-start)/c), where c is calculated based on total number of shares for the round and your shares-per-second across the round. While it might seem that older shares are reduced in value as they age, the truth is that each share after your first one increases in value. You are not "punished" for a disconnect. Let's say you submitted 100 shares then dc'd for the rest of the round. At the end of the round, those 100 shares have the same score based on when they were submitted as they would have had if you'd mined all the way through the round. You are paid for the work you did.
|
|
|
sounds to me your equipment is effing u over not Slush. resolve your problems and dont bad mouth Slush for your problems.
What's your problem? I got a problem with Slush's way of threating their members. It's normal that sometimes the hash rate goes down whatever the cause is, but it is not normal that Slush will punish their members so bad! It's already hard enough to mine some bitcoins nowadays. I got my opinion and it got nothing to do with you! Are you their lawyer? A few weeks ago, I was having similar problems. I'd been mining on Slush with good results but it seemed my payouts were starting to get random, then I noticed my mining software (cgminer and bfgminer) was reporting more stale shares than previous and also began random appcrashes. Yeah, I thought something was wrong with Slush, so I moved to another pool and things seemed to be better for a few days, then it all started happening again there. Finally, the modem started random dropouts. Called my DSL supplier and they sent a tech out -- found I was 450 meters further from their local switch than my high speed line rate allowed -- signal was just below borderline minimum and the modem wasn't strong enough to consistently pull it in. After he called the central office to drop my line rate to the slower tier signal, the modem -- and my mining -- stabilized immediately. I also immediately came back to Slush's pool. Now, I'm waiting for more switches in my neighborhood and I'm looking for a better modem, but my only mining problem is how to add hash rate fast enough to keep up with the network. I'm not saying you have the same problems I had, but I think 21Th/s worth of satisfied miners suggest it's not the pool that's causing whatever is wrong with your results here. If you check out your end of things and still feel Slush's pool isn't giving you what you expect, then try the other pools. And if there is a problem with this pool, then Slush is probably working on fixing it -- debugging software and/or adding new features takes time.
|
|
|
That's good news if it holds that low
|
|
|
Yeah, a 942 BTC transaction.
|
|
|
What happens when u get everything you ever wanted.....
You start wishing you hadn't made some of those wishes
|
|
|
I think that the problem is that we are looking at long term and you are looking short term. Yes, until the difficulty increase the time to find a block would decrease. And you would continue to find them at a constant rate. But, when he difficulty does go up, it will more than compensate for the previous "gift". At least i think it will. there are those that speculate that the date the last Bitcoin is mined is slowly moving closer.
If you mean the last bitcoin mined by design, that won't happen until sometime in 2041 -- but there are things that could shut down the network before then, and somebody will be the last to find a block.
|
|
|
Can anybody tell me why stratum doesn't work with Erupter Blades? stratum.bitcoin.cz:3333 works just fine with USB Erupters, but not with Blades. Blades are hard-coded for getwork -- you'll need to use a stratum proxy.
|
|
|
Yup, 18702 needs a recalc
18702 2013-06-22 15:21:37 1:59:11 30464457 5986 0.00000107 242788 25.44442180 88 confirmations left
|
|
|
Anyone know if I should be running my suggested difficulty at 32 or 64 if I have a Avalon mining away @ 80000
According to worker settings options on your My Account page, anything in the range 65-128Gh/s should have a diff of 64.
|
|
|
My theory about activity is that the quality of your posts, as well as the number of replies you give to the same topic, and the time spent on the forum determines it. If you reply more to a thread with quality posts, in theory, you are more "active."
How would it be able to check the quality of your posts? I kinda like the idea tho. Word count, I guess. And Lexile score maybe? I don't know, maybe an admin will make an announcement later today. Hope it's not just word count -- I mean, sometimes somebody asks a yes or no question, you'd have to add some spam to the answer in order to get word count credit
|
|
|
The problem is how do we increase our activity score. Some people have been booted from Heroes to Juniors I've heard!
That's a good question -- might not be related to just posting since I just made a post, but my activity score stayed the same.
|
|
|
I think this an April fools joke from BFL which just arrived.
No, the April Fools joke from BFL is not scheduled to ship until next week
|
|
|
2013-06-17 22:37:11: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:11, Verification failed, check hardware! (0:0:Barts, ce5273db) 2013-06-17 22:37:13: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:13, Verification failed, check hardware! (0:1:Cypress, 727d93c7) 2013-06-17 22:37:20: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:20, Verification failed, check hardware! (0:0:Barts, a2952421) 2013-06-17 22:37:29: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:1:Cypress, 70fe5733) 2013-06-17 22:37:29: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:0:Barts, 0df11781) 2013-06-17 22:37:31: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:31, Verification failed, check hardware! (0:1:Cypress, 0558f90a) 2013-06-17 22:37:37: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:37, Verification failed, check hardware! (0:1:Cypress, 1e22764a) 2013-06-17 22:37:40: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:40, Verification failed, check hardware! (0:2:Juniper, 00d0bf18) 2013-06-17 22:37:44: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:2:Juniper, a415432f) 2013-06-17 22:37:44: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:0:Barts, fb1cb804) 2013-06-17 22:37:45: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:45, Verification failed, check hardware! (0:1:Cypress, 9e719e0e) please help me diaganosis this
Probably a Catalyst problem. Are you using 12.8, and what driver version?
|
|
|
Are there any data for the whole "network luck"? I'm afraid those can't be obtained easily, because the whole network hashrate is calculated from found blocks, thus supposing "network luck" equal to 100 %. This way, one can't differentiate between hashrate changes and luck changes. Or am I wrong?
On way of looking at it is that luck for the whole network is 100% all the time -- I mean, the network always finds a block. Another way of looking at it is whether the network is finding blocks in less than 10 minutes average per block (>100%), at 10 minutes average (100%), or longer than 10 minutes average (<100%), but then difficulty changes are used to keep the average as close to 10 minutes as possible.
|
|
|
Sobering. The acceleration in magnitude of difficulty increase every couple of weeks indicates that it won't be long until a 1 Th/s worker will earn around 0.01 BTC per block found by the pool.
|
|
|
I temporarily doubled my hash rate and earning the same amount per round. Once I sell my other PC with the 7850, I think I'm done with cryptocoins.
Reaper is the only mining software working with my hardware, so I'm limited with what I can use with LTC (reaper, cgminer, bfgminer, none works for me on LTC mining).
GPU Mining is the only viable option for me since AISC is not easily or affordably obtainable.
And this dwindling luck isn't helping. This s the first I've seen it dip down to the 60s %
cgminer works ok for me mining LTC. You might have a typo in some option or left something out, tho. Here's my cmd line for WeMineLTC pool: cgminer --scrypt -o stratum+tcp://us.wemineltc.com:80 -u workername -p workerpass -d 0 -I 12 -w 64 --thread-concurrency 8192 I use the -d 0 so that only gpu0 starts, and then I can start or stop my other gpus ala guiminer. Makes switching from mining to gaming to mining easy. If you haven't already seen it, check out https://github.com/ckolivas/cgminer/blob/master/SCRYPT-README for using cgminer on LTC.
|
|
|
I have a question about ASIC mining on slush's pool. what software should i use? will the guiminer work? I haven't received delivery of my ASIC yet because; BFL, but I want to be ready to go as soon as I get it.(in 2 weeks apparently) anyways, what is the recommended software to hook up my ASIC to the pool?
Not sure if guiminer will handle ASICs, but I couldn't get it to work with my FPGAs. I use it on one gpu rig and cgminer on the other. I've had trouble with cgminer staying connected for FPGAs so for them I use bfgminer. Since bfgminer also handles Avalon rigs, I imagine it will run BFL ASICs, too.
|
|
|
|