Quote from: MagicSmoker on February 19, 2018, 11:19:58 AM

Quote from: jkminkov on February 19, 2018, 10:32:41 AM

Quote from: MagicSmoker on February 17, 2018, 07:10:58 PM

...

I'm *hoping* that MrPlus' fork of NemosMiner will help, but if not I will use NiceHash for auto-convert to BTC and Zpool or MiningPoolHub for "single-algo, convert to whatever I want."

try MinerControl* to use all mentioned pools, it has config to use current pool api data or use an average window(60 minutes by default), use master-slave config if run multiple rigs, avoid looking @ zpool webpage stats cause it would block pulling api, use https://miningpoolhubstats.com/ instead.

* - https://drive.google.com/drive/folders/1lT8E8j3BKzM7r1Mo2EFHk1NmP8gkdZ1Q and https://bitcointalk.org/index.php?topic=769239.1180

Using a 60 minute average of profitability would be better than relying on either the instantaneous value when polled or the strange attempt to average the 24 hour and instantaneous data that NemosMiner and others are pursuing. However, MinerControl appears to have been abandoned several years ago while MrPlus has been working on a fork of NemosMiner* right now and so seems to be receptive to implementing good ideas provided by the community so I am giving it a shot now.

* - https://bitcointalk.org/index.php?topic=2965976.0

There is another factor that I think I have picked up that contributes to the loss of income with algo switching on zpool and it relates to the delay between when a new hash is solved and when it becomes "immature". If there are several "new" hashes and the miner switches way to a new algo you lose some of the income from those shares when they switch to immature. This issue is easily observable. simply mine a coin like x17 and when you see 4 or 5 new shares sitting in the pool stop your miner and see how many of those hashes you get paid for.