Quote from: papampi on February 03, 2018, 05:22:15 PM

Quote from: CryptAtomeTrader44 on February 03, 2018, 05:04:27 PM

Quote from: papampi on February 03, 2018, 03:50:23 PM

First of all I should thank you for your nice tone... and sorry for nicehash bugs in 1bash, as I said its a pre-release, and usually they have bugs.
I had no intentions of adding Nicehash to my wtm switch as I dont use nicehash but after many users asked for it I followed @CryptAtomeTrader44 instructions on it, and he said that "NICE_" should be changed to "NICE-" in coin name for it to work.

So if you have a fix for it please let us know.

Thanks.
Pap.

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.

I already made the change as your request and added it in 1bash 19-2.1 pre release :

Code:

NICE_ADDRESS="$NICEHASH_BTC_ADDRESS"

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 ...