Pages:
Author

Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 11. (Read 458150 times)

newbie
Activity: 56
Merit: 0
As for changes to share difficulty, since ASICs do official dominate the mining scene, and most are substantially fast (minimum of a few Gh), I will be increasing the minimum share difficulty again soon, probably to 8.

128 please.
legendary
Activity: 1223
Merit: 1006
Greetings Eligius Miners!

*makes epic entrance of some sort* *poof*

OK, so, as of now, everything is in working order, and I will do my best to keep it that way.  Stats are working and caught up, the bulk of payouts are caught up (some normal blocks paid to failsafe since the large catch up payout, but I will get to those soon), NMC payouts are caught up (with a bonus to those who kept mining through the troubles), automatic payouts are working, and all seems well.

Thank you everyone for your generous donations.  They are much appreciate and will go towards further pool infrastructure improvements soon.

My girlfriend is also thrilled at the amount of support everyone has had for her while I've been glued to my keyboard fixing the latest issues and thanks everyone who donated.

----

Briefly addressing some posts... the 128/256 second hash rate calculations are actually almost passively calculated.  They are fed from the CPPSRB reward system code. Since it has to process every share anyway it's trivial to do some running hash rate calcs with little to no resource usage.

As for changes to share difficulty, since ASICs do official dominate the mining scene, and most are substantially fast (minimum of a few Gh), I will be increasing the minimum share difficulty again soon, probably to 8.

For vardiff, I don't want to lose any more stats resolution by slowing that down.

---

I will admittedly be taking a bit of a break from Eligius fix-ups for the moment... little burned out after this weekend.  But I'm going to be continuing to improve everything as possible.  I should have hardware for improving the web/stats server in the pipelines already which should help out with that load quite a bit soon.

Happy mining!

-wk
legendary
Activity: 2968
Merit: 1198
Well done WK, nice to see the stats working fully again.

+1!!!
legendary
Activity: 2968
Merit: 1198
bfgminer connects but does not find the blade as an device

You need to start bfgminer with --http-port, also make sure there is no firewall (iptables, etc.) blocking your miners from connecting to that port.

legendary
Activity: 2114
Merit: 1005
ASIC Wannabe
0.034 in 24 hours, it's look like some problem still here... and NMC...

Chamber pot with handle inward

seriously, go fuck yourself. you should not receive a bitcent of that payout considering the garbage you've filled this thread with over the past 3 days
legendary
Activity: 1652
Merit: 1029
Well done WK, nice to see the stats working fully again.
legendary
Activity: 1223
Merit: 1006
What exactly are you guys talking about?
newbie
Activity: 56
Merit: 0
0.034 in 24 hours, it's look like some problem still here... and NMC...

Chamber pot with handle inward

Yeah, I have the same thing, payout every day of .04-ish, but there is always a 0.04-ish balance.

Sometimes though, I get two payouts in one day. So, it's not too bad.

I think that's just the way wz computes it, at least for now. Maybe there are two separate data streams going to the payout server, your current payout and the currently running (in process) hashing.

At least, that's the way I'm reading it. I could be wrong. I have never been shafted by Eligius, and I doubt he's trying to shaft anybody.

I have enough problems keeping my mining gear going and not burning out any circuits....

I hope problem will be repaired soon.
hero member
Activity: 529
Merit: 501
0.034 in 24 hours, it's look like some problem still here... and NMC...

Chamber pot with handle inward

Yeah, I have the same thing, payout every day of .04-ish, but there is always a 0.04-ish balance.

Sometimes though, I get two payouts in one day. So, it's not too bad.

I think that's just the way wz computes it, at least for now. Maybe there are two separate data streams going to the payout server, your current payout and the currently running (in process) hashing.

At least, that's the way I'm reading it. I could be wrong. I have never been shafted by Eligius, and I doubt he's trying to shaft anybody.

I have enough problems keeping my mining gear going and not burning out any circuits....
legendary
Activity: 1246
Merit: 1001
0.034 in 24 hours, it's look like some problem still here... and NMC...

Chamber pot with handle inward

Eliza, is that you!
newbie
Activity: 56
Merit: 0
0.034 in 24 hours, it's look like some problem still here... and NMC...

Chamber pot with handle inward
full member
Activity: 168
Merit: 100
OK! Now it works with bfgminer !! Had to use the 32Bit Version! NOT the 64Bit .... Grin

Don't use bfgminer with blades or cubes. You'll lose a pretty significant amount of hashrate.

This depends on the computer you are running bfgminer or slush's proxy on. I had a significant drop in hash rate using BFGMiner with my blades on my Raspberry Pi. Currently I use an old Atom netbook for my mining (they are really cheap used/refurbished) and over the course of a week of mining I did not see a significant difference in my hashrate. BFGMiner uses a lot of CPU on my ten blade setup on that netbook, so I suspect the number of devices being proxied and the size of your processor are factors to consider.

In the very beginning on bfgminer I did have a really bad hash rate until I gave each blade a unique username/password. After that all was well.
full member
Activity: 184
Merit: 100
every-ting crisp, mon!

jah rastafari!
newbie
Activity: 5
Merit: 0
you will get some errors, not important


mining_proxy.exe -o stratum.mining.eligius.st -p 3334 -gp 8332 -sp 3333

config user:pass      YOUR Wallet ADDRESS HERE_Blade1:nopw

config port to  8332

config server to your computer IP address

config user:pass      YOUR Wallet ADDRESS HERE_Blade1:nopw


Somehow it works with: proxy.exe -o stratum.mining.eligius.st -p 3334

But get allot of warnings

This is the correct way to run it. Post your warnings. Probably normal behavior.
Here are the Errors:

2014-01-21 21:09:40,359 INFO proxy jobs.submit # Submitting d435eb0e
2014-01-21 21:09:40,359 WARNING proxy getwork_listener._on_submit # [0ms] Share from MY_ADDRESS
hero member
Activity: 616
Merit: 500
I got Satoshi's avatar!
Everything seems to be in order.. stats, graphs, payout queue etc.  Grin

Nice work WK!
newbie
Activity: 10
Merit: 0
OK! Now it works with bfgminer !! Had to use the 32Bit Version! NOT the 64Bit .... Grin

Don't use bfgminer with blades or cubes. You'll lose a pretty significant amount of hashrate.
legendary
Activity: 1652
Merit: 1029
I'm going to have to wait forever to see the 0.0001 btc that I might have mined.
newbie
Activity: 23
Merit: 0
my donation sent to 1StatsQytc7UEZ9sHJ9BGX2csmkj8XZr2
everyone should pitch in a little this is a worthy pool and the admin does not ask for much.
sr. member
Activity: 280
Merit: 250
OK! Now it works with bfgminer !! Had to use the 32Bit Version! NOT the 64Bit .... Grin
sr. member
Activity: 280
Merit: 250
Somehow it works with: proxy.exe -o stratum.mining.eligius.st -p 3334

But get allot of warnings

This is the correct way to run it. Post your warnings. Probably normal behavior.
Here are the Errors:

2014-01-21 21:09:40,359 INFO proxy jobs.submit # Submitting d435eb0e
2014-01-21 21:09:40,359 WARNING proxy getwork_listener._on_submit # [0ms] Share from MY_ADDRESS
Pages:
Jump to: