Major updates

1. Added "Enable" check box in the API tokens setup.
If you do not want to monitor a pool, just uncheck the check box so that the API token of the pool is retained.
(Only available for web version, not for mobile)

2. Auto-refresh, stopping
At the bottom of the page, there is a check box to allow you to stop the auto-refresh.
Check it again to allow auto-refresh.

3. Added a "Page generated" date and time.

4. Miners are sorted by name and aligned left for a more organised look.

For the technies, programmers:

5. Implemented factory design pattern.
Allows easy adding of new pools

6. Refactored MVC codes.
Less repeated codes. Makes for easier and faster changes (whatever it may be).

I was wondering why would the json api for all pools be "happy"...

Hi Ed,

Do you mean to provide a JSON API to show the information of all the pools?

Hi,

In the JSON API for user stats, "estimated_reward" is spelt as "estimated_reword".

Regards,
Koo

You can run another instance with '-f 50'. And point it to a different pool.

So it will chuck along at very low hashrate. When the '-f 5' instance is not eating up GPU cycles, the '-f 50' will spring up to take over.

When the '-f 5' pool comes back to life, the '-f 50' will drop back to about 100kh/s (estimate).

So if you have 3 GPUs, you should be running 6 instances of poclbm.

Also, I'll pimp my site here www.btc-poolwatch.com .With this, you can monitor multiple pools easily and see how your multi-pool workers are performing.

Thanks, Nasty.

BTW, I have implemented a new feature to turn-off monitoring of some pools, but keep the API keys, to make our life easier.

The has been tested in my test site by beta tester (erm 1 beta tester). I will move this to LIVE tonight or over the weekend.

Sorry for the delay on this. Just got a pre-owned 5870 and was busy with upgrading my rigs to 11.6. A man's gotta eat.

ps. I've got a few donations (4 so far...), and if you have donated, please PM me and I can give you the link to the beta site so you can get a first hand view of up-coming features.
Just PM me with the donation transaction code.

Regards,
Koo

updated with new screen shots in first post.

Miners are still ok.

Only webfront is down.

Inaba, you already pay for the server charges and SMSes charges. So I don't think you should incurr any more cost running the pool.

Just put the 1% as bonus for the block finder. 1% is 0.5BTC? Will be significant to those with < 1ghs.

index the tables? 

Hi guys,

I've added Mainframe MC to www.btc-poolwatch.com

If you mine at multiple pools, this should be useful to you.

The main page auto-refreshes every 5 minutes.

If you point your iphone/android phones to it, it will be formatted to 320px width so everything displays nicely.

Hope you guys like it.

Regards,
Koo

Is there something wrong with the email contents?

I got the following emails (title):

Block #136901 has been solved!
Block #136900 has been solved!
Block #136838 has been solved!
Block #136731 has been solved!

It doesn't tally with the stats page.

Added Mainframe MC!

Regards,
Koo

Damn you pool-hoppers!! *shakes fist*

ok, I'll think of something.

Will do tonight while I wait for DNS propagation.

The pool stats cache have had a hit rate of about 85%! That is very good and I'm happy with that.

Next to-do is to move to a different host before I implement anything new things in the database to minimize migration headaches.

The top miners info is off by 1 decimal point. I'm hashing at 24ghs..LOL

Nice! I'm only getting < 0.1% stales. I never knew that.

Thanks for your support!

To use this on different browser/device, you will have to go through the pain of copying and pasting all the APIs.

The way to solve this is to assign each user a user token, like the API token that stores all the pool tokens. But this will take some time to implement.

In the mean time, if you have to manage multiple API Tokens, what I'll do is email all the tokens to myself, so that I don't need to login to various pools to copy the tokens.

On each device, I just open up the email and do a copy and paste. Hope this helps.

Regards,
Koo

nah, purely server side problem. It's up after a reboot.

I think I'll put getting stable hosting as top priority