CKPool Stats - iPhone App

[vh]

Apple iPhone version for CKPool Stats is now available

This is the main thread to provide status and QA.  

Related Threads:
https://bitcointalk.org/index.php?topic=789369.0 kano.is
https://bitcointalk.org/index.php?topic=763510.0 solo.ckpool.org

CKPool Stats provides a portable view of key statistics from kano.is and solo.ckpool.org.

Current Release v1.2 adds:
- Worker transition to idle notification.
- Worker sorting by name / hash tapping.
- Badge notification for idle workers.
- api key QR reader.  

Release v1.1 included support for:
- Block solve / found notification.
- Payout notification (kano.is).
- Apple watch notification when paired.
- Pool statistics.
- API based worker statistics (kano.is).
- BTC address worker statistics.

https://itunes.apple.com/us/app/ckpool-stats/id1076177533?ls=1&mt=8



Troubleshooting steps:
1. Make sure you have internet access.
2. Make sure you allow notifications (do it right the first time).
3. Kano.is username(s) are case sensitive.

FAQ:
Q. There's a red badge on my icon with a number in it.  What is it and how do i clear it?
A. The number represents the count of idle workers seen in your watch list.   It will clear itself out when idle workers clear out.

Q.  How do I sort my workers by hashrate?
A.  Tap the hashrate of any worker.   It will sort ascending (yellow).  A second tap on the hashrate will sort descending (green).  Same applies to worker name.

Q. What is Direct Addresses?
A. That plus sign in configuration is for adding BTC based worker monitoring addresses.   It will be listed under Direct Addresses.
        1. use address.worker syntax (address only might work)
        2. swipe the added item to the left to get the option to delete typos.

Q.  What is the criteria for Trending Down?
A.  Subject to change: Trending Down is currently set to show worker where its 5 min hash is less than 85% of it's 24h hash.

Q.  The app link is reporting not available in my country.
A.  Try again in later.

Q.  Can I join beta to get a sneak peek at the next build.
A.  PM me an email.   You'll get added to apple's beta list for new build notification and early install.  


Known Bugs:
- Two stats pool mode covers up marquee on iPad mini.
  + Cleaned up in next build.    Workaround: Use four stats mode.


What's next in v1.3:
1.  Worker detail modal.
2.  More on/off buttons in the configuration section to customize.
3.  One or more misc todo.


Misc Todos:
1.  Summary group for DA
2.  iPad friendly(er)
3.  Multiple account support.
4.  Add worker name which found block.  (best effort)

Disclaimer:
The app is free, as such you can expect at a minimum you will get free quality support.
If you like the app and want to root for it's survival, support the dev license fee, or to just send a thanks,
    send donations to : 1CKaPP1wSBBfqhJB5uE7QBqyvEf2EBSjQe

[clgrissom3]

Nice work vh!  More stuff for our geek gadgets!

I really like the three worker screens for Hashing, Trending Down, and Idle.  It took me a second to figure that out.  I was wondering why one of my S5s (that's been down for 8 hours at the data center) was not showing up on the Hashing screen.

[d57heinz]

Very Nice App.. Appreciate it:)  sent you a small donation... https://blockexplorer.com/tx/f474c886d339ab1a59b90e6df4bb7661405e3bc848fa330b92847df8a9502562

Was wondering if your app will display who found the block?  Not sure if kano api provides those details i haven't used it. Maybe could scrape the blocks page for the data after a block found notification if the api does not...

Best Regards
d57heinz

[edonkey]

I've been playing with your app. Very nice so far.

Does the direct address feature support worker names appended to the BTC address in the usual form (i.e. address.workername)?

I accidentally created a blank direct address, but was able to delete it (based on your instructions in the first post). Maybe you could consider some basic validation when entering a new address?

Thanks for your efforts!

[jonnybravo0311]

Nice work!  I don't mine on the pools; however, I do support them.  I sent you a donation: https://www.blocktrail.com/BTC/tx/51b5f35ba32e93dcecf194e5803c1640b096b1b958f9e64c965e6fa31cbf285a

[ZACHM]

Very Nice App.. Appreciate it:)  sent you a small donation... https://blockexplorer.com/tx/f474c886d339ab1a59b90e6df4bb7661405e3bc848fa330b92847df8a9502562

Was wondering if your app will display who found the block?  Not sure if kano api provides those details i haven't used it. Maybe could scrape the blocks page for the data after a block found notification if the api does not...

Best Regards
d57heinz

I looked into doing this at one point, but the api does not support it and the block finder is not shown on the blocks page unless you are logged in.

[vh]

Glad to see it's getting some activity use and holding up so far.

re: tagging on block solver's name
- adding to todo.   not in api but doable and it will add to the excitement   i suspect kano is not displaying it on the home screen because of privacy respect.   if i get a request to not display, i'll end up removing it.

re: direct btc address.   yes it takes address_worker syntax.

re: donation.   cool.   appreciated and thanks.

[kano]

I added a qrcode of the API key to the "Account"->"User Settings" page coz it's a drag to have to type that whole key out
(I of course simply used a qr code reader to copy/paste into the configuration)

[kano]

Glad to see it's getting some activity use and holding up so far.

re: tagging on block solver's name
- adding to todo.   not in api but doable and it will add to the excitement   i suspect kano is not displaying it on the home screen because of privacy respect.   if i get a request to not display, i'll end up removing it.

re: direct btc address.   yes it takes address_worker syntax.

re: donation.   cool.   appreciated and thanks.

Um - it's not doable without a password - and as I've said on the login page, no one should be giving out their password.

Edit: also note that the API is pretty much fixed - but if you are screen scraping web pages, that will break if I change any of them and I'm not holding back web page changes to avoid breaking an app that scrapes a web page.

[vh]

I added a qrcode of the API key to the "Account"->"User Settings" page coz it's a drag to have to type that whole key out
(I of course simply used a qr code reader to copy/paste into the configuration)

If you do, i'll look into adding a QR scanner.   looks pretty basic.

[vh]

Glad to see it's getting some activity use and holding up so far.

re: tagging on block solver's name
- adding to todo.   not in api but doable and it will add to the excitement   i suspect kano is not displaying it on the home screen because of privacy respect.   if i get a request to not display, i'll end up removing it.

re: direct btc address.   yes it takes address_worker syntax.

re: donation.   cool.   appreciated and thanks.

Um - it's not doable without a password - and as I've said on the login page, no one should be giving out their password.

i summarize most stats via an aggregator for notification and the new https only requirements in xcode.   the app won't be requesting user passwords.    i would likely have to use my own and broadcast global values without others needed to do so.

[kano]

I added a qrcode of the API key to the "Account"->"User Settings" page coz it's a drag to have to type that whole key out
(I of course simply used a qr code reader to copy/paste into the configuration)

If you do, i'll look into adding a QR scanner.   looks pretty basic.

"added"

[kano]

Glad to see it's getting some activity use and holding up so far.

re: tagging on block solver's name
- adding to todo.   not in api but doable and it will add to the excitement   i suspect kano is not displaying it on the home screen because of privacy respect.   if i get a request to not display, i'll end up removing it.

re: direct btc address.   yes it takes address_worker syntax.

re: donation.   cool.   appreciated and thanks.

Um - it's not doable without a password - and as I've said on the login page, no one should be giving out their password.

i summarize most stats via an aggregator for notification and the new https only requirements in xcode.   the app won't be requesting user passwords.    i would likely have to use my own and broadcast global values without others needed to do so.

Yes I do understand how you can get around that - however I'm really not all that happy to have accounts on the pool that have known passwords ...

[vh]

Edit: also note that the API is pretty much fixed - but if you are screen scraping web pages, that will break if I change any of them and I'm not holding back web page changes to avoid breaking an app that scrapes a web page.

API has a implied contract with those of us who use it.    
Web scraping will definitely be unstable.   And more work for me, bad experience for end user.   Adding to wish list, and leaving at that until i ponder it more.

[densuj]

I hope in the future, you can support to android app too not only for iphone. Because many user who using android include me. 

[edonkey]

The worker stats works great for normal hash rate miners. But I have a pair of Compac stick miners pointing at ck's solo pool and they only show as "idle" with a hash rate of 0.

Sure the stick miners only produce about 16 GHs each, which is admittedly pathetic. But that's as fast as they go. In fact, they're overclocked

I expect that lots of us (including everyone in the Compac Solo Club) are pointing low hash rate miners at the solo pool. It would be nice if that was supported in your app.

[vh]

The worker stats works great for normal hash rate miners. But I have a pair of Compac stick miners pointing at ck's solo pool and they only show as "idle" with a hash rate of 0.

Sure the stick miners only produce about 16 GHs each, which is admittedly pathetic. But that's as fast as they go. In fact, they're overclocked

I expect that lots of us (including everyone in the Compac Solo Club) are pointing low hash rate miners at the solo pool. It would be nice if that was supported in your app.

it should be displayed.   put your worker name at the end of this url string, browse it and see if there's data.

https://www.kano.is/worker.php?a=

fix it first to get data and pm me the worker address if there's a mismatch.

[vh]

I hope in the future, you can support to android app too not only for iphone. Because many user who using android include me. 

Good Job to TheJesterOne for getting that one out, and for setting the bar for the ideas for this.
https://bitcointalk.org/index.php?topic=789369.msg11091187#msg11091187

I've fiddled with java, but not that great at it honestly. 

[vh]

Yes I do understand how you can get around that - however I'm really not all that happy to have accounts on the pool that have known passwords ...

i am truly shooting to keep everyone happy.  not everyone will win, but you do get priority .  will find a balance.

so after a bit of pondering i will leave data found behind passwords authentication alone.   
even though i can secure it with a point to point node and a single password guarded from the world.

my stance on screen scraping though:

i'm not against it to pick up public data so long as the site owner doesn't say go away.
screen scraping will continue to occur to pick up tidbits of neat data (aggregator/normalizer node - no change to code) from various places until the corresponding api data is available.

given that i will keep a sharp eye out for api updates as it is the better way to go.

user requests will be sorted into versions and wish-lists (todos) accordingly to not be forgotten about.

[edonkey]

The worker stats works great for normal hash rate miners. But I have a pair of Compac stick miners pointing at ck's solo pool and they only show as "idle" with a hash rate of 0.

Sure the stick miners only produce about 16 GHs each, which is admittedly pathetic. But that's as fast as they go. In fact, they're overclocked

I expect that lots of us (including everyone in the Compac Solo Club) are pointing low hash rate miners at the solo pool. It would be nice if that was supported in your app.

it should be displayed.   put your worker name at the end of this url string, browse it and see if there's data.

https://www.kano.is/worker.php?a=

fix it first to get data and pm me the worker address if there's a mismatch.

The addresses in question are on ck's solo pool, not kano's. Here's an example URL, including the address:

http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jan11edonkeystick

Maybe you can't monitor addresses on the solo pool? I tried to see if there was a different config if I selected the solo pool on the main page of the app, but it seems like there's a single configuration for the app for both pools.