village.idiot
|
|
February 05, 2012, 06:11:10 PM |
|
Yes, your guide. It's the only one I've used.
Wow, I like easy. Sorry I still don't know what I'm doing.
Thanks a bunch
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 05, 2012, 06:16:34 PM |
|
No problem. For those not able to update or not use git for whatever reason, here's the fix: Find this in Transport.py (around line 92): bits = hex(difficulty) bits = bits[2:len(bits) - 1] bits += ('0' * (8 - len(bits))) bits = ''.join(list(chunks(bits, 2))[::-1]) Replace those four lines with this one line: bits = '%08x' % difficulty.byteswap()
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
NetworkerZ
Member
Offline
Activity: 114
Merit: 10
|
|
February 05, 2012, 09:21:47 PM |
|
A windows binary update will be there too!
Greetz NetworkerZ
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 06, 2012, 12:10:49 AM |
|
Ok folks - because BIP 16 and 17 are such a hot topic, I have enabled your ability to vote for whichever BIP you want. Mining on US3 will be a vote for BIP 17, mining on US2 will be a vote for BIP 16 and mining on US1 will be an abstain. US 1 - Abstain from voting US 2 - BIP 16 US 3 - BIP 17 When and if an official decision is made and the blockchain is irrevocably modified to support one or the other, all servers will converge to support the appropriate change (if any). If none of this makes any sense to you, don't worry about it and just keep on doing what you're doing as it probably doesn't affect you for the most part and is really a technical matter for those interested. You can read more about it here: https://bitcointalk.org/index.php?topic=61125.0Though I suggest you read more than just that thread, the BIP 16 and BIP 17 threads for instance, before jumping to any decisions. Ultimately, though, for most people, it's an academic argument, so I wouldn't worry too much about it.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
Math Man
|
|
February 06, 2012, 12:21:53 AM |
|
Thanks for making this democratic.
|
|
|
|
gnar1ta$
Donator
Hero Member
Offline
Activity: 798
Merit: 500
|
|
February 06, 2012, 12:38:19 AM Last edit: February 06, 2012, 12:51:23 AM by gnar1ta$ |
|
Great job with BIP voting inaba, one more reason for miners to use this pool. If this is the only pool offering voting, you should put an post on the discussion board, see if brings in more miners until it gets moved.
|
Losing hundreds of Bitcoins with the best scammers in the business - BFL, Avalon, KNC, HashFast.
|
|
|
village.idiot
|
|
February 06, 2012, 12:58:00 AM |
|
I understood nails, screws and glue but didn't get SHIT beyond that.
|
|
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
|
February 06, 2012, 04:53:20 AM |
|
I'm not sure what was up w/ the last round but my mining output was the same and pool gh was same but my payout was less then half of what been gettin last week..... my estimated reward also reflects this low amount... Why? is the votin system messin it up? Cuz I mine both us2 and us3 equally.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 06, 2012, 05:08:17 AM |
|
Are you using poclbm? There was a substantial bug that just showed up in it a few days ago where it will keep hashing and getting work, but it fails to actually submit the shares. I had two machines running like that for two days before I realized it.
The voting is pretty much separate from share submittal, so it shouldn't have anything to do with it.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
|
February 06, 2012, 06:42:48 AM |
|
nope, I use phatk on cgminer gonna try just mining on us1 and not splitting shares between any of the servers. See if that fixes the problem, if not then I dont know whats going on. Nothing has changed on my end. Cuz even eclipsemc my worker status says its the same as it was but my payout is less then half it was =( this has been 3 blocks in a row now.
Even my share ratio to entire pool share count for the last 3 blocks remains the same as it did before. I dont understand
|
|
|
|
cuz0882
|
|
February 06, 2012, 07:58:59 AM Last edit: February 06, 2012, 10:03:56 AM by cuz0882 |
|
nope, I use phatk on cgminer gonna try just mining on us1 and not splitting shares between any of the servers. See if that fixes the problem, if not then I dont know whats going on. Nothing has changed on my end. Cuz even eclipsemc my worker status says its the same as it was but my payout is less then half it was =( this has been 3 blocks in a row now.
Even my share ratio to entire pool share count for the last 3 blocks remains the same as it did before. I dont understand
I think something is wrong also. I have over 11gh, and I received .5745 as a reward. Which is .01149 of the total pool. That would mean the pool's hash rate was around 970gh. The hash rate was actually 580gh. The reward should be more like .94 I also use cgminer but in windows.
|
|
|
|
NetworkerZ
Member
Offline
Activity: 114
Merit: 10
|
|
February 06, 2012, 09:52:12 AM |
|
Your reward belongs to the shares you submitted, not the MHash!
Greetz NetworkerZ
|
|
|
|
cuz0882
|
|
February 06, 2012, 10:05:35 AM |
|
Your reward belongs to the shares you submitted, not the MHash!
Greetz NetworkerZ
The Mhash should match up pretty close unless you have a low hash rate or the block was solved really quickly. Regardless I had 22867 shares in the block I was using for a example with 1215505 Total shares for the block which is .018812 % multiplied by 50 is .94 total reward. I don't see how it could be correct at .57 reward.
|
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 06, 2012, 10:27:10 AM |
|
Your reward belongs to the shares you submitted, not the MHash!
Greetz NetworkerZ
The Mhash should match up pretty close unless you have a low hash rate or the block was solved really quickly. Regardless I had 22867 shares in the block I was using for a example with 1215505 Total shares for the block which is .018812 % multiplied by 50 is .94 total reward. I don't see how it could be correct at .57 reward. DGM does that for 2 reasons: 1) Your "capacitor" isn't fully charged 2) The pool got lucky
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 06, 2012, 01:42:48 PM |
|
I really need to find some way to graphically illustrate how DGM works for payouts, as it's not intuitive without investigating it thoroughly.
Cuz0882: How many blocks have you been mining?
GenTarking: How are you splitting the shares between servers? Just different instances of cgminer? Also, have you used the cashout option?
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
cuz0882
|
|
February 06, 2012, 02:57:22 PM |
|
I really need to find some way to graphically illustrate how DGM works for payouts, as it's not intuitive without investigating it thoroughly.
Cuz0882: How many blocks have you been mining?
GenTarking: How are you splitting the shares between servers? Just different instances of cgminer? Also, have you used the cashout option?
Only 21 blocks in this pool.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 06, 2012, 02:59:20 PM |
|
What is your user name? Also, have you used the cashout option?
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
cuz0882
|
|
February 06, 2012, 03:25:23 PM |
|
What is your user name? Also, have you used the cashout option?
cuz72 No, its set to auto pay in bitcoins.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
February 06, 2012, 03:45:38 PM |
|
Looks like you (and everyone else) are seeing the effects of the large hashrate increase. You should see a corresponding increase in your payout over the next few blocks after the hashrate stabilizes.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
|