Clipse,
I'm not part of the BTC-Poolwatch project, so don't consider it 100% apparent that they wouldn't want to add such features. I was simply supplying reasons why it isn't feasible with the current setup and why it wouldn't necessarily be a great idea to do such a thing on a mass scale anyway (even an open-source tool for individuals to do this could end up taking down a pool the same way a DDoS attack could if it started spreading like wildfire, much like hoppers sometimes bring down a pool by monitoring it heavily while not even hashing at it).
Dustin
Topic: *BTC Poolwatch* - no new dev for now - page 5. (Read 33495 times)
rearwheels would you be willing to add some basic earnings/accounting section.
Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
Yours isn't the first request for a feature that would require the server to store our information and poll our data whether we are actually using the page or not. It probably won't be the last either. That said, if you had read through the thread, you would have learned that our API keys are stored ina cookie on our computer and the data from the servers is only retrieved from the pools when we request it by loading the page. Given those two constraints, there is no way he can tell you what you earned in the last 24 hours or what your overall average hash rate for the last 24 hours was. Changing this design would be 1) a privacey concern and 2) potentially harmful to the pools due to the number of constant API requests coming in, so I doubt rearwheels is interested in doing such a thing. However, if you could get your pool(s) to include that data in the data returned by the API i should imagine that he'd be happy to add it to his page and perform math on it where doing so would make sense.Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
Thanks for assuming I wasnt aware of how btc poolwatch cache the stats in a cookie, unfortunately I was.
My request would obviously suggest an accounts section / users actually logging in. This is part of the request for such a feature and I cant imagine it not being possible to implement.
The question would be would they want to add such features, I guess not. This isnt the end of the world as I have other means to go about this, it would just have been an easier approach to get the same thing done.
rearwheels would you be willing to add some basic earnings/accounting section.
Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
Yours isn't the first request for a feature that would require the server to store our information and poll our data whether we are actually using the page or not. It probably won't be the last either. That said, if you had read through the thread, you would have learned that our API keys are stored ina cookie on our computer and the data from the servers is only retrieved from the pools when we request it by loading the page. Given those two constraints, there is no way he can tell you what you earned in the last 24 hours or what your overall average hash rate for the last 24 hours was. Changing this design would be 1) a privacey concern and 2) potentially harmful to the pools due to the number of constant API requests coming in, so I doubt rearwheels is interested in doing such a thing. However, if you could get your pool(s) to include that data in the data returned by the API i should imagine that he'd be happy to add it to his page and perform math on it where doing so would make sense. Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
rearwheels would you be willing to add some basic earnings/accounting section.
Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
Im thinking it would be nice to use btc poolwatch that allready combines the confirmed/unconfirmed and estimated earnings in one block for all listed pools however it would be even more usefull if we could select an earnings range or at the very least have 24hr earnings calculated for confirmed/unconfirmed/estimated earnings.
This way we could more easily figure out what we made in a 24hr cycle compared to expected returns based on hashrate. Users on more than one pool it starts to get tricky to keep accurate 24hr cycle track of earnings.
Eligius pool speed fixed.
The only pool that does not return json.
Minor update to the "Pool Stats" page.
Added a show of count down to new difficulty
Code:
6d 08:06:40 to new difficulty: 1,826,161
Nice addition rw!
btw, pool speed on eligius has a bug:
Quote
Eligius
[Speed:0 ByteH/s]
Confirmed Rewards: 0.31658895
[Estimated: 0.0]
[Speed:0 ByteH/s]
Confirmed Rewards: 0.31658895
[Estimated: 0.0]
Just wondering if there was an update on adding NoFeeMining.com??
Added nofeemining.com!
thx
sent some coin
Minor update to the "Pool Stats" page.
Added a show of count down to new difficulty
Code:
6d 08:06:40 to new difficulty: 1,826,161
Was that a convoluted request to add triplemining? If so, I'll second that. But I don't think they do user apis, only pool stats.
No, actually, someone else requested it, he tried and the API was broken so he was going to e-mail the admins. I was just providing potentially useful information. That said, TripleMining provides API keys to users, so I should think they would have per-user stats. However, those may not be at the same URL, I wouldn't know.EDIT: I guess one could find out easily enough since the API on the workers page is a link... http://api.triplemining.com/json/
yep - triple just added it yesterday - talk about coincidence!
Hm...can you check by doing the following:
1. hit the api url with your api key
http://api.triplemining.com/json/
If you are using IE or firefox, you will be asked to save the output to a file.
2. Copy and paste the output into http://jsonlint.com/ and click validate. This will format the json nicely.
Double check the "stales" information reported by triplemining json.
My only problem with this is that the "alive" is returned as a text and not a boolean value.
IE displayed it instead of asking me to save. IMHO, it was human readable, so I didn't mess with jsonlint, but it definitely shows 9 stales. Sounds like a question for triplemining, but I'll let someone else mess with that. 1. hit the api url with your api key
http://api.triplemining.com/json/
If you are using IE or firefox, you will be asked to save the output to a file.
2. Copy and paste the output into http://jsonlint.com/ and click validate. This will format the json nicely.
Double check the "stales" information reported by triplemining json.
My only problem with this is that the "alive" is returned as a text and not a boolean value.
Hm...can you check by doing the following:
1. hit the api url with your api key
http://api.triplemining.com/json/
If you are using IE or firefox, you will be asked to save the output to a file.
2. Copy and paste the output into http://jsonlint.com/ and click validate. This will format the json nicely.
Double check the "stales" information reported by triplemining json.
My only problem with this is that the "alive" is returned as a text and not a boolean value.
Added TripleMiningI'm not 100% sure if I've interpreted the json reply for worker status correctly. Please try it out.
The worker name and shares counts look right. I'm not sure that the number you have for stales is right, though, you show 9 stales on my worker while the website appears to say I have no invalids.
Added TripleMining
I'm not 100% sure if I've interpreted the json reply for worker status correctly. Please try it out.
I'm not 100% sure if I've interpreted the json reply for worker status correctly. Please try it out.
The link "http://api.triplemining.com/json/stats" only shows the number of shares currently? I was looking through the bithopper thread and it seems this triplemining API was created for that purpose.
But "http://api.triplemining.com/json/
But I have a few nasty emails to send to my webhosting company first.
Was that a convoluted request to add triplemining? If so, I'll second that. But I don't think they do user apis, only pool stats.
No, actually, someone else requested it, he tried and the API was broken so he was going to e-mail the admins. I was just providing potentially useful information. That said, TripleMining provides API keys to users, so I should think they would have per-user stats. However, those may not be at the same URL, I wouldn't know.EDIT: I guess one could find out easily enough since the API on the workers page is a link... http://api.triplemining.com/json/
The link for PolMine is going to NoFeeMining.com.
Sorry about that. Fixed!Quote
For JSON stats, please use http://api.triplemining.com/json/stats
Perhaps the admins responded to you, but if they didn't, perhaps they were letting users know because it has been fixed but they didn't think you needed to. Perhaps not, though, I don't know.Was that a convoluted request to add triplemining? If so, I'll second that. But I don't think they do user apis, only pool stats.
The link for PolMine is going to NoFeeMining.com.
Sorry about that. Fixed!Quote
For JSON stats, please use http://api.triplemining.com/json/stats
Perhaps the admins responded to you, but if they didn't, perhaps they were letting users know because it has been fixed but they didn't think you needed to. Perhaps not, though, I don't know. The link for PolMine is going to NoFeeMining.com.
Sorry about that. Fixed!
The link for PolMine is going to NoFeeMining.com.
Anyway it's done!
I know! I actually found it before I saw this post! Nice surprise there.
Jump to: