[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[andrey2345]

Hello! What is the namecoin payout threshold? I dont get any namecoins for a few days now...

[spooderman]

Also, how is it 105% PPS NMC? Are you like....giving us NMC for free?

[ssateneth]

Eligius has a large buffer of namecoins built up from earlier merged mining, likely from people who haven't set a NMC address. It can afford to pay you extra NMC at the expense of the NMC buffer getting smaller.

[helmax]

sorry eligius i like this pool
but 10% hw is a lot
some people like me will change pool

[kendog77]

I wish the Knc firmware came with cgminer and bfgminer.

I suspect bfgminer will not have the same issue with November Jupiters.

[Biffa]

I wish the Knc firmware came with cgminer and bfgminer.

I suspect bfgminer will not have the same issue with November Jupiters.

You can get bfgminer if you install Bertmod 0.4

[Biffa]

Following up my earlier post about KNC...

Still not able to duplicate any issues on any devices I have ssh'd into.  Several folks have run their own tests with varying results which I'm looking into.

Hi

Just tried switching from Elgius to BTCGuild and HW errors went down from 12% to 2% and has been stable at 2% over the past 15 hours.

This only affects the faster running Nov Jupiter @ 650GH/s+

Gonna try slush's next as I'm not comfortable with the size of either BTCG or GHash.io

[robix]

Following up my earlier post about KNC...

Still not able to duplicate any issues on any devices I have ssh'd into.  Several folks have run their own tests with varying results which I'm looking into.

Hi

Just tried switching from Elgius to BTCGuild and HW errors went down from 12% to 2% and has been stable at 2% over the past 15 hours.

This only affects the faster running Nov Jupiter @ 650GH/s+

Gonna try slush's next as I'm not comfortable with the size of either BTCG or GHash.io

Slush has the same effect. Way less HW errors and higher hashrate.

[kendog77]

I tried a November Jupiter again this morning at Eligius, and it still has many hardware errors and pool rejects.

I also have an October unit mining at Eligius that is working perfectly.

[wizkid057]

KNC has even said that pool choice effecting HW error rate "does not make sense".

So, it definitely has to be a software (cgminer) problem somewhere, likely with something very subtle.

I would suggest anyone having this issue upgrade to the latest bfgminer and use that instead.  The KNC driver for bfgminer was written independently of cgminer and reportedly does not have any issues with any pools. (Latest version)

-wk

[wizkid057]

Following up since I responded before checking all messages on IRC.

Seems a few people have done some tests on their own using bfgminer, with a mod to work around the bug with the latest jupiter's i2c issue.

Results were pretty solid that cgminer has to be the cause of the misreported HW errors.  My 'out in left field without looking at the code closely' guess is that somewhere along the line is it losing work it generated and when it goes to do the recheck it is checking using the wrong work, thus misinterpreting it as a HW error and consequently not submitting the should-be-valid share to the pool, resulting in a lower hashrate.  This is not a problem with Eligius or any pool and is a problem with the stock software.

Also, contrary to the crazed reports all over, this issue is not consistent, not with Eligius or any other pool.  So, enough with trying to blame Eligius for this.

I'll try to see if Luke-Jr can push a fix for the latest bfgminer so that people can switch to bfgminer to fix the issue on the latest jupiters.

-wk

[robix]

@wizkid

Thanks for your endeavor and your explanations. I think you misunderstood something, and I think, I speak for the other KnC Nov rig owners also, no one blamed or wanted to blame you or the pool. We just stated that there is a problem, but did not claim that it's a problem of the pool itself.

Eligius is a fine pool. Keep up your good work and, again, thanks for your work.

[kendog77]

@wizkid

Thanks for your endeavor and your explanations. I think you misunderstood something, and I think, I speak for the other KnC Nov rig owners also, no one blamed or wanted to blame you or the pool. We just stated that there is a problem, but did not claim that it's a problem of the pool itself.

Eligius is a fine pool. Keep up your good work and, again, thanks for your work.

I agree. I don't think the problem is with the Eligius pool, but unfortunately the pool ends up taking a hit when the fastest mining rigs on the market don't work well with it using default, non hacked, firmware. The reason November Jupiters don't work well with the pool is kind of irrelevant.

I love the pool and will be back when Knc issues a firmware fix.

[wizkid057]

@wizkid

Thanks for your endeavor and your explanations. I think you misunderstood something, and I think, I speak for the other KnC Nov rig owners also, no one blamed or wanted to blame you or the pool. We just stated that there is a problem, but did not claim that it's a problem of the pool itself.

Eligius is a fine pool. Keep up your good work and, again, thanks for your work.

I agree. I don't think the problem is with the Eligius pool, but unfortunately the pool ends up taking a hit when the fastest mining rigs on the market don't work well with it using default, non hacked, firmware. The reason November Jupiters don't work well with the pool is kind of irrelevant.

I love the pool and will be back when Knc issues a firmware fix.

Well, there are in fact people using this issue with KNC devices to pull people away from Eligius for whatever

That's the thing, the KNC devices do work well with it, as there are quite a few mining Eligius, including many November ship jupiters.  There are only a handful of people actually experiencing this issue.

Its definitely not related to the pool and I'm sure you're not actually getting better long-term hash rates elsewhere.  The issue is with the hardware/software.  Any illusion otherwise just means you either didn't test long enough, just got lucky/unlucky, or your pool is lying about or miscalculating your hash rate.  (Eligius bases this directly on shares accepted, as it should.)  If your Nov. jupiter gets high HW errors on Eligius, then based on my tests (of over a dozen jupiters now, thank you very much for the support folks) it does everywhere else also.  There's no difference in the data sent from Eligius than there is from any other pool aside from the obvious (who gets paid for found blocks).

It's been confirmed that the same issue that affected some Avalon users a while back with Eligius regarding a large coinbase transaction does not affect KNC units as they have tons of CPU headroom. (I tried with a coinbase transaction 50x larger than Eligius's allowed max and KNC devices didn't even flinch.)

Spoke with someone from KNC and they say the issue is likely related to the DC to DC converter temperature, which would explain why the issue is intermittent.

-wk

[wizkid057]

Greetings miners,

So, on to some minor fixes/changes.

Since I dropped the minimum payout amount down to 40 TBC (~0.04 BTC) the coinbase/generation transaction has been reaching the set maximum outputs almost every block.  This means that the balance ends up in the pool's cold wallet and needs to be paid manually later (which I have been doing).

In an effort to address this without increasing the size of the coinbase transaction (which can cause problems with miners that have low memory or slow hosts) I've modified the way the coinbase transaction is created slightly with regard to the payout queue.

Here is how it worked previously:

• Sort addresses in queue by balance age, oldest to newest
• Pay addresses until either the full coinbase/reward amount was consumed or 128 outputs were paid
• If less than the full reward were consumed, and less than 2000 TBC remain, send the balance to the offline "change" address.
• If more, pay 2000 TBC to the offline change address, balance to the main offline wallet

Now it works like this, changes highlighted in green:

• Sort addresses in queue by balance age, oldest to newest
• Pay addresses until either the full coinbase/reward amount was consumed or 100 outputs were paid
• If less than the full reward were consumed, re-sort the addresses in queue, highest balance to lowest balance
• Pay addresses until either the full coinbase/reward amount was consumed or 28 outputs were paid
• If less than the full reward were consumed, and less than 2000 TBC remain, send the balance to the offline "change" address.
• If more, pay 2000 TBC to the offline change address, balance to the main offline wallet

This has the effect of better filling the coinbase/generated payout transaction with more miners that are due payouts by effectively allowing miners with the largest balances due to jump ahead in the queue, only when needed, to better pay the full block reward directly to miners, instead of to a pool offline wallet for manual payment.

Summary: The payout queue should be paid out automatically the majority of the time and faster than it has been with less manual payouts needed.  More fresh coins for miners.

Happy mining!

-wk

[GigaWave]

I didn't read the KNC issues in detail. But one issue I seem to be having lately is if the 'pool difficulty' is high for my device, it seems more likely to crash(Temperature runs higher). Which requires a full power down of the device(BFL 60GH).  I'm looking forward to the set-able difficulty, so I can do some testing.

[Luke-Jr]

I didn't read the KNC issues in detail. But one issue I seem to be having lately is if the 'pool difficulty' is high for my device, it seems more likely to crash(Temperature runs higher). Which requires a full power down of the device(BFL 60GH).  I'm looking forward to the set-able difficulty, so I can do some testing.

Difficulty does not affect devices at all.
Even if you could set difficulty, it is unlikely to allow setting it lower than the automatic variable difficulty (which is lower than most pools use on Eligius).

[helmax]

@wizkid

Thanks for your endeavor and your explanations. I think you misunderstood something, and I think, I speak for the other KnC Nov rig owners also, no one blamed or wanted to blame you or the pool. We just stated that there is a problem, but did not claim that it's a problem of the pool itself.

Eligius is a fine pool. Keep up your good work and, again, thanks for your work.

thats it

people only want kncminers works good here

[jgarzik]

coinbase payouts do not matter to me...  I would rather have regular-sized payouts that reduce dust in the wallet (more friendly to the network).

i.e. payout at 0.1 BTC threshold.

Any chance of having that option?

Implementing that would have the side effect of not needing to put a set of addresses in the coinbase.

[twmz]

coinbase payouts do not matter to me...  I would rather have regular-sized payouts that reduce dust in the wallet (more friendly to the network).

i.e. payout at 0.1 BTC threshold.

Any chance of having that option?

Implementing that would have the side effect of not needing to put a set of addresses in the coinbase.

minimum payout can be configured here (I have mine set to 0.2):

http://eligius.st/~wizkid057/newstats/mystats.php?cmd=options