Feedback on changes/ideas
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Feedback on changes/ideas
I have been using prohashing for a while off and on and in general I am very happy with the service (and enthusiastic operators).
A few suggestions if I may:
1. I run quite a few rigs - the "current worker status" only handles 10. If I have more than 10, and select next page, it seems random which rig will come on the next page. I use that to scan for rigs that are down etc.
2. API access - I know you guys are looking into it - but i would be great to be able to have a page showing the stats accessible on iphone etc.
3. More historical profitability history. Both total M/H and payouts for the whole server, and the same for individual users.
4. This might be tricky to do but it would be great to get more stats on the individual coin pools, I have played around with making some automated switching (instead of your switching algorithm) but would need more pool history. I also think the fact that users can mine individual pools is a great selling point which is probably "under-marketed".
Keep on the good work!
A few suggestions if I may:
1. I run quite a few rigs - the "current worker status" only handles 10. If I have more than 10, and select next page, it seems random which rig will come on the next page. I use that to scan for rigs that are down etc.
2. API access - I know you guys are looking into it - but i would be great to be able to have a page showing the stats accessible on iphone etc.
3. More historical profitability history. Both total M/H and payouts for the whole server, and the same for individual users.
4. This might be tricky to do but it would be great to get more stats on the individual coin pools, I have played around with making some automated switching (instead of your switching algorithm) but would need more pool history. I also think the fact that users can mine individual pools is a great selling point which is probably "under-marketed".
Keep on the good work!
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Feedback on changes/ideas
Hi trade,
Thanks for the tips.
1. This issue should be easy to resolve and we can put it out by next weekend.
2. We can provide API access, but we haven't been able to come up with a way that developing a mobile app could be profitable (the number of developer hours would be too great for the small number of customers we could gain). Do you think someone would develop a mobile app if API keys were provided? Were you interested in doing that?
3. We'll add these to the list.
4. Are you disconnecting and reconnecting to our server, or to other pools? If you connect to other pools, our statistics are going to be inaccurate, because our orphan rates will be different than theirs.
In regards to API access, we may want to use a WAMP server instead of a REST interface, so that there could be realtime data. Perhaps you could share your opinion on that.
Thanks for the tips.
1. This issue should be easy to resolve and we can put it out by next weekend.
2. We can provide API access, but we haven't been able to come up with a way that developing a mobile app could be profitable (the number of developer hours would be too great for the small number of customers we could gain). Do you think someone would develop a mobile app if API keys were provided? Were you interested in doing that?
3. We'll add these to the list.
4. Are you disconnecting and reconnecting to our server, or to other pools? If you connect to other pools, our statistics are going to be inaccurate, because our orphan rates will be different than theirs.
In regards to API access, we may want to use a WAMP server instead of a REST interface, so that there could be realtime data. Perhaps you could share your opinion on that.
Re: Feedback on changes/ideas
Thanks for your reply.
1. Thnx
2. I agree that developing an app would not be profitable. But have a look at https://itunes.apple.com/app/id813061889 or https://play.google.com/store/apps/deta ... oinmonitor, they are typical API reading softwares. I am sure I could facilitate some some of wrap around but if the API is available, these existing programs really do the job.
1. Thnx
2. I agree that developing an app would not be profitable. But have a look at https://itunes.apple.com/app/id813061889 or https://play.google.com/store/apps/deta ... oinmonitor, they are typical API reading softwares. I am sure I could facilitate some some of wrap around but if the API is available, these existing programs really do the job.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Feedback on changes/ideas
Are you the developer of that app? If you are not, do you know who I can contact?
That description reads like the app developer will add support for free if we provide an API. I'll confirm that with him and find out what format he wants the API in.
That description reads like the app developer will add support for free if we provide an API. I'll confirm that with him and find out what format he wants the API in.
Re: Feedback on changes/ideas
I'd like the "hashrate" display to be more detailed. Seeing extremely tiny lines going back a week isn't very useful to a Zeus owner. My old crap is just as likely to run smooth for days as it is to start kicking out HW errors. On Nicehash I can zoom in to a day or even 12 hours so I can see at a glance what my old heaps are doing RIGHT NOW. I realize I can hover over the graph and get some info, but trying to move my mouse one friggin micron to locate the data I want simply isn't working for me.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Feedback on changes/ideas
Thanks for the suggestion, Some1. That's actually an issue we've known about for a while.
I'd love to lie to you and say that we plan to fix it soon, but the reality is that Chris is backlogged with a whole lot of things that can increase profitability, and profitability always has to come first. However, once profitability is maxed out again, we'll definitely look into changing the hashrate charts.
I'd love to lie to you and say that we plan to fix it soon, but the reality is that Chris is backlogged with a whole lot of things that can increase profitability, and profitability always has to come first. However, once profitability is maxed out again, we'll definitely look into changing the hashrate charts.