Hi
I don't have baikal miner yet, so have limited knowledge about it.
Is it possible to set same priorities to each algo pool?
I hope it to stop useless pool alive checking when current connection (algo) is alive.
Baikal allows you to set different priorities for each port (algo) in the list of pools. It will automatically switch to a new algo when you take a port offline, so it works fine for now. The only thing it doesn't do, which causes issues within Miningpoolhub is allow someone to set difficulties separately for each pool. Would it be possible on the miningpoolhub end to set difficulties for the baikal mining pool for smaller coins (digibyte, etc) to 256 and to whatever lower setting is better for Dash or other 'harder' coins? I have noticed when I keep the difficulty setting at 256 I get lots of rejected shares, but if I take it off I don't think I'm being as efficient with the smaller coins.
Thanks!
Each pool remembers last mined difficulty value and resumes from that value after reconnection.
(Different algo pool works independently, they use their own difficulty level)
If you want to set starting diff, try to set worker password as "d=256"
More info about setting start difficulty is here
https://bitcointalk.org/index.php?topic=472510.msg10596890#msg10596890If your issue is about Qubit algo pool, they would have some difficulty mulitplier issue.
I'm not sure about this issue with Baikal miner, but sgminer and ccminer used different factor for difficulty level. So, ccminer needed difficulty multiplier value for 256 or 0.00390625 (1/256) to mine.
Can you clarify what coin you seem to have problem? And what difficulty value was set at website worker page.