Yes that will be fixed as well


@Frangomel:

thanks for the log. That are indeed much more then should usually happen. Is it the 3G or the 4G code (or the 4G ASM) and what version of the miner? Will wireshark that version myself on a test sys to see if I see so many duplicates, too.

Hi there,

1. Good question ... need to set up a Windows 7 system to check myself, on Win 10 (just checked) it works. What is needed is that there is an empty folder "logs" in the directory of the miner and using parameters --logs 1. I will check back on that.
2. Thats indeed odd - the miner reports about accepted shares only when pool did send an accept message. Can you send me the thing the pool host send you in a private message? (What algorithm is this by the way? Every code is a bit different...)
3. Currently you can not distinguish. For almost every stratum protocol you get back only "accepted" or "rejected", but barely a reason. 0.7 and 0.6 are different here: 0.6 submits every solution found, independently if already a new job did arrive or not, while for most coins except Beam 0.7 does filter out the stale ones. For Beam it is different, because there the stratum specs allow submitting old shares if they belong to same block height, so some pools (sunpool, sparkpool...) credit stale shares, some do not. By the way if someone is interested in statistics: On my Beam fee account (that should be an average of all miners using my miner) we are at 0.04% rejected shares, 1.2% delayed / stale shares and 98,74% valid + in time.
4. I am planning to add more statistics to the long stats as well as the API - the keyboard trigger is an interesting idea, will check how easy that is to do.
5. I am still there - from time to time. But last week was extremely busy working - a bit too much. Need to step a little shorter. But before (next week) will release 0.8 with a solution to the Nicehash problem on 144/5 and one new algorithm


Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?