Topic: Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB - page 108. (Read 1061417 times)
Thanks for the details!
Yes, they were captured within 2 minutes of each other. There is a backup pool set, but it hasn't received and shares at all if that's what you're wondering.
May I ask what the formula for calculating hashrate from the diff 1 shares is?
Diff1 shares per sec = hashrate / (2^48/65535)May I ask what the formula for calculating hashrate from the diff 1 shares is?
Not quite simplified... Diff1 shares per sec = hashrate / (2^32)
So, hashrate in hashes per second divided by 4294967296
Edit: Realized the original question was the opposite, so:
hashes_per_second = (diff1_shares * 4294967296)/time_in_seconds
https://en.bitcoin.it/wiki/Difficulty#What_network_hash_rate_results_in_a_given_difficulty.3F
Quote
The expected number of hashes we need to calculate to find a block with difficulty D is therefore
or just
and described in this postQuote
D * 2**256 / (0xffff * 2**208)
or just
Quote
D * 2**48 / 0xffff
https://bitcointalksearch.org/topic/m.740512
Yes, they were captured within 2 minutes of each other. There is a backup pool set, but it hasn't received and shares at all if that's what you're wondering.
May I ask what the formula for calculating hashrate from the diff 1 shares is?
Diff1 shares per sec = hashrate / (2^48/65535)May I ask what the formula for calculating hashrate from the diff 1 shares is?
Not quite simplified... Diff1 shares per sec = hashrate / (2^32)
So, hashrate in hashes per second divided by 4294967296
Edit: Realized the original question was the opposite, so:
hashes_per_second = (diff1_shares * 4294967296)/time_in_seconds
Yes, they were captured within 2 minutes of each other. There is a backup pool set, but it hasn't received and shares at all if that's what you're wondering.
May I ask what the formula for calculating hashrate from the diff 1 shares is?
Diff1 shares per sec = hashrate / (2^48/65535) May I ask what the formula for calculating hashrate from the diff 1 shares is?
Yes, they were captured within 2 minutes of each other. There is a backup pool set, but it hasn't received and shares at all if that's what you're wondering.
May I ask what the formula for calculating hashrate from the diff 1 shares is?
May I ask what the formula for calculating hashrate from the diff 1 shares is?
There's an issue with Antminer S4 and Eligius, Eligius isn't reporting the hashrate properly:
Pretty sure the issue is with the ASIC, but I figured I'd post this anyways.
Were all those images from the same time? 47,000 Diff1 shares over 50 minutes is not 2TH/sPretty sure the issue is with the ASIC, but I figured I'd post this anyways.
Do you have a backup pool?
There's an issue with Antminer S4 and Eligius, Eligius isn't reporting the hashrate properly:
Pretty sure the issue is with the ASIC, but I figured I'd post this anyways.
Pretty sure the issue is with the ASIC, but I figured I'd post this anyways.
I just realized I haven't gotten any NMC deposits in 2 weeks or so. Is there any way to see the NMC queue, or does it all just happen behind the scenes?
Thanks for any insight.
Thanks for any insight.
September 30, 2014, 10:58:20 PM
Ah yet another hash power buy sell place that makes no sense in practice...
Well whatever works.
Well whatever works.
ya doesn't make sense, i've been thinking about over n over and i have no clue why ppl would pay double what they can mine back for hash but i guess whatever i'll take it if they're willing to pay it...helps for diff. rate changes when luck goes to da crapper
September 30, 2014, 10:26:31 AM
If you're hash rate doesn't change then your estimated change probably won't change much if you have shelved shares.... this is normal.
OK, but if the estimate is between 0.45x and 0.5x every 3 hours at my current has rate and in 5 hours what I had hashed is still the same, then there is something wrong.
If your shares rewarded are less than 100% (ie, you have shelved shares) and your hashrate remains the same, and the pool wide hash rate does not change drastically, then your estimate will always be about the same. Period.
September 30, 2014, 10:24:12 AM
If you're hash rate doesn't change then your estimated change probably won't change much if you have shelved shares.... this is normal.
OK, but if the estimate is between 0.45x and 0.5x every 3 hours at my current has rate and in 5 hours what I had hashed is still the same, then there is something wrong.
September 30, 2014, 08:05:48 AM
If you're hash rate doesn't change then your estimated change probably won't change much if you have shelved shares.... this is normal.
September 30, 2014, 07:13:34 AM
I am finding that I hashing fine but most times the estimate change doesn't move for more than 5 hours. Something doesn't seem right. I have checked my neppys and they are all say their are hashing at 3.4TH/s so I just don't get it.
September 30, 2014, 03:39:07 AM
I'm having an issue with one of my miners and just wanted to check if anybody else has the same problem: All my miners which are directed to Eligius work well - only some which come from Bitmine start hashing properly, then, after a couple of hours, they disconnect and do not get into failover. They just produce heat. Nothing more. I tried now with other pools - and to my surprise, they hash away without any issues.
I see that only aboout 97% of the shares are being accepted, so I'm wondering as to where I have to start to find out why they always play "living dead" when connected with Eligius. I assume it may be an error with the miners, but which error.
Has anybody an idea or has had similar problems and found a solution?
I see that only aboout 97% of the shares are being accepted, so I'm wondering as to where I have to start to find out why they always play "living dead" when connected with Eligius. I assume it may be an error with the miners, but which error.
Has anybody an idea or has had similar problems and found a solution?
September 29, 2014, 08:27:57 PM
Ah yet another hash power buy sell place that makes no sense in practice...
Well whatever works.
Well whatever works.
ya doesn't make sense, i've been thinking about over n over and i have no clue why ppl would pay double what they can mine back for hash but i guess whatever i'll take it if they're willing to pay it...helps for diff. rate changes when luck goes to da crapper
ive thought about it too. I think they are speculating on coins...
September 29, 2014, 07:12:20 PM
Ah yet another hash power buy sell place that makes no sense in practice...
Well whatever works.
Well whatever works.
ya doesn't make sense, i've been thinking about over n over and i have no clue why ppl would pay double what they can mine back for hash but i guess whatever i'll take it if they're willing to pay it...helps for diff. rate changes when luck goes to da crapper
September 29, 2014, 04:32:01 PM
Ah yet another hash power buy sell place that makes no sense in practice...
Well whatever works.
Well whatever works.
September 29, 2014, 04:26:09 PM
Man people sure do freak when the stats aren't perfect...
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Hmm slush had a double orphan too...a bug must be going around
And with the hopping...I think it'll help cause nicehash isn't a pool, I'm selling my hash so luck doesn't matter
September 29, 2014, 01:11:25 PM
Man people sure do freak when the stats aren't perfect...
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Thanks for the update!
September 29, 2014, 01:01:42 PM
Man people sure do freak when the stats aren't perfect...
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Anyway, the double orphaned blocks caused a failsafe and the system is recomputing data and catching up as a result. No worries, as usual.
Jump to: