Question that I am hoping someone can help me with - I configured MultiPoolMiner with only MPH, and altered the Algorithm list to contain only MPH compatible algorithms. Nonetheless, several times per day it seems to switch over to mining on zpool, no matter what I do to the configuration.
Is this somehow the way that the devfee is being handled for MPM? The individual miners with devfees sometimes switch, but they're labelled with "devfee" so at least I know what is happening. With the zpool switches, I have no idea why it's happening. I don't always catch it right away so I'm unable to tell if it does it for the 10 minutes I've configured, or just "as long as it feels like it."
I'm happy to let it do some time for the dev, just want to be sure that's what's happening - like I said, I see it more than once per day, and I haven't pinned down the amount of time, so it feels like something it shouldn't be doing.
Topic: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin. - page 124. (Read 487870 times)
December 14, 2017, 04:18:21 PM
December 14, 2017, 04:03:28 PM
Hey guys,
Altought hash for lyra2rev2 its not measured correctly, do we get the hash we see localy in our miner?
Altought hash for lyra2rev2 its not measured correctly, do we get the hash we see localy in our miner?
December 14, 2017, 04:00:48 PM
Do i understand it correct.
@Note: Round Earnings are not credited until 130 confirms.@
Means that i need to do 130 accepted shares on this pool in this round to get some % from it?
So what is round? Same as @Time Since Last Block@ that affect on @Est. Avg. Time per Round (Pool)@
If i use Awesomeminer and do 130 shares in 1-2 minutes, does it mean that if i switched to another algo with it and did 130 shares before block was founded, i would get % for that shares?
Or its just better to use bat pool file?
@Note: Round Earnings are not credited until 130 confirms.@
Means that i need to do 130 accepted shares on this pool in this round to get some % from it?
So what is round? Same as @Time Since Last Block@ that affect on @Est. Avg. Time per Round (Pool)@
If i use Awesomeminer and do 130 shares in 1-2 minutes, does it mean that if i switched to another algo with it and did 130 shares before block was founded, i would get % for that shares?
Or its just better to use bat pool file?
December 14, 2017, 03:51:06 PM
Quick question. I have been mining Monacoin the last few days on my 1080ti rig. It's been consistant but under reports my current hash rate consistantly. Typically I have been on other pools where it varies and averages out. My profit is also lower according to calculations. I was reading that there is a problem with the LyraRev2 on the miner side. Is this true and am I better off switching to an eqhihash algo coin? On Mona I am coming in under but only a few dollars under which I have noticed that what to mine is not all that accurate sometimes.
Any feedback would be appreciated! I am tryingng to give Bitcoin Gold a 24hr run and it is reporting my hash rate correctly but not really finding blocks so I think profit will be less than sticking with the more consistant Monacoin.
What do you guys think?
Any feedback would be appreciated! I am tryingng to give Bitcoin Gold a 24hr run and it is reporting my hash rate correctly but not really finding blocks so I think profit will be less than sticking with the more consistant Monacoin.
What do you guys think?
December 14, 2017, 03:23:51 PM
guys what do you think is better miner to use MultiPoolMiner or Awesome Miner?
Btw how can i set cpu miner with awesome miner for multipoolhub?
Btw how can i set cpu miner with awesome miner for multipoolhub?
I can't speak to the CPU Miner, i don't use it.
However i have started leaning towards the batch file method using the hub feature. Instead of awesome miner. I found awesome miner switched too often, thus causing me to loose progress.
The batch file only switches after the share is found. This way you don't lose as much. (That is my understanding.)
December 14, 2017, 03:17:49 PM
Can/should i take the btc wallet address out of the mpm bat if i am only using mph and have my auto exchange set to litecoin?
December 14, 2017, 03:11:52 PM
It's close but it IS very wrong as Temporel said.
Anyone going to explain for the rest of us?
OK i think i see it.
They do not use the same ports and ID.
Each miner uses its own server and IP combo, the use the same username.workername to manage it.
Then you can only connect to the most profitable pool. Is this the discrepancy?
December 14, 2017, 03:11:15 PM
guys what do you think is better miner to use MultiPoolMiner or Awesome Miner?
Btw how can i set cpu miner with awesome miner for multipoolhub?
Btw how can i set cpu miner with awesome miner for multipoolhub?
December 14, 2017, 03:04:54 PM
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.
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.
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.
Definately better then the FAQ.
except its wrong about many things (djmuk's theory)
Are you saying the FAQ is wrong? or djmuk's theory? Cause from what i can see his theory is absolutely correct.
djmuk's theory , wake up
How about you explain your claim, cause again his theory looks to be completely correct. So as it stands you made a baseless claim and still have not backed it up. Maybe its you who needs to wake up.
It's close but it IS very wrong as Temporel said.
December 14, 2017, 03:00:01 PM
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.
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.
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.
Definately better then the FAQ.
except its wrong about many things (djmuk's theory)
Are you saying the FAQ is wrong? or djmuk's theory? Cause from what i can see his theory is absolutely correct.
djmuk's theory , wake up
How about you explain your claim, cause again his theory looks to be completely correct. So as it stands you made a baseless claim and still have not backed it up. Maybe its you who needs to wake up.
December 14, 2017, 02:38:27 PM
By default, I'm finding that cryptonight difficulty starts out way too high. I wouldn't start finding shares until 15 minutes in as it takes time for the difficulty to auto-adjust down to something more reasonable.
I'm playing around with difficulty numbers using d=xxx in the password field, but nothing seems to be working. I don't know what's the min and max for the settings.
What's the min and max for -p d=xxxx ?
Thanks.
Example:
ccminer.exe -a cryptonight -o stratum+tcp://us-east.cryptonight-hub.miningpoolhub.com:17024 -u username.worker -p d=1 -i 10 -d 0,1
I'm playing around with difficulty numbers using d=xxx in the password field, but nothing seems to be working. I don't know what's the min and max for the settings.
What's the min and max for -p d=xxxx ?
Thanks.
Example:
ccminer.exe -a cryptonight -o stratum+tcp://us-east.cryptonight-hub.miningpoolhub.com:17024 -u username.worker -p d=1 -i 10 -d 0,1
December 14, 2017, 02:34:18 PM
Hi guys,
I´ve set MPH to "auto switches" and "auto exchange" into Bitcoin.
Which coin would you suggest for auto exchanging?
Thanks
I´ve set MPH to "auto switches" and "auto exchange" into Bitcoin.
Which coin would you suggest for auto exchanging?
Thanks
we asked twice in the last 48 hours and no one replied. Im currently getting paid in ETH and it works fine
December 14, 2017, 02:33:14 PM
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.
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.
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.
Definately better then the FAQ.
except its wrong about many things (djmuk's theory)
Are you saying the FAQ is wrong? or djmuk's theory? Cause from what i can see his theory is absolutely correct.
djmuk's theory , wake up
December 14, 2017, 02:08:26 PM
Hi guys,
I´ve set MPH to "auto switches" and "auto exchange" into Bitcoin.
Which coin would you suggest for auto exchanging?
Thanks
I´ve set MPH to "auto switches" and "auto exchange" into Bitcoin.
Which coin would you suggest for auto exchanging?
Thanks
December 14, 2017, 12:29:20 PM
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.
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.
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.
Definately better then the FAQ.
except its wrong about many things (djmuk's theory)
Are you saying the FAQ is wrong? or djmuk's theory? Cause from what i can see his theory is absolutely correct.
12xxx ports will only allow you to connect to whatever algorithm is most profitable for what you have set in the hub section of your account. All others will not accept you connection.
The batch file loops through miners until it finds the one you can use.
17xxx ports will let you connect whenever and will switch coins, but does nothing to switch algorithms.
The FAQ actually makes sense configuration wise, all we really need is a clear explanation of what and why its doing it.
December 14, 2017, 12:21:33 PM
I am sure you have had offers from all over the place, but if you do want any help with some UI stuff and whatnot. (Not asking to see the secret backend). I would be willing to put some time in.
On a separate note i need to ask.
Does MPM work using the hub feature? Or does it do its own calculations and switch when it thinks its best?
On a separate note i need to ask.
Does MPM work using the hub feature? Or does it do its own calculations and switch when it thinks its best?
December 14, 2017, 12:19:18 PM
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.
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.
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.
Definately better then the FAQ.
except its wrong about many things (djmuk's theory)
December 14, 2017, 12:16:06 PM
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.
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.
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.
Definately better then the FAQ. Took me 2 days of pissing around to figure out how everything worked. The site usability is horrific (I'm a 20+ yr developer) and the explanations of how things work are scattered throughout different areas of the site. Kinda looks like my old admin back-end pages from the 1990s.
On the other hand, I've been happy with the pool so far even though it takes forever to confirm the coins. They seems to have a good system for choosing what coin to mine.
December 14, 2017, 10:33:19 AM
Why not say 'support in forum only' - or create a separate forum thread for support issues...
People don't read the FAQs. Nor do they want to wait, they want answers and they want them now. Its a big job for one person, and no matter how you approach it there will be people complaining. Just do the best you can, I've been mining on MPH for some months now and recently began upgrading my mining rigs to be even more profitable than before. According to a few sample runs I've made, I'm actually getting a higher payout than Nicehash says my rig would have produced. A little extra effort in setting up and tuning goes a long way, but all the people spoiled by nicehash's automation don't really know how to set a miner and are complaining about having to do things the old fashioned way.
Got email from admin telling me that my siacoin sent to bittrex is gone cause of their wallet.
4days of mining gone. just left MPH for good.
4days of mining gone. just left MPH for good.
Hi
I'm miningpoolhub op.
I didn't answer that kind of message.
You siacoin is not lost. It will come back when bittrex enables siacoin wallet.
I posted a link to r/siacoin a page or so ago with details of what is going on. The gist of it is that Bittrex's wallet cannot handle the transaction volume currently going on, and rather than risk severe data corruption and loss of coin they have opted to suspend wallet operations temporarily until the siacoin dev team can provide a solution. There should be an updated siacoin wallet out in a few days, and more to come once fixes for bittrex are released.
Might be worth updating the pool announcement regarding siacoin with this info and the reddit link, that way people aren't left wondering.
December 14, 2017, 09:37:11 AM
Hi
I'm miningpoolhub op.
Hi,I'm miningpoolhub op.
Could you add to auto-switches groups yet another Nvidia group -- with equihash, lyra2re2 and lyra2z together?
As far as I can see, for auto algo-switches at the moment it's possible to have either equhash+lyra2re2 or lyra2re2+lyra2z.
Thanks!
Jump to: