Quote from: crypper on June 30, 2018, 02:33:52 PM

Quote from: ComputerGenie on June 30, 2018, 12:26:59 PM

Quote from: crypper on June 30, 2018, 11:37:09 AM

...I'm on equihash autoswitch (zen, zec, btg, zcl; port 17203) at MininPoolHub; happily mining with older EWBF cuda miner.
BTG is however about to fork (~ July 1st) and switch to 144,5 algo.
Since new EWBF miner doesn't support 200,9 and older miner doesn't support 144,5, it will not be possible to mine at MPH with either of the miners. What would be a solution here?...

Because the K & N change makes for what is essentially a new algo, it's not possible to have one port that supports "different equihashs" at the same time (unless the pool has special software to change from a to b). One miner that autochanged algos based on a given pool's switch would have to coordinate with that given pool. That's just not how miners work, unless they, or some overlay app, are proprietary to that pool (like nicehash).

You are probably right, BTG will have to be dropped from the port. MPH is however silent on that matter. We'll see.

The MPH banner shows they're supporting BTG after the fork, but yeah, BTG will have to come out of the auto-switching Equihash pool.

Their BTG page offers specs - they're keeping the same port number post-fork, so they must plan to take out the old pool and connect a new pool to that same port number at the time of the fork (or have otherwise automated the switch on their end - in which case, good job, MPH.)

https://bitcoin-gold.miningpoolhub.com/