[ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin.

[btc3769]

You create 5 different pools with different priorities, but they'll need to be the 5 highest priorities in your list. I have mine setup as 4,5,6,7,8,9 (lets me add something as 1,2,3 if I wanted to). Miningpoolhub will automatically shut down the ports it's not using when it switches between them. For example, if it's auto-switching on x11, the x13, x15, quark and qubit pools will show as 'down' in the baikal because miningpoolhub has shut them off, letting the baikal auto switch to them.

[1714328074]

1714328074

[1714328074]

1714328074

[1714328074]

1714328074

[datlant]

You create 5 different pools with different priorities, but they'll need to be the 5 highest priorities in your list. I have mine setup as 4,5,6,7,8,9 (lets me add something as 1,2,3 if I wanted to). Miningpoolhub will automatically shut down the ports it's not using when it switches between them. For example, if it's auto-switching on x11, the x13, x15, quark and qubit pools will show as 'down' in the baikal because miningpoolhub has shut them off, letting the baikal auto switch to them.

@btc3769, thanks a lot!

[carlo_0000]

myriad yescrypt pool gonna be add when qubits is remove ?

[Tai_Pan]

You create 5 different pools with different priorities, but they'll need to be the 5 highest priorities in your list. I have mine setup as 4,5,6,7,8,9 (lets me add something as 1,2,3 if I wanted to). Miningpoolhub will automatically shut down the ports it's not using when it switches between them. For example, if it's auto-switching on x11, the x13, x15, quark and qubit pools will show as 'down' in the baikal because miningpoolhub has shut them off, letting the baikal auto switch to them.

Do you own a Baikal?

[btc3769]

I do, why?

[TanteStefana2]

Dash must be updated to latest wallet or mining will be rejected    

0.12.0.58

[avirdoz]

Ethereum pool down?

[TanteStefana2]

Baikal Miner Setting for MiningPoolHub


1. Set each algo and server info like below. These server and port numbers are written at FAQ page also.

quark : stratum+tcp://hub.miningpoolhub.com:12015
qubit : stratum+tcp://hub.miningpoolhub.com:12014
x15 : stratum+tcp://hub.miningpoolhub.com:12009
x13 : stratum+tcp://hub.miningpoolhub.com:12008
x11 : stratum+tcp://hub.miningpoolhub.com:12007


2. Set "ASIC Baikal - Quark, Qubit, x11, x13, x15" at Hub worker page.
https://miningpoolhub.com/?page=account&action=hubworkers


3. You can also set some coin (like Bitcoin) at Auto Exchange page to get all coins exchanged. (optional)
https://miningpoolhub.com/?page=account&action=autoexchange

You really need to double check and make sure that your on the correct wallet.  Dash forked yesterday with older wallet versions.  You post you're on 0.12.0.56 but you should be on 0.12.0.58.  If you're on the wrong chain, all the mining going on right now could be for naught.  So I'm afraid to mine in case we don't get paid.

[miningpoolhub]

You create 5 different pools with different priorities, but they'll need to be the 5 highest priorities in your list. I have mine setup as 4,5,6,7,8,9 (lets me add something as 1,2,3 if I wanted to). Miningpoolhub will automatically shut down the ports it's not using when it switches between them. For example, if it's auto-switching on x11, the x13, x15, quark and qubit pools will show as 'down' in the baikal because miningpoolhub has shut them off, letting the baikal auto switch to them.

Hi
I don't have baikal miner yet, so have limited knowledge about it.

Is it possible to set same priorities to each algo pool?
I hope it to stop useless pool alive checking when current connection (algo) is alive.

[miningpoolhub]

Dash must be updated to latest wallet or mining will be rejected    

0.12.0.58

Oh, it's already updated few months ago.
We are on the right chain. I just forgot to mention it on Dash news page.

[miningpoolhub]

Ethereum pool down?

Nope. it's working well.
Please try again.

[miningpoolhub]

You really need to double check and make sure that your on the correct wallet.  Dash forked yesterday with older wallet versions.  You post you're on 0.12.0.56 but you should be on 0.12.0.58.  If you're on the wrong chain, all the mining going on right now could be for naught.  So I'm afraid to mine in case we don't get paid.

I updated few months ago.
We are on the right chain. I just forgot to mention it on Dash news page.

Sorry for inconvenience.

[miningpoolhub]

myriad yescrypt pool gonna be add when qubits is remove ?

Well, not sure at this moment.
New Myriadcoin wallet has some bloating memory issues currently. I would open yescrypt pool if this issue is fixed.

[TanteStefana2]

Dash must be updated to latest wallet or mining will be rejected    

0.12.0.58

Oh, it's already updated few months ago.
We are on the right chain. I just forgot to mention it on Dash news page.

Awesome, thank you!

[btc3769]

Hi
I don't have baikal miner yet, so have limited knowledge about it.

Is it possible to set same priorities to each algo pool?
I hope it to stop useless pool alive checking when current connection (algo) is alive.

Baikal allows you to set different priorities for each port (algo) in the list of pools. It will automatically switch to a new algo when you take a port offline, so it works fine for now. The only thing it doesn't do, which causes issues within Miningpoolhub is allow someone to set difficulties separately for each pool. Would it be possible on the miningpoolhub end to set difficulties for the baikal mining pool for smaller coins (digibyte, etc) to 256 and to whatever lower setting is better for Dash or other 'harder' coins? I have noticed when I keep the difficulty setting at 256 I get lots of rejected shares, but if I take it off I don't think I'm being as efficient with the smaller coins.

Thanks!

[miningpoolhub]

Hi
I don't have baikal miner yet, so have limited knowledge about it.

Is it possible to set same priorities to each algo pool?
I hope it to stop useless pool alive checking when current connection (algo) is alive.

Baikal allows you to set different priorities for each port (algo) in the list of pools. It will automatically switch to a new algo when you take a port offline, so it works fine for now. The only thing it doesn't do, which causes issues within Miningpoolhub is allow someone to set difficulties separately for each pool. Would it be possible on the miningpoolhub end to set difficulties for the baikal mining pool for smaller coins (digibyte, etc) to 256 and to whatever lower setting is better for Dash or other 'harder' coins? I have noticed when I keep the difficulty setting at 256 I get lots of rejected shares, but if I take it off I don't think I'm being as efficient with the smaller coins.

Thanks!

Each pool remembers last mined difficulty value and resumes from that value after reconnection.
(Different algo pool works independently, they use their own difficulty level)

If you want to set starting diff, try to set worker password as "d=256"
More info about setting start difficulty is here
https://bitcointalk.org/index.php?topic=472510.msg10596890#msg10596890

If your issue is about Qubit algo pool, they would have some difficulty mulitplier issue.
I'm not sure about this issue with Baikal miner, but sgminer and ccminer used different factor for difficulty level. So, ccminer needed difficulty multiplier value for 256 or 0.00390625 (1/256) to mine.

Can you clarify what coin you seem to have problem? And what difficulty value was set at website worker page.

[btc3769]

Each pool remembers last mined difficulty value and resumes from that value after reconnection.
(Different algo pool works independently, they use their own difficulty level)

If you want to set starting diff, try to set worker password as "d=256"
More info about setting start difficulty is here
https://bitcointalk.org/index.php?topic=472510.msg10596890#msg10596890

If your issue is about Qubit algo pool, they would have some difficulty mulitplier issue.
I'm not sure about this issue with Baikal miner, but sgminer and ccminer used different factor for difficulty level. So, ccminer needed difficulty multiplier value for 256 or 0.00390625 (1/256) to mine.

Can you clarify what coin you seem to have problem? And what difficulty value was set at website worker page.

It's hard for me to say right now. I can say I have my difficulty setting manually set to 256 in my baikal miner (diff-multiplier 256), but currently we're on Dash in the auto-pool and my worker shows a difficulty of 1.58, and a rejected rate of ~1%. I almost always see 0% with anything except Dash-do you think this is because I've set my difficulty at 256, and, if I remove that 256 diff setting, will other, easier coins have the same issue?

[miningpoolhub]

It's hard for me to say right now. I can say I have my difficulty setting manually set to 256 in my baikal miner (diff-multiplier 256), but currently we're on Dash in the auto-pool and my worker shows a difficulty of 1.58, and a rejected rate of ~1%. I almost always see 0% with anything except Dash-do you think this is because I've set my difficulty at 256, and, if I remove that 256 diff setting, will other, easier coins have the same issue?

I don't think x11 needs diff-multiplier settings, as x11 algo didn't have difficulty factor incompatibility issue from the start.
(Only qubit would need that option. Maybe it doesn't need that option at all. You can test it by changing diff-multiplier and see the reject rate from dashboard)


~1% reject is normal. Stale shares (little bit late share) can be rejected, and it can happen to any coin.
The reason why you see ~1% reject only from Dash is because Dash is the most profitable coin lately and pool mostly mine that. Other coins would not have long enough time to be mined.


1. Does diff-multiplier affects whole (X11, Qubit, Quark) algo settings?
2. Is your x11 hashrate reported correctly on pool even you set diff-multiplier? Then Baikal's diff-multiplier option doesn't seem to work with x11.

[btc3769]

I don't think x11 needs diff-multiplier settings, as x11 algo didn't have difficulty factor incompatibility issue from the start.
(Only qubit would need that option. Maybe it doesn't need that option at all. You can test it by changing diff-multiplier and see the reject rate from dashboard)


~1% reject is normal. Stale shares (little bit late share) can be rejected, and it can happen to any coin.
The reason why you see ~1% reject only from Dash is because Dash is the most profitable coin lately and pool mostly mine that. Other coins would not have long enough time to be mined.


1. Does diff-multiplier affects whole (X11, Qubit, Quark) algo settings?
2. Is your x11 hashrate reported correctly on pool even you set diff-multiplier? Then Baikal's diff-multiplier option doesn't seem to work with x11.

The diff-multiplier is a single setting which I believe affects all pools (there's no way to set specific pools or algos, so I've no idea, but this is my guess). I know I had the diff-multiplier set a couple days ago, noticed we were mining Dash, and that I was seeing around 20-30% rejected packets, so I shut off the diff multiplier and it fell back to 0-1%, so I thought it was that setting. Now I have it on again, though, and all seems to be working, so I'll keep an eye on things and let you know if there are more issues

[btc3769]

Also, would there be any way to turn auto-exchange on, but prevent some coins from participating? For example, I would like to auto-exchange Uro and Smartcoin, but I would rather not exchange DASH and ETH. Is there a way to enable this?