mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also. this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting
Hi fistsofgod, thanks a lot for the feedback! Could you let us know which pool is it? We will try to understand what is happening. Cheers
dapool.io
Have also experienced a lot more rejected shares with dapool than snowmining.com I dont know if it is dapool specific because those are the only 2 i have used.
Already had a chat with fistsofgod but we weren't able to debug the issue. I may add that not every (miniz) worker is experiencing the same behaviour.
We're very interested in the resolution of this issue. If you need any support, please let us know.
We had been hashing for the best part of the last month with a few fellow miners. Right now we are opening our brand new mining platform to the public. Have a few coins already in backlog ready to be added in the near future.
I'd like to know how it should work automatic algo/pers detection. When I try mining a equihash 192,7 with ArrowPoW pers, the miner automatically resorts to 144,5 with BgoldPoW if no algo/pers are specified.
Thank you
Hi daPool, at the moment, if the pool server contains arw then it will automatically detect that you want to mine Arrow. If you can give us a few more details we can also add your pool to our autodetection 'magic' list. Thanks for contacting us! Cheers
Oh.. I see!
Right now we use "full" command line options, that is
Re: miniZ, a fast & friendly Equihash 144,5 150,5 125,4 192,7 210,9 96,5 Cuda miner.
by
daPool
on 26/11/2019, 16:00:27 UTC
Hello, I'm a pool operator.
I'd like to know how it should work automatic algo/pers detection. When I try mining a equihash 192,7 with ArrowPoW pers, the miner automatically resorts to 144,5 with BgoldPoW if no algo/pers are specified.