Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB

[freebit13]

Looks like this thread has turned into a lot of non-Eligius specific speculation... wonder if a mod could split some of this off.

Isn't this a self-moderated thread?

 

[1715046867]

1715046867

[1715046867]

1715046867

[1715046867]

1715046867

[wizkid057]

Looks like this thread has turned into a lot of non-Eligius specific speculation... wonder if a mod could split some of this off.

Isn't this a self-moderated thread?

 

Yeah, but can only delete posts.  I don't consider the discussion useless, just not on topic... would rather a mod pull it elsewhere.

[blubberli]

But a guy on IRC was selling it super cheap... 10000 NMC per liter.

ROFL, now you got me, Eligius Pool forever. All hail the wizkid!

[DaveF]

So, NMC payouts would be next?

SCNR 

Decided NMC would be better spent on more unicorn blood...

[/troll]

http://www.thinkgeek.com/product/e5a7/

Heh.

-Dave

[mdude77]

Maybe it's not malicious activity?  Maybe there's something wrong with some piece of software being used?

For example, I have a number of S1s running through a Stratum proxy.  How can I verify it's properly feeding random work to all the ants, and half of them aren't working on the same thing the other half are working on?

M

[wizkid057]

The pool does this by using unique extranonce/coinbase data for every connection.  It also checks for duplicate submissions.

[mdude77]

The pool does this by using unique extranonce/coinbase data for every connection.  It also checks for duplicate submissions.

I'm only using one connection, that's why I'm using the proxy.  How would I know if I was getting duplicate submissions?  I don't recall seeing rejects/dupes/stales anywhere in the stats.  Presumably the proxy would tell me if something was rejected.  And presumably I'd notice if my payout wasn't in line with my hashrate.  Assuming that dupes/rejects are properly not included in my shares.

What about the S1 itself, or any other large mining equipment?  Has anyone reputable audited the output of the S1 to make sure all is copacetic?  200gh/s (OCd) is a lot of hashes to verify everything is working right.  Has anyone fed it controlled data and verified the output is sufficiently random to indicate it's working properly?  I think I know enough about mining works to think that a hash is a hash is a hash, so if it appears to be generating good hashes, presumably at sometime it would generate a hash that equates to a block?

Just thinking out loud here.

M

[CydeWeys]

The pool does this by using unique extranonce/coinbase data for every connection.  It also checks for duplicate submissions.

What about the S1 itself, or any other large mining equipment?  Has anyone reputable audited the output of the S1 to make sure all is copacetic?  200gh/s (OCd) is a lot of hashes to verify everything is working right.  Has anyone fed it controlled data and verified the output is sufficiently random to indicate it's working properly?  I think I know enough about mining works to think that a hash is a hash is a hash, so if it appears to be generating good hashes, presumably at sometime it would generate a hash that equates to a block?

A hash is a hash is a hash.  In fact, each difficulty level 1 mining pool share is equivalent to finding a block at difficulty level 1.  It's trivially easy to determine that any given share is valid, and in fact, all mining pools do this for all shares.  Shares that are invalid are rejected and don't count towards your indicated hash rate.  So your indicated hash rate is your real hash rate.

There's nothing to worry about.

[Ties42]

Is it normal that I get in and out of the payout queue? At various points it shows a remaining 0.000000BTC remaining to get in the payout queue and sometimes it shows an XX amount of block to get my payout. It already went back and forth a few times so far.

[wizkid057]

Payout queue all caught up.  Stats should reflect it shortly.

7.07789204 BTC (230.014 TBC) in manual payments applied to balances from tx 17c78b73ac0d43417a1ca47ca8e97ccce8c44e7a44e62c8eeaffaf3152a9107c
98.98896096 BTC (2405.2 TBC) in manual payments applied to balances from tx 68dae8dacd84ab03ccd7c966434f1748a3b41b85670f8b128bd9909baf9a3857
1612.60043849 BTC (2588.4 TBC) in manual payments applied to balances from tx c553073799d6f2df123444aa907983768721a8815ee7f05725339734cbf533b8

[rausvi15]

Your approximate maximum potential earnings at the current network difficulty of 6,119,726,089.13 and maintaining your 3-hour average hash rate of 2,537.43 Gh/s is 0.20852384 BTC per day.

but more then 3 weeks i have :
Shares Rewarded
   85.24%??

and round Luck is always more then 100% ..150...300....600%...

[baddw]

The pool does this by using unique extranonce/coinbase data for every connection.  It also checks for duplicate submissions.

I'm only using one connection, that's why I'm using the proxy.  How would I know if I was getting duplicate submissions?  I don't recall seeing rejects/dupes/stales anywhere in the stats.  Presumably the proxy would tell me if something was rejected.  And presumably I'd notice if my payout wasn't in line with my hashrate.  Assuming that dupes/rejects are properly not included in my shares.

What about the S1 itself, or any other large mining equipment?  Has anyone reputable audited the output of the S1 to make sure all is copacetic?  200gh/s (OCd) is a lot of hashes to verify everything is working right.  Has anyone fed it controlled data and verified the output is sufficiently random to indicate it's working properly?  I think I know enough about mining works to think that a hash is a hash is a hash, so if it appears to be generating good hashes, presumably at sometime it would generate a hash that equates to a block?

Just thinking out loud here.

M

The hash verifies the block, and the block verifies the hash.  (Otherwise the hash is just a bunch of random letters and numbers, unrelated to anything.)  The block includes the nonce that is generated by your miner.  Each share that you submit to the pool must include both the hash and the un-hashed nonce*.  Otherwise you could be submitting nonsense to the pool and getting credit for it.  It's easy for the pool to verify that the shares that you submit are valid hashes of valid blocks.

*and other info maybe?  Or does the pool just need the nonce, and all the rest of the block is pre-determined? I suppose it depends on the mining connection protocol: Stratum is pre-determined while GetBlockTemplate needs more?

[mdude77]

Your approximate maximum potential earnings at the current network difficulty of 6,119,726,089.13 and maintaining your 3-hour average hash rate of 2,537.43 Gh/s is 0.20852384 BTC per day.

but more then 3 weeks i have :
Shares Rewarded
   85.24%??

and round Luck is always more then 100% ..150...300....600%...

Not sure where your luck numbers are coming from.  According to my calculations:

last 10 blocks: 55.3%
last 12 hours: 44.63%
last 24 hours: 40.45%
last 7 days: 89.53%
last 30 days: 90.87%
last 90 days: 95.05%

for reference, BTC Guild is at 96% for 90 days and 100% for 180 days.

M

[davebodger]

Is it normal that I get in and out of the payout queue? At various points it shows a remaining 0.000000BTC remaining to get in the payout queue and sometimes it shows an XX amount of block to get my payout. It already went back and forth a few times so far.

Yes, normal, I've had this several times.
It's where the estimate of your next payment varies slightly as time goes on and you are on the edge of the block, as I understand it.
Not to worry, if you don't get paid this block then you are well positioned to be paid, almost certainly, next block, assuming no untoward events, such as an orphan.

[baddw]

Is it normal that I get in and out of the payout queue? At various points it shows a remaining 0.000000BTC remaining to get in the payout queue and sometimes it shows an XX amount of block to get my payout. It already went back and forth a few times so far.

Yes, normal, I've had this several times.
It's where the estimate of your next payment varies slightly as time goes on and you are on the edge of the block, as I understand it.
Not to worry, if you don't get paid this block then you are well positioned to be paid, almost certainly, next block, assuming no untoward events, such as an orphan.

Or a whale (whose last payout happens to be older than yours) hitting their threshold, so they take up the next several blocks.

[AbiTxGroup]

Something is up with the pool reporting hash rates.  All of my miners are still connected to Eligius but their hash rates reported are dropping fast.  I also notice that we have lost 1PH/s to the pool overall.

Locally, each of my ASIC miner shows their normal hash rate and all of my GPU miners are doing fine on their appropriate scrypt pool. 

My ASIC miners have not been changing to their backup pools either.

Internet connection on my side shows good and I have 8mbps down and 1.5mbps up according to speakeasy speed test.

The only traffic outbound at my router is the miners and now this laptop that I am using atm.  Network traffic monitoring shows nothing unusual here.

I switched a miner of to its backup pool to check out the hash rating there, but it will take a while to ramp up.

Anyone else seeing any problems with hash rate reporting?

[inzli]

Something is up with the pool reporting hash rates.  All of my miners are still connected to Eligius but their hash rates reported are dropping fast.  I also notice that we have lost 1PH/s to the pool overall.

Locally, each of my ASIC miner shows their normal hash rate and all of my GPU miners are doing fine on their appropriate scrypt pool.  

My ASIC miners have not been changing to their backup pools either.

Internet connection on my side shows good and I have 8mbps down and 1.5mbps up according to speakeasy speed test.

The only traffic outbound at my router is the miners and now this laptop that I am using atm.  Network traffic monitoring shows nothing unusual here.

I switched a miner of to its backup pool to check out the hash rating there, but it will take a while to ramp up.

Anyone else seeing any problems with hash rate reporting?

I can confirm this. Same situation here with 9 miners. Switched one miner to another pool where the hash rate is shown as it should be.

[azdarknet]

I have a nice strait graph and constant hash speed for the last few days since my last change, so its clearly not pool wide.

[lowerjerzey]

I have a nice strait graph and constant hash speed for the last few days since my last change, so its clearly not pool wide.

Yeah it is pool wide. Go here and check any contributor, do the top 5. They each have dropped. Let's see your graph.

http://eligius.st/~wizkid057/newstats/topcontributors.php

[wizkid057]

The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/