We should not use 24 hour actuals in our profit switching script, that makes sense.
But current estimate has a high fluctuation.
Does anyone see a reason why we should not just use the average of both values? (as long as current estimate is not zero)
Or we could just check if current estimate is not zero and still use 24 hour actuals?
I use a customized version of Nemos which does some of this.
I'ts less switching than CurrentEstimate / more than Actual24hr. Works great for me since about 2 weeks.
Moreover with the current down trend. Following Actual 24hr is not great.
Made it available here:
https://github.com/MrPlusGH/NemosMinerPlus-v2.4.2/releases. Have a go if you like.
Added functionality:
prerun feature
Ability to run a batch prior switching to a specific algo.
For example, can be used to set OC via nvidiaInspector
Simply create a file named <AlgoName>.bat in prerun folder
If <AlgoName>.bat does not exist, will try to launch prerun/default.bat
ahashpoolplus
Added ahashpoolplus as a pool.
Simply use -PoolName ahashpoolplus in start.bat
Uses calculations based on 24hractual and currentestimate ahashpool prices to get more realistic estimate.
Includes some trust index based on past 1hr currentestimate variation from 24hr.
This shows less switching than following Current Estimate and more switching that following the 24hr Actual.
AND is NOT sensible to spikes.
Better profitability on our rigs.
Test and share the results on yours.
Only for ahashpool. Working on expanding the feature to other pools.
Algo switching log
Added simple algo switching log in csv. switching.log file found in Logs folder.
Can be easily imported in excel as csv file.
Dude, with all due respect, but editing nemo's tool and *removing* his devfee address to put yours instead is definitely not nice. I see the point in wanting to get benefit from your work, but I'd suggest:
1. Be transparent about it (IE: Communicate)
2. Do not fully remove the original author's devfee. Consider a mixed solution.
Show Posts
