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

[wizkid057]

So the pool is handling that?

What kind of connection does the server have? Seems like a powerful server.

The pool server is actually a very nice machine with very good connectivity.  I won't release full/exact specs, though, as I don't want anyone to consider it a "challenge"...

Have you considered getting rid of getwork (and the botnets) and just do Stratum and GBT?

Yes, but, we probably won't be disabling getwork.  We still have many miners who are happily mining away at just a few Mh/sec or so using getwork.  I see no reason to penalize them because someone doesn't configure their botnet efficiently.

P.S. - I need a raise.

Nice work . Can only give you a small bit of your raise ghehe...

Thank you for the tip!  It is greatly appreciated.

I'm actually spending the remainder of my weeking working on the "My Eligius" control panel.  Probably won't finish it, though.  I had planned to spend the majority of my free time this weekend working on it, however, but, alas, keeping the pool running was a higher priority.

Thanks everyone for your patience!

Happy mining.

-wk

[1714898850]

1714898850

[1714898850]

1714898850

[jgarzik]

* jgarzik votes for a fixed minimum difficulty which is out of reach of most CPU miners, as well as eliminating getwork.

GBT or stratum only.

But just an opinion.    Looking forward to the control panel.

[Luke-Jr]

I'd suggest perhaps making it GBT/Stratum only on the main node, and offering a private getwork port to miners on request.
Only potential problem is, most likely miners using getwork are also the ones who don't pay any attention :|

[Shevek]

Stats are broken:

Error: Username 1xxxxxxxxxxxxxxxxxxxxxxxxxx not found in database. Please try again later. If this issue persists, please report it to the pool operator.

[ThunderSheep]

I was seeing this too for about 20 minutes but it seems better now.
-Sheep

[wizkid057]

Stats are broken:

Error: Username 1xxxxxxxxxxxxxxxxxxxxxxxxxx not found in database. Please try again later. If this issue persists, please report it to the pool operator.

I was seeing this too for about 20 minutes but it seems better now.
-Sheep

Sorry folks, I was trying to track down a bug in stats which is causing it to use more sql connections than needed.

[bitcoindaddy]

* jgarzik votes for a fixed minimum difficulty which is out of reach of most CPU miners, as well as eliminating getwork.

GBT or stratum only.

But just an opinion.    Looking forward to the control panel.

Seconded.

[purelithium]

Why won't this block die!

I think it did just as I posted this :S

[purelithium]

Anyone else notice that the user stats are "stalled"? Mine have the exact same hashrate listed for the past 4 hours or so.

[WynX]

Yep same here. Some of my miners also swapped pool (probably unrelated).

[AlexanderB]

Hey guys, new to the pool, and mining happily.

Noticed the stats page freezing today, it seems to be okay now..

[wizkid057]

Anyone else notice that the user stats are "stalled"? Mine have the exact same hashrate listed for the past 4 hours or so.

Noticed the stats page freezing today, it seems to be okay now..

Been working on a resources balancing act with the stats.  I think I'm going to try to get some actual load balancing going with them very soon, likely moving stats to another server entirely to save resources on the main server.  My priority is keeping the pool itself operation, with stats secondary.  The stats always catch up even if they go down or "stall" for a while, so, I keep them as a secondary priority.

Thanks for the support!

-wk

[organofcorti]

Been working on a resources balancing act with the stats.  I think I'm going to try to get some actual load balancing going with them very soon, likely moving stats to another server entirely to save resources on the main server.  My priority is keeping the pool itself operation, with stats secondary.  The stats always catch up even if they go down or "stall" for a while, so, I keep them as a secondary priority.

Thanks for the support!

-wk

I meant to post a thank you ages ago - you've kept the Eligius stats page stable and easy to scrape. I haven't had to touch the weekly stats scripts since you took over. So thanks for doing a great job, and I hope some of your miners are donating to help support the work you do. There's a lot to like about this pool.

[wizkid057]

Been working on a resources balancing act with the stats.  I think I'm going to try to get some actual load balancing going with them very soon, likely moving stats to another server entirely to save resources on the main server.  My priority is keeping the pool itself operation, with stats secondary.  The stats always catch up even if they go down or "stall" for a while, so, I keep them as a secondary priority.

Thanks for the support!

-wk

I meant to post a thank you ages ago - you've kept the Eligius stats page stable and easy to scrape. I haven't had to touch the weekly stats scripts since you took over. So thanks for doing a great job, and I hope some of your miners are donating to help support the work you do. There's a lot to like about this pool.

Thank you for the encouragement!

I guess you won't need to change much even when I finally finish the official stats API.

[organofcorti]

Been working on a resources balancing act with the stats.  I think I'm going to try to get some actual load balancing going with them very soon, likely moving stats to another server entirely to save resources on the main server.  My priority is keeping the pool itself operation, with stats secondary.  The stats always catch up even if they go down or "stall" for a while, so, I keep them as a secondary priority.

Thanks for the support!

-wk

I meant to post a thank you ages ago - you've kept the Eligius stats page stable and easy to scrape. I haven't had to touch the weekly stats scripts since you took over. So thanks for doing a great job, and I hope some of your miners are donating to help support the work you do. There's a lot to like about this pool.

Thank you for the encouragement!

I guess you won't need to change much even when I finally finish the official stats API.

API for blocks history? Sweet! CSV or JSON?

[wizkid057]

I guess you won't need to change much even when I finally finish the official stats API.

API for blocks history? Sweet! CSV or JSON?

I was actually going to make it configurable as either JSON, CSV, or tab-delimited text, along with options for limitting the query (minheight=210000, for example), as well as customizing the fields output.

There will be APIs for detailed block data (including all payouts and other data available for each block if desired), data for all manually sent payouts, as well as various individual and aggregated miner stats (pool-wide and individual hashrate datas dating back over a year, share counts per timeframe on a pool-wide of individual basis, etc).

I'm pretty ambitious, and I plan on having this be the most comprehensive pool API ever.

P.S. - The code which outputs this data will be open source also.

[iambaboon]

Where is the 'Like' button !

[purelithium]

Where is the 'Like' button !

Hopefully soon we'll have the tip bot like the bitcointip bot on reddit. It'll make "liking" someone's post a lot easier!

[phrozenspite]

anyone else noticing their stats page not updating? or is that just me at the moment. 

[Subo1977]

anyone else noticing their stats page not updating? or is that just me at the moment. 

me too