I think Nemo can implement something like Pareto principle or any other %/% in batch. For example, use 20% of algos that bring 80% of 24h actual profit. It will mine most profitable algo, but exclude the ones, that pumped for a 1 minute, beacause no one multialgo pool can exchange it with a good exchange rate during short period. (sorry for my english)

Can anyone explain what i'm doing wrong. I use ahash24 .bat with my 5x1060/3gb , when nemosminer choose to mine blake2s my earnings (on website last 50 earnings)  are good (~0.00000245) , but when it mine neoscrypt my earnings = ~0.00000009. Anyone has same problem?

UPD: Found that profit on neoscrypt's Vivo and Innova is good, but Orbit, Feather and Guncoin is soo low.

I am not so good in computers, especially in servers. Thats why i am looking for a step-by-step guide. So maybe someone will create it.

I hope someday someone will make a guide how to use YiiimpLogger with free hosting. Tried today on 000webhost (have sql and cron listed in futures) but nothing succeeded. Maybe someone have step-by-step guide? Thx )

Hello guys.
Sorry for my english. Hope someone will understand me.

If there any way to see stats for ahashpool like "Algho X brought Y BTC during Z time" ?
So i can use stats from nemosminer to see duration of every algho and on website i can see btc profit for every share but only for last 50.
I just want to know what alghos to exclude from .bat. Or its better to use default ahashpool.bat. Thats because i heard that many ppl remove tribus, xevan, skunk, etc but for 2 days i mined these alghos 60% of the time but cant see what profit it brought to me.

Hello, Nemo.
Sorry for my english, i hope you will understand that i mean.

Have you ever thought about adding weight factor to your profit switching algho?
All of us knows that when use standard .bat some low-profit coins periodically break into top. And when we use 24h .bat we get a little less profit than we actually could. I think anyone prefer recieve stable profit that higher than using other miners or pools, here is why we use your miner.But standard .bat is a bit random, 24h is preferable for people that just want profit. What about adding average weight factor that will use both alghos. For example, ((Current estimate+24h Estimate)/2) + 24hr Actual*2!)/2. For sure like it calculates now with considering of rig's hashrate. This just an example, I used 2! factor cause I think 24h actual 2 times more important that Estimate, for sure this factor can better be calculated duting parallel tests. But this can exclude coins that was pumped for a one minute and inclute coins that really raise in price.