Anychance of adding timetravel algo?

@CryptAtomeTrader44
Thanks for the Merit point

I've spent some time in the last few days experimenting with different ethash miners, I found that the easiest way to switch is to make a link named "latest" and point it to the selected miner version. I also had to move the content of the existing "latest" directory in a properly named dir, I don't understand why it hasn't been done this way already. I think the best would be that update script will install new miners in a dedicated directory and update the "latest" link to point the new miner version. Than like it's for claymore in 1bash one should be able to select either "latest" or the exact version. It sounds reasonable or I'm missing something obvious?

Yes, I wrote that there are some post of that.
hurvajs77 had to read it in two or three of my posts a few weeks ago when nicehash returned online after their December BTC hack.

I also had problems with the implementation of these crypto currencies nicehash algo displayed in the list of WTM ...
In fact, I had to review all the 0miner script to check the conditional loops "If" and "fi" I did not notice where I found that it was missing, but what is certain c After doing this, I did not have any more problems with nicehash-algo.
Without this operation, I was entitled to an empty line in the terminal window. He detected that it was nicehash thanks to the python scripts, but did not launch the mining command. As if he did not find it ...

Finally, I asked to replace the underscore in the forked script python papampi because the site WTM uses a dash and not an underscore, which implies that if I want to see the nicehash-algo years the list WTM that recovers that script, I have to put dashes.

Another change request that I made is to change the BTC address used for Nicehash commands to undermine their multi-algo cooperative.
Indeed, nicehash generates its own BTC addresses associated with our accounts nicehash online and therefore you can not directly mine to any BTC address of another site (exchange) or wallet
So I myself replaced this variable in the commands to mine nicehash-algo in NICEHASH_BTC_ADDRESS which is a BTC address for the internal auto exchange on their site, but which can not be a BTC address external to their site and has our personal account.

If this is not clear, do not hesitate to explain what is problematic.

Papampi, can you help me out. I'm not sure where to start really but one of my rigs keeps getting a GPU Utilization is too low: restarting 3main error ever so often and it constantly says "connection closed by server r:0". I've tried different pools and different coins but seem to have the same issue. I've also reformatted with a fresh copy of nvOC 19-2.0 but still have issues. Thanks man!

Yes, so it's not a problem, but NICEHASH_BTC_ADDRESS must be in 1bash file of course.

I have not made this update to version 19-2.1 yet

Another thing: I wanted to know what happened to this story of a guy who had posted and which he proposed to share the source of his code with us although he develloped for him initially.

Leenoox had asked him to share his code with graphics and statistics but I do not know if he did something ...

So is this meant to be a multi-algo switching rather than coin switching (same algo)?  Is it a better switching at estimating most profitable coins?  Just trying to get a better sense of the difference between MPH_EQUIHASH and SALFTER.  Also got it working today

Weird...did that yesterday and seemed to give me some errors but seems to be working today.  I did notice the OC setting I had in SALFTER did not work while i was hashing equihash algo.  I assume that would be the same for the others, any idea why the OC settings are not working in SALFTER?  I turned off the manual settings so i didn't miss that...

MPH_EQUIHASH just mine equihash algo, SALFETR_MPH switch between different algos.
There are some bugs in 3main in 19-2.0 with ethminer
Open 3main and change ethminer for both nicehash and mph,
Fixed in 19-2.1

salfter nicehash :
Change:

To:

salfter mph:
Change:
To:

No idea, he just posted some screen shots.
The thing is writing a code for yourself and for everyone's use has many differences.

When you write for yourself there are bugs and limitations that you know them and you may or may not put time to fix them.
But when you publish a free code for public usage, some people think just because you share your code, they paid you for it and they let themselves tell you whatever they like.
Thats why so many people don't like to post their codes and just use it privately instead of posting it for public usage.

Sometimes I think that's the reason fullzero left his own project and maybe we should do the same too.
Just write for ourselves and use as it suits us ...