I'm not sure what you have, but it is not a .csv
Topic: KanoPool Monitor - hashrates, workers, rewards and notifications for KanPool - page 6. (Read 45019 times)
March 10, 2016, 11:40:54 PM
Your file is not a valid .csv file, yours looks like this:
I'm not sure what you have, but it is not a .csv
I'm not sure what you have, but it is not a .csv
March 10, 2016, 11:31:50 PM
The import feature is finally here! 
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
I get this error after uploading the CSV file into your tool.
The file Rewards.csv has been uploaded.
Not a valid block number!
Fatal error: Call to a member function fetch_assoc() on a non-object in /homepages/8/d177552237/htdocs/zachmonroe/ckpoolmonitor/fileUpload.php on line 49
March 10, 2016, 10:08:46 PM
The import feature is finally here!
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
Very nice Zach!
March 10, 2016, 09:56:53 PM
You think Kano might provide the rewards data via API? That would be much easier for all I think
I asked one time in the past, but don't want to bother him about it.
Yes it would be easier, but I think in order to do it safely there would probably have to be a second API key for access to the rewards records.
But at the same time I don't think it would really matter, there isn't anything that can be done with the data, and the transactions are already public on the blockchain.
If he added it, I would assume it would only give the most recent reward info. But that would be enough.
March 10, 2016, 09:50:03 PM
The import feature is finally here!
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
You think Kano might provide the rewards data via API? That would be much easier for all I think
March 10, 2016, 09:43:42 PM
The import feature is finally here!
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
There may be some bugs to work out, but it seams to work right now.
You need to select the information from your rewards page and copy it to a spreadsheet program, then save it as a csv file.
It should look something like this:
The file name does not matter, except it needs to be a .csv extension
Then go to Your Rewards page and choose to upload the file.
It should enter those rewards in for you, it will check for duplicates so you don't need to worry about overwriting older entries.
Try it and let me know if you have any problems.
February 18, 2016, 09:54:09 AM
If I understand, you are no longer using AV6R1?
The worker graph does not really look at the worker names, it looks at their position in the results as stored in the database. So if AV6R1 was your last worker, then you stopped using that worker, your new worker would become your last worker. But the graph gets its worker name from the first record, so your old worker is on the first record it finds within the graphs timespan. Thereby displaying your new workers data with the old worker name, eventually the old worker will clear out.
It is something that I had planned on fixing, but had forgotten about it. Thanks for the reminder, I will get on it very soon.
The worker graph does not really look at the worker names, it looks at their position in the results as stored in the database. So if AV6R1 was your last worker, then you stopped using that worker, your new worker would become your last worker. But the graph gets its worker name from the first record, so your old worker is on the first record it finds within the graphs timespan. Thereby displaying your new workers data with the old worker name, eventually the old worker will clear out.
It is something that I had planned on fixing, but had forgotten about it. Thanks for the reminder, I will get on it very soon.
I used both of them but the stats has been interchange in the UI.
AV62 has been running for like 10 hours but it show days of stats ... AV6R1 show only the last 10 hours. It should be the other way around.
February 18, 2016, 12:16:01 AM
If I understand, you are no longer using AV6R1?
The worker graph does not really look at the worker names, it looks at their position in the results as stored in the database. So if AV6R1 was your last worker, then you stopped using that worker, your new worker would become your last worker. But the graph gets its worker name from the first record, so your old worker is on the first record it finds within the graphs timespan. Thereby displaying your new workers data with the old worker name, eventually the old worker will clear out.
It is something that I had planned on fixing, but had forgotten about it. Thanks for the reminder, I will get on it very soon.
The worker graph does not really look at the worker names, it looks at their position in the results as stored in the database. So if AV6R1 was your last worker, then you stopped using that worker, your new worker would become your last worker. But the graph gets its worker name from the first record, so your old worker is on the first record it finds within the graphs timespan. Thereby displaying your new workers data with the old worker name, eventually the old worker will clear out.
It is something that I had planned on fixing, but had forgotten about it. Thanks for the reminder, I will get on it very soon.
February 17, 2016, 11:17:26 PM
I think I found an issue.
I created a new worker named => AV62 and I have an older worker named => AV6R1.
The stats are shown incorrectly in the full details worker graph page.
The stats for worker AV6R1 are shown for the worker AV62.
Thanks ;-)
I created a new worker named => AV62 and I have an older worker named => AV6R1.
The stats are shown incorrectly in the full details worker graph page.
The stats for worker AV6R1 are shown for the worker AV62.
Thanks ;-)
February 11, 2016, 09:01:22 PM
I think I found him.
The comma in the hashrate was messing it up. Hopefully should be fixed now.
The comma in the hashrate was messing it up. Hopefully should be fixed now.
February 11, 2016, 08:20:16 PM
Can anyone find Waldo? Anything odd about this alert?
Your hashrate has dropped below your specified rate of 95.0000 TH/s!
Your latest 5 minute average rate is 2,913.8485 TH/s!
You will continue to get these notifications approximately every 5 minutes until your rate increases above your set minimum or you log in and change your settings.
Thanks for using CKPoolMonitor
Please be sure to login and verify your apikey and/or BTC address are valid.
Your hashrate has dropped below your specified rate of 95.0000 TH/s!
Your latest 5 minute average rate is 2,913.8485 TH/s!
You will continue to get these notifications approximately every 5 minutes until your rate increases above your set minimum or you log in and change your settings.
Thanks for using CKPoolMonitor
Please be sure to login and verify your apikey and/or BTC address are valid.
February 11, 2016, 12:53:01 PM
When the script that gets everyone’s data from Kano.is and processes it into my database runs it goes one by one through the users. There was an issue with a user’s account information and when the script got to that user it would die. I have since fixed the script, but any user after that one did not get recorded data from 2016-02-08 14:21 to 2016-02-10 04:01 UTC. Sorry about that, I am working on a way for me to be notified when things like this happen so I can fix them sooner.
February 11, 2016, 05:43:52 AM
Seems like there was a problem with recording hashrate on 9.feb.
I rented about 300 TH/s for a couple of hours, but it does not show in my hashgraph. I can see it in the shift-tab and shift-graph on the pool's site tho.
Send me a PM if you need more details, thanks!
-Tore
I rented about 300 TH/s for a couple of hours, but it does not show in my hashgraph. I can see it in the shift-tab and shift-graph on the pool's site tho.
Send me a PM if you need more details, thanks!
-Tore
February 10, 2016, 11:57:35 PM
Just a FYI for anyone that has Project Fi. They have finally created the email/SMS gateway. The address is: your10digit#@msg.fi.google.com
February 10, 2016, 12:08:04 AM
Just thought I'd share some updates:
- There was some issues with the primary script, I sorted those out so things should be running a little smoother.
- The graph and pay chart on the main page were not loading correctly, they have been fixed.
Currently there are about 160 active users using the monitor and we are tracking almost 7PH or about 30% of the hashrate on the pool.
If anyone notices any issues let me know.
Hopefully this coming weekend I will have some free time to cross some of the items off the to-do list.
edit:
I am still seeing some accounts where people have entered a username and BTC address, or some other combination. If you are mining on Kano.is with a username then only enter your username and API Key, DO NOT enter a BTC address. If you are mining with a BTC Address then only enter that, DO NOT enter a username or API Key. If you have questions or need any help you can ask here, pm me or send me an email.
- There was some issues with the primary script, I sorted those out so things should be running a little smoother.
- The graph and pay chart on the main page were not loading correctly, they have been fixed.
Currently there are about 160 active users using the monitor and we are tracking almost 7PH or about 30% of the hashrate on the pool.
If anyone notices any issues let me know.
Hopefully this coming weekend I will have some free time to cross some of the items off the to-do list.
edit:
I am still seeing some accounts where people have entered a username and BTC address, or some other combination. If you are mining on Kano.is with a username then only enter your username and API Key, DO NOT enter a BTC address. If you are mining with a BTC Address then only enter that, DO NOT enter a username or API Key. If you have questions or need any help you can ask here, pm me or send me an email.
February 08, 2016, 06:27:45 PM
Yeah, I should have realized it was going to do that.
You mentioned that you might have some gear for sale? I might be interested, could you send me a PM with what you have for sale?
You mentioned that you might have some gear for sale? I might be interested, could you send me a PM with what you have for sale?
PM me your list also
February 07, 2016, 09:18:56 AM
Yeah, I should have realized it was going to do that.
You mentioned that you might have some gear for sale? I might be interested, could you send me a PM with what you have for sale?
You mentioned that you might have some gear for sale? I might be interested, could you send me a PM with what you have for sale?
February 07, 2016, 09:15:54 AM
Yeah, woke up did a 2nd BLOCK dance while brushing my teeth and again was let down. =) Let's have a REAL block soon please.
February 07, 2016, 08:51:53 AM
Sorry about that one, I guess I can't remove the unworthy block from my database until we find another one.
February 05, 2016, 08:18:28 AM
Site is down, would appreciate a fix! 
Edit:
Aand its up.
Edit:
Aand its up.
Jump to: