Status as of Sunday, August 19, 2018
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.
While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.
While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
Tomas_Novak
- Posts: 28
- Joined: Wed Jun 13, 2018 4:14 am
Re: Status as of Sunday, August 19, 2018
port 3337 not working
Re: Status as of Sunday, August 19, 2018
yep it's not for me either, plus on 3333 i aint getting any worker statusTomas_Novak wrote:port 3337 not working
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Status as of Sunday, August 19, 2018
Unfortunately, I haven't been able to reproduce this issue. We'll keep trying and let you know what we find. We may need another customer to report a similar issue so that we can look at what's in common.djliss wrote:yep it's not for me either, plus on 3333 i aint getting any worker statusTomas_Novak wrote:port 3337 not working
Re: Status as of Sunday, August 19, 2018
It was definitely a problem earlier, but appears to be working correctly now.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Status as of Sunday, August 19, 2018
OK, great. I can't reproduce this error and CSZiggy has yet to reply with his username, so I'm going to consider it resolved for the time being. If I see a rash of errors in the mining server logs, that should indicate something is wrong and I'll resume investigating.ryguy wrote:It was definitely a problem earlier, but appears to be working correctly now.
Re: Status as of Sunday, August 19, 2018
seems to be working now on 3333 with status, will try 3337 when i get home from work.
Re: Status as of Sunday, August 19, 2018
On a side note, anyone know which is more profitable with GPU's lyra2rev2 or equihash? is lyra2rev2 asic resistant? if so will this be more profitable for GPU's as there are a lot of equihash asic's that have dragged profitability on GPU's down.
Re: Status as of Sunday, August 19, 2018
Using the same settings I used before I was able to connect in without an issue today.
Nothing changed on my end but now it connects in and mines without issues.
Thanks for the fix, seems to be working fine now.
Nothing changed on my end but now it connects in and mines without issues.
Thanks for the fix, seems to be working fine now.
Re: Status as of Sunday, August 19, 2018
talking about algos that are easy to implement is zhash one of them as it looks quite profitable at the moment (BTG is using this algo now by the looks of things)
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Status as of Sunday, August 19, 2018
I'm working on neoscrypt right now. There doesn't appear to be an open-source implementation of the zhash algorithm that I can find, and equihash mining in general is more complex to implement. It might be next after ETH mining, though.djliss wrote:talking about algos that are easy to implement is zhash one of them as it looks quite profitable at the moment (BTG is using this algo now by the looks of things)