[CLOSED] Semi-private mining pool

[elasticband]

Just as suggestion:
Idle worker notification is great. When I get It I always rush to see if everything is fine. And most of the times everything is already working when I connect.
Would it be possibile to get a "recovery" notification if the workers comes up again?

+1

[jamesg]

Just as suggestion:
Idle worker notification is great. When I get It I always rush to see if everything is fine. And most of the times everything is already working when I connect.
Would it be possibile to get a "recovery" notification if the workers comes up again?

+1

To clarify, you would like a setting on each worker that would notify you when a worker goes from idle to active?

[elasticband]

Yes.... when wr get an idle notify we run to out rigs only to find everyyhing is ok and they are online again.. so yes if they come online again after being inactive this woukd he nice to know

[michelet]

Yes.... when wr get an idle notify we run to out rigs only to find everyyhing is ok and they are online again.. so yes if they come online again after being inactive this woukd he nice to know

exactly.
Alternatively/additionaly it could be nice to set a timeout for the notification. (so you notify the worker is idle after x minutes)
That would reduce the amount of emails that are sent.

[elasticband]

Getting quite a large difference it pool estimates for my avalons, they tend to be quite even and balanced around 81-83gh on other pools, 93ghs from a overclocked 3 module batch 1 would be nice though

[elasticband]

A nice line graph displaying each workers hashrate would be cool instead of just the one line

[jamesg]

Getting quite a large difference it pool estimates for my avalons, they tend to be quite even and balanced around 81-83gh on other pools, 93ghs from a overclocked 3 module batch 1 would be nice though

Our pool targets less shares per minute (12) than other pools to further reduce data retention issues. The effect of this is that your 30 minute average will trend higher and lower than on other pools. This evens out over a couple of hours.

I do track hash rate histories by worker so I can add that to the dashboard. I'll see how soon I can get that up.

[jamesg]

Shifts have been moved to 50% of difficulty to accomodate the pools increasing growth. Also, bugs with shift creation have been resolved.

It should take approximately 500 minutes to fully "earn in" when first starting on the pool. This means it will also take 500 minutes for your earnings to stop after you leave the pool.

O, and we found 4 blocks in 1 hour! 

[jamesg]

Lots of firsts today including a hat trick (three blocks in a row), 5 of 6 consecutive blocks, and a block that took 3 seconds to find!   

Thanks to everybody for reaching out to join the pool and helping to make this such a fun project to run. I know I have more work to do on the pool, but it is nice to see these firsts rolling in.

[jamesg]

5 registration links are available for those who are over 200Gh/s.

[bitpop]

I'm making it my mission to get all the hashing power I can and boycott this cocky pool.

[Turbor]

I'm making it my mission to get all the hashing power I can and boycott this cocky pool.

  hashpower... separates the men from the boys !

[elasticband]

Getting quite a large difference it pool estimates for my avalons, they tend to be quite even and balanced around 81-83gh on other pools, 93ghs from a overclocked 3 module batch 1 would be nice though

Our pool targets less shares per minute (12) than other pools to further reduce data retention issues. The effect of this is that your 30 minute average will trend higher and lower than on other pools. This evens out over a couple of hours.

I do track hash rate histories by worker so I can add that to the dashboard. I'll see how soon I can get that up.

Any advance on displaying a progress chart of each worker or getting merged NMC mining running? I'm currently directing half my miners elswhere jut for the NMC really

[jamesg]

Any advance on displaying a progress chart of each worker or getting merged NMC mining running? I'm currently directing half my miners elswhere jut for the NMC really

I've been running around the country like a mad man for the last little while getting Teramining up and running and haven't had much time for programming. This will change once I get back from the Bitcoin conference in New York. I'll also be interviewing firms to continue development without me being the roadblock to getting shit done.

I'm fairly confident that per worker stats should be very low hanging fruit. Just so everyone is aware, this is currently what is on my development list.

• Blocks in the last 24 hrs. on Stats page
• Change "View All Blocks" to "Block Details" on Stats page
• Payout threshold setting for automating payment requests.
• Add ability to show stats per worker
• Worker Recovery notification
• Speed up hash rate and shares submitted graphs
• NMC merged mining

Best,
James

[allinvain]

I'm making it my mission to get all the hashing power I can and boycott this cocky pool.

Lol, why? What's your beef with this pool? Did this pool run over your dog or call your girlfriend fat?

[Omen1855]

As promised I've added some multi-avalon power to the mine. This pool's hashrate is exploding

[Morblias]

What's up with that latest block showing the pool at 1.09Ph/s and 100% CDF? lol

[wknight]

100%.. yup.. long rounds broke the server

[jamesg]

100%.. yup.. long rounds broke the server

Pool had a little hiccup last night. All has been corrected and should be showing the proper information now.

[jamesg]

I've made some updates to the pool interface.

• Show the number of blocks found in the last 24 hrs. on the main stats page.
• Upgraded all bitcoind instances to 0.8.3
• Payout threshold setting in the settings area for automating payment requests. Set to 0 to disable automated payout requests.
• API key creation / reset under settings along with access to any url under /statistics

More to come tomorrow

Edit: When using your api key with the /statistics area, you can append a .json to any url to get back JSON data instead of a web page.

Ex. /statistics.json?apikey=yourapikey