Quote from: hesido on June 08, 2018, 07:52:06 AM

I used the proxy with SRBMiner with good results, and tested with XMR-stak also. However, I need to add TLS support and that means I have to learn more stuff. I could also employ the max allowed difficulty in the pool switch too, it may be another parameter in the coin-switch (auto coin switch is in the works, not working

). When thing get stable enough for SRB (it never does, it's a continuous fight against new drivers and windows updates and new algos) but if at all, coin switching through job json would be super awesome (without miner restart ;=) ), to overcome the namespace problems (everybody is calling some algo differently) since there's no set standard for algo names, you could go with e.g. "_SRB_powtype": "CryptonightV7" , so the proxy can add that to the job json..

But in future if the algo names follow standards, pools can send the "powtype" for any job, this way they can signal miners any algo change due to forks etc. with no problems, so hashrates are not lost with people trying to guess when the fork is going to happen, e.g. they could send "CryptonightHeavy" for block 30000, and "HavenAlgo" for block 30001 so the change would be seamless (even for miners that would need a restart, they would restart at the proper time!), this would be very good for a comfortable transition to new algos. A man can only dream Cheesy

Coin switching for the same algo shouldnt be hard, your proxy sends info in json which coin to mine, minert just switches to the pool/wallet for that coin, and continues to mine.

If you manage to make it stable enough ("it never does, it's a continuous fight against new drivers and windows updates"

)) ), i can make SRBMiner compatible with it.