Re: [POOL][Scrypt][Scrypt-N][X11][X13] Profit switching pool - wafflepool.com
So since I cannot wait to rejoin Waffle, I'm just walking through the concept of auto switching and wondering if this is what it takes:
1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix
2). Additional ports to receive the switching clients
3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another
I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled.
My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix
2). Additional ports to receive the switching clients
3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another
I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled.
My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
This is almost exactly what we'll do. The biggest thing unaccounted for is how to handle users who either prefer (electricity, etc) a specific algorithm (aka, add +25% weight to x13), and users who have cards that switch at rates outside our standard (eg, having a card that does X13 at 6x instead of our calculated 3.4x).
Doing the first part (algo switching) shouldn't be too terribly difficult, some tech additions (turning on/off ports), and some minor switcher logic (choosing which port to open).
Doing the second part (per user config of weights) is a lot tougher, and will likely get pushed back for a while (no one else is doing that yet either, so its not like we're playing catchup)
What I'm doing is using custom variables that are being set in the password field to control my own formula as to how I want to mine. So I can give my own custom defined weight to each algo, or I can use the defaults. Then the pool is taking those and applying them. In thinking that through, that means the port opening and closing simplicity is not there, as some will be mining different coins based on custom settings, so I'm not clear how they are doing that (keeping in mind I have no knowledge of the backend of a pool, but just was trying to better understand it).
For me, I'm fine with using default calculations if it speeds up implementation and makes it easier on the back end. Based on your past, I would certainly trust your profitability calculations, as I have on a per coin basis, this simply makes a multi-pool even more multi.