Quote from: badman74 on July 09, 2014, 01:08:11 AM

Quote from: langes01x on July 09, 2014, 12:59:22 AM

Quote from: nicehashdev on July 08, 2014, 09:50:47 PM

I have proposal for stratum extension to support algorithm change without reconnects.

First, we need to normalize name of the algorithms; example:

Code:

scrypt, nscrypt, x11, x13, x15

Miner subscribes to server that it is capable of switching algorithms. It also sends parameter list. Each parameter consists of 3 parameters: algorithm name, factor and cost. Factor is speed in MH/s (it is only important to be relative to other provided factors of other algorithms), cost is daily cost of rig in USD.

Example for 2 algorithms:

Code:

{"id": X, "method": "mining.algorithm.subscribe", "params": [["scrypt", "1", "2.5"], ["x11", "4.2", "2"]]}\n

Server then calculates which is best algorithm for this rig considering provided factors and costs. Before any work is provided and on algorithm switch, server sends (example to switch to x11):

{"id": null, "method": "mining.set_algorithm", "params": ["x11"]}\n

Immediately after that server sends new difficulty and new work.

There is no need to have the server do this. It would be just as easy to create a client-side switcher that can figure out when it should switch between different algorithms. I've created a switcher like this for the TradeMyBit pool that uses sgminer v5 no-restart switching (and the old method of switching for backwards compatibility). As long as the NiceHash pool has an API that returns the profitability of each algorithm then it's just a matter of deciding if or when you want to switch.

See https://bitcointalk.org/index.php?topic=661827

why couldn't this determine the profitability on its own, just give it your hash rates and cost and get the price info from the web then have it switch as necessary on ANY pool

The point is that it could as long as NiceHash (or whatever multi-algo pool you want to mine at) expose the appropriate API required to get the profitability information for the algorithms they are currently mining.

Of course as it is it wouldn't work but it would only take a small number of tweaks to get it working with other pools. If that is possible (i.e. the required API exists) and people want it then I could look into it.