Topic: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin. - page 126. (Read 487870 times)

You setup an account just to post that.

4 years of vibrant community, awesome pool operator and a great pool. NiceHash goes down and everything turns into conspiracy theories.

Why a lot of AMD/nVidia variants at AUTO SWITCHES page?
How can I understand which is best for me? Please, help!

Found some info regarding the notice that Siacoin is unable to auto-exchange due to a wallet problem at bittrex:

https://www.reddit.com/r/siacoin/comments/7jf33l/sia_sc_2_days_wallet_maintenance_on_bittrex_is/dr65kfq/

Seems that the current siacoin wallet has performance problems when dealing with larger transaction volumes, and has been taken offline pending a fix from the devs.

This same issue could pop up on MPH, so there will be an updated wallet soon containing fixes.

Did anyone manage to fix reported rate @ MPH for Zcoin with ccminer?

Tried:
-ccminer x64 2.2.3 cuda 9
-ccminer x86 djm34 2.2.x (.1 or .2) (which is the one suggested by MPH @ the Zcoin pool page)
-ccminer x86 "some other fix version" forgot which fork

With all the above getting around 50-60% ccminer rate

With ccminer x86 djm34 non cuda 9 I get worse ccminer performance (around 2800, down from 3050 with others) but way better reported rates (up to 2500)

Any ideas?
Should I just check how much I'm getting with one vs the other and just ignore what's being reported?

I'll also do some suprnova tests.

There is no simple and absolute way of determining the most profitable coin to mine.  The biggest issue is that any coin that is the most profitable will immediately get a lot of mining power applied to it, which will drop the profitability rapidly.  The affect will be amplified on low volume coins.  So there are different ways of deciding which coin is the best to mine and whattomine.com can't be assumed to be the absolute arbiter on this.  Rapidly jumping from mining one coin to another will also hit profitability as most pools use PPLNS so it's hard to say with certainty if MPH method of choosing a coin is good or bad.

each algo have their own port btw.

This is how I see it:

The pool "kicks you" out (by not giving you work) until you start mining the "most profitable" algo from this list (its a loop):

:start
EthDcrMiner64.exe -epool us-east.ethash-hub.miningpoolhub.com:12020 -ewal username.workername -eworker username.workername -esm 3 -epsw x -allcoins 1 -retrydelay -1
#ethminer --farm-retries 0 -G -S us-east.ethash-hub.miningpoolhub.com:12020 -O username.workername:x -FS exit
ccminer -r 0 -a groestl -o stratum+tcp://hub.miningpoolhub.com:12004 -u username.workername -p x
ccminer -r 0 -a myr-gr -o stratum+tcp://hub.miningpoolhub.com:12005 -u username.workername -p x
ccminer -r 0 -a x11 -o stratum+tcp://hub.miningpoolhub.com:12007 -u username.workername -p x
ccminer -r 0 -a x13 -o stratum+tcp://hub.miningpoolhub.com:12008 -u username.workername -p x
ccminer -r 0 -a x15 -o stratum+tcp://hub.miningpoolhub.com:12009 -u username.workername -p x
ccminer -r 0 -a neoscrypt -o stratum+tcp://hub.miningpoolhub.com:12012 -u username.workername -p x
ccminer -r 0 -a qubit -o stratum+tcp://hub.miningpoolhub.com:12014 -u username.workername -p x
ccminer -r 0 -a quark -o stratum+tcp://hub.miningpoolhub.com:12015 -u username.workername -p x
ccminer -r 0 -a skein -o stratum+tcp://hub.miningpoolhub.com:12016 -u username.workername -p x
ccminer -r 0 -a lyra2v2 -o stratum+tcp://hub.miningpoolhub.com:12018 -u username.workername -p x
ccminer -r 0 -a vanilla -o stratum+tcp://hub.miningpoolhub.com:12019 -u username.workername -p x
timeout 1
goto start

this is what I am using but I just saw something weird. Equihash choose Zclassic even if was clearly more profitable to mine ZEN or even Zcash, it wasnt even close, ZEN was 50% more profitable...

This is a good explanation, much better than on the FAQ page.  I like MPH but the frontend is a mess in useability terms and it could definitely do with better explanations.  It would save a lot of newbie questions and confusion here.  Not being able to easily see at a glance what you are mining at any given moment desperately needs to be fixed.  I understand however that big improvements are pending.

Miners that do their own algo profitability calculations should use the fixed algo coin switching ports (17xxx).

Miners that want to use MPH's algo profitability switch should use the 12xxx port numbers, with the mining software configured to cycle through a list of algos in response to the worker authentication being rejected by the pool. Like so a given set of worker credentials will only be valid on the most profitable algo of the selected list.

I think Awesomeminer or MPM try and do this algo switching within the software so they should (probably) be set up with the specific Algo ports in their config not the multi-algo ports.  Only use the multi-algo ports if you WANT the POOL to decide which algo to mine as any connections to the non-optimal algo will be closed.....

FWIW I think the multi algo works like this.

You set your miner software up with either multiple pools or multiple calls to the miner software in a batch file where each call runs a different algo. All the pools/calls use the SAME multi algo port and id details.

The Multi-algo port detects which algo you are using and routes you to the correct pool. IF the algo is not the most profitable of the set then the Multia-algo port closes the connection, this then makes the miner move onto the next pool (needs failover-only set) or causes the miner command line to exit and run the next one in the batch file.

So you configure the miner software to loop round trying each algo in turn against the multialgo port, the port will reject/close the connection if that is not the most profitable algo of the set.   your miner MUST support all of the possible algo's which is why there are different ports for different algo sets.

Makes total sense.  However, why have separate ports for the multi-algo?  e.g. Awesome miner does multi-algo with MPH but uses the 17xxx (auto switch) ports.  Why have separate 12xxx ports for multi-algo when it's always the client who decides the algo?

Well said.  Myself, I am pretty sure I got it now.

What a frustrating time. Not only can I not seem to find a good home for my miners without constant babysitting, this forum is failing just as much so I cant complain about it...

I've completely switched to Lyra2z/Zcoin with both GPU and CPU. Hash rate display on Dashboard also seems fine. I'll let it run for 2 days and check back

Anyone have experience with baikal miners and auto switching? I am using the default config inside the miner and followed the instructions to set up the worker and it won't profit switch. It will stay on the algo with the first priority including x11 which is the clear loser as far as profit goes. For now I am just switching the miner priority order based on the websites profit estimates but would love to have these be automatic as explained in the instructions.

I use port 17023 for mining equihash.
I dont see - what i mining now and how mach my speed.
All pools show zero speed, but wallets filled.

Where i can see my speed and status of my workers?

I'm curious myself what is happening over at Bittrex that has kept the sia wallet offline for so long. And now the expanse wallet is down too, I was going to use that as a backup. Its just a temporary inconvenience that the coins cannot be exchanged and the profits paid out to you right away. If that is such a big deal, then select a different coin to pay out as- or only mine the coin you want and pay that out to a local wallet instead of relying on automated coin exchanging systems.

Unless something really messed up happened, all of your profits should be perfectly safe as coins waiting to be converted or converted coins waiting to return to the pool and be paid out.

I apologize then, i may have quoted at the wrong level in the thread.

Tbh I like MPH. I am not complaining. I know how it works dude.