- It looks like Cryptsy is at it again, taking their price feed offline. I don't know how long it's going to last this time around, but there isn't a worse time for it to happen than at the start of business hours on a Monday morning. There isn't much we can do without price data.
- Fortunately, I completed the code for multiple exchanges yesterday. No testing at all has begun on that, and it will take a while to get a test Poloniex account set up, so it will be two or three weekends.
- Thanks to the people who reported bugs yesterday. I was able to fix the issue with hashrates disappearing, and another issue regarding negative times listed as coins being mined will be fixed tonight.
- Kristof, if you are there, and Cryptsy is up, could you try connecting to see if the latest fixes have resolved your problems with miners?
- The webserver for mail, forums, and so on is still hindering us because we can't check E-Mail remotely. It's amazing how easy it is to write and test code, and how difficult it is to configure other people's software. It is likely that adding multiple exchanges will turn out to take less time than configuring this webserver has.
- We were going to start advertising to dogecoin users today, but these Cryptsy problems may make us delay another two weeks until we can provide them with better service quality.
Status as of Monday, November 3
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.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Status as of Monday, November 3
Here's today's status:
-
- Posts: 44
- Joined: Fri Aug 29, 2014 11:15 am
Re: Status as of Monday, November 3
Still getting lots of errors like:
and constant flushing but I'll leave it on for another 20 or so minutes just to see if it can get up to speed. Bfgminer is showing about half the hashrate i get on straight ltc pools with a 40% reject rate.
Edit: I've taken it off sooner, its clear that the flushing issue is a major problem with the units. With a quick coin like CHN and the hashrate was falling to <40% and the reject rate climbing to over 60%.
Code: Select all
[2014-11-03 21:09:31] Rejected 003af0f0 KNC 1coh pool 0 Diff 16m/15m (Share is above target of 655)
[2014-11-03 21:09:31] Rejected 002eb0c5 KNC 2amr pool 0 Diff 21m/15m (Share is above target of 655)
[2014-11-03 21:09:31] Rejected 000be310 KNC 3ahu pool 0 Diff 84m/15m (Share is above target of 655)
[2014-11-03 21:09:31] Rejected 001976a5 KNC 3apt pool 0 Diff 39m/15m (Share is above target of 655)
[2014-11-03 21:09:32] Rejected 0024cea0 KNC 3bfo pool 0 Diff 27m/15m (Share is above target of 655)
[2014-11-03 21:09:32] Rejected 003704d4 KNC 3bsr pool 0 Diff 18m/15m (Share is above target of 655)
[2014-11-03 21:09:32] Rejected 00368134 KNC 0cmz pool 0 Diff 18m/15m (Share is above target of 655)
[2014-11-03 21:09:32] Rejected 003d13c0 KNC 0crz pool 0 Diff 16m/15m (Share is above target of 655)
Edit: I've taken it off sooner, its clear that the flushing issue is a major problem with the units. With a quick coin like CHN and the hashrate was falling to <40% and the reject rate climbing to over 60%.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Status as of Monday, November 3
I see that these error messages say "share is above target of 655." What did you enter as the password field in your miner? Is that using a static difficulty? I wonder if the mining server is not correctly parsing the difficulty or if the miners are not submitting the correct password.
-
- Posts: 44
- Joined: Fri Aug 29, 2014 11:15 am
Re: Status as of Monday, November 3
Yes I'm using d=65536 as the password, also from what i've seen on other pools the optimal difficulty for the titan is somewhere between 1024 and 2048. Does the difficulty have to be a multiple of 2 or could I say have it at 1442?
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Status as of Monday, November 3
It has to be a power of 2, not just a multiple of 2. You could try setting the difficulty equal to 2048 and trying again, but I guess that you would get the same result.
Tonight, I'm going to focus more on this stability issues and put off the multiple exchanges by a day or two, and I'm going to try to find a reproducible case. I'll start by looking at the database to see when you submitted those shares yesterday, and maybe I can learn something from that.
Tonight, I'm going to focus more on this stability issues and put off the multiple exchanges by a day or two, and I'm going to try to find a reproducible case. I'll start by looking at the database to see when you submitted those shares yesterday, and maybe I can learn something from that.