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

[miningpoolhub]

Maybe my answer will be the same for ZCL Pool. This is what I am getting using silentarmy v5 through ethOS

Connecting to us-east.equihash-hub.miningpoolhub.com:20575                                                                                 
Stratum: invalid msg from server: mining.authorize failed: {'id': 2, 'result': False, 'error': None}   

Settings found in here -
http://paste.ethosdistro.com/xupuzekini

Not sure if I need this?
--use 0 -c stratum+tcp://us-east.equihash-hub.miningpoolhub.com:20575 -u Gutz211.da0d0b -p x

Can you try it again? I tried it with same username and server info and succeded with Claymore miner.
I haven't tried it with silentarmy yet but it would work now.

I don't know what happened at that time but seems like there were some db connection failure or something.
I'll investigate it right now.

I have tried again and got something a bit different - These are my settings in ethOS

--use 0 -c stratum+tcp://us-east.equihash-hub.miningpoolhub.com:20575 -u Gutz211.da0d0b -p x
proxywallet t1XYFVzyd6u7My4uKAe8zt5CeG1deCsFyAQ
proxypool1 us-east.equihash-hub.miningpoolhub.com:20575
proxypool1 us-east1.zclassic.miningpoolhub.com :20575
globalminer zcash-miner

and this is the error I am getting now -

silentarmy: error: Extraneous arguments found on command line   

As always, thanks for your time

I can't test ethOS as I don't have that one but as I read the instruction( http://ethosdistro.com/kb/#mining-zcash ), I think proxywallet should be Gutz211.da0d0b not wallet.
(MiningPoolHub doesn't use wallet authorization for mining, but username is used instead)

"silentarmy: error: Extraneous arguments found on command line" is related to commandline argument problem.
I recommend you to check commandline arguments or contact ethOS dev. I believe they have simple answer about it.

[miningpoolhub]

Port 17023 is down on Nicehash and Claymore. Same error on both: Authorization failed
Zclassic appears to be breaking it as it is back up again.

What server location have you used?
Can you tell me exact server info and username?

I tested all three servers with Nicehash and Claymore but they are all working well now.

Orders are down again on Nicehash because it has switched to Zclassic. Server details are automatically taken from the API like I have on every other algorithm:
stratum+tcp://us-east1.hub.miningpoolhub.com:17023
stratum+tcp://europe1.hub.miningpoolhub.com:17023
aaronsace.nicehash_equihash:x

us-east1.hub.miningpoolhub.com
europe1.hub.miningpoolhub.com

These are not official servers. I will open them soon but not currently.



Please use below.

U.S.     :   us-east.equihash-hub.miningpoolhub.com:17023
Europe :   europe.equihash-hub.miningpoolhub.com:17023
Asia     :   asia.equihash-hub.miningpoolhub.com:17023

These are dedicated servers for equihash (zec/zcl)

[miningpoolhub]

Haven´t your pool any static ports for ZClassic, like some other pools?
Or at least a "remember-last-diff-on-dis-/reconnect-same-worker"-function?

Miningpoolhub doesn't provide static diff ports currently as it's worse than vardiff in performance.

But every ports remember last diff and start from that difficulty level when reconnects.

Or you can specify starting difficulty value at the password field like below
d=12345
Learn more about difficulty hint at below link.
https://bitcointalk.org/index.php?topic=472510.msg10596890#msg10596890

[aaronsace]

Port 17023 is down on Nicehash and Claymore. Same error on both: Authorization failed
Zclassic appears to be breaking it as it is back up again.

What server location have you used?
Can you tell me exact server info and username?

I tested all three servers with Nicehash and Claymore but they are all working well now.

Orders are down again on Nicehash because it has switched to Zclassic. Server details are automatically taken from the API like I have on every other algorithm:
stratum+tcp://us-east1.hub.miningpoolhub.com:17023
stratum+tcp://europe1.hub.miningpoolhub.com:17023
aaronsace.nicehash_equihash:x

us-east1.hub.miningpoolhub.com
europe1.hub.miningpoolhub.com

These are not official servers. I will open them soon but not currently.



Please use below.

U.S.     :   us-east.equihash-hub.miningpoolhub.com:17023
Europe :   europe.equihash-hub.miningpoolhub.com:17023
Asia     :   asia.equihash-hub.miningpoolhub.com:17023

These are dedicated servers for equihash (zec/zcl)

Alright, bit a pain as it's all pulled from your API like always.
I'll have to manually change it and cancel them all then.

Thank you for your help.

[miningpoolhub]

Alright, bit a pain as it's all pulled from your API like always.
I'll have to manually change it and cancel them all then.

Thank you for your help.

Oh.. sorry about it.

I enabled zec/zcl, and auto switching ports for hub.miningpoolhub.com host now.
And I fixed API responses for algorithms that have dedicated servers.

Sorry again.

[miningpoolhub]

Zcash payout daemon was crashed.
Automatic zcash recovery program caught the error and recovered from critical error.

Sorry for little bit delayed payouts.

[aaronsace]

Alright, bit a pain as it's all pulled from your API like always.
I'll have to manually change it and cancel them all then.

Thank you for your help.

Oh.. sorry about it.

I enabled zec/zcl, and auto switching ports for hub.miningpoolhub.com host now.
And I fixed API responses for algorithms that have dedicated servers.

Sorry again.

For some reason the difficulty has dropped below 63 now...
I sent my miner to the worker name to push it back up. How do I prevent it doing that again without sending my miner to it?

Edit: It still keeps dropping below 63. It had been working fine for days; has something changed?
"d=64" does nothing; still connects at 60.23529400.

Notice: Pool verificator may may not be 100% accurate and may report pool being compatible while in fact it is not compatible or vice versa. Always discuss with pool operator if you encounter any issues with the pool verificator.

Pool host: europe.equihash-hub.miningpoolhub.com
Pool port: 17023
Pool user: aaronsace.nicehash_equihash
Pool pass: d=64
Algorithm: Equihash

Resolving pool host europe.equihash-hub.miningpoolhub.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 46.101.243.246:17023... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_target... Pool difficulty too low (provided=60.23529412, minimum=63)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Error: Read timed out
Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you!

Close

[miningpoolhub]

Zcash payout daemon was crashed.
Automatic zcash recovery program caught the error and recovered from critical error.

Sorry for little bit delayed payouts.

All things resolved few hours ago. Forgot to post this message  

[miningpoolhub]

For some reason the difficulty has dropped below 63 now...
I sent my miner to the worker name to push it back up. How do I prevent it doing that again without sending my miner to it?

Why are you trying to keep difficulty higher than 63?

Edit: It still keeps dropping below 63. It had been working fine for days; has something changed?
"d=64" does nothing; still connects at 60.23529400.

Well nothing changed. I even didn't restart the pool.
d=64 is just hint for "starting" of difficulty level. It will start from 64 at connection but will adjusted by vardiff mechanism as time passes.

Decreased difficulty doesn't mean that your miner works less. Every pool has different target time, which makes difficulty level specific to that pool only.

For example, MiningPoolHub have set target time as 20 seconds for every miners. It means every miner should submit one shares every 20 seconds in average.
If I set longer target time like 60 seconds, you will get much higher difficulty.
Or if I set target time like 10 seconds, you will get lower difficulty and submit shares more often.

The reward is calculated by sum of share difficulty. So it's just same that when you submit 30 difficulty share twice or 60 difficulty share once.

Vardiff is doing its work to optimize the balance between mining power and share verification.
So, don't worry about difficulty level.

[miningpoolhub]

Hello MiningPoolHub-Miners,

I have written a little application which helps miners to easily start mining on the MiningPoolHub-Pool.

It is available on github: https://github.com/piotrek1668/mph-manager/releases

For now zcash, zclassic, ethereum and ethereum-classic simple coin mining are available to mine through this app.



Have fun with this tool! 
Piba88

Thank you for your effort.
I sent 0.2 BTC donation for you. Not that much but wanted to say thank you.
txid : 73883708a74795c2b9306759edc8642d45ea5f2b243ea64525f38f94eaf5ef9a

May I introduce this app at main homepage?
Maybe adding more coins would be good.

[aaronsace]

For some reason the difficulty has dropped below 63 now...
I sent my miner to the worker name to push it back up. How do I prevent it doing that again without sending my miner to it?

Why are you trying to keep difficulty higher than 63?

Edit: It still keeps dropping below 63. It had been working fine for days; has something changed?
"d=64" does nothing; still connects at 60.23529400.

Well nothing changed. I even didn't restart the pool.
d=64 is just hint for "starting" of difficulty level. It will start from 64 at connection but will adjusted by vardiff mechanism as time passes.

Decreased difficulty doesn't mean that your miner works less. Every pool has different target time, which makes difficulty level specific to that pool only.

For example, MiningPoolHub have set target time as 20 seconds for every miners. It means every miner should submit one shares every 20 seconds in average.
If I set longer target time like 60 seconds, you will get much higher difficulty.
Or if I set target time like 10 seconds, you will get lower difficulty and submit shares more often.

The reward is calculated by sum of share difficulty. So it's just same that when you submit 30 difficulty share twice or 60 difficulty share once.

Vardiff is doing its work to optimize the balance between mining power and share verification.
So, don't worry about difficulty level.

Nicehash has a minimum of 63. It would push the difficulty back up if it started mining but it drops below 63 before it ever gets chance; catch 22. It had been working perfectly fine before like every other algorithm. To stop this happening, you need to set your minimum difficulty on your Nicehash stratum to 63; or maybe stop decreasing the difficulty when idle.

The minimum currently on your pool seems to be '60.23529400'. Fixed orders are not working either; they are dropping to '60.23529400' even though they are at running at 500sols then they die.

I was getting 2 zec a day before it stopped working.

Edit: Think I have got 2 fixed orders on Nicehash going before the difficulty dropped. The rest of the idle orders are still dropping down in difficulty then die.
'd=10000' doesn't do anything.

Had a long run but a fixed order just dropped to '60.54927100' difficulty again and died:
free photo hosting

Idle orders are just endless drops:
free image hosting

It works but with it dead 50% of the time, it's pot luck:
image sharing sites

Please fix soon! Thanks!

[Biterion]

Dear Miningpoolhub,

i saw problem in my desktop interface,
for more 12 hours nothing got reward..
i mining ZCL with nothing problem with my miner
it's normal..?

i'm connect to: asia.equihash-hub.miningpoolhub.com:20575

need your explaination..
thanks

PIC:

https://s11.postimg.org/w2lu5bt37/Screenshot_3.jpg

[miningpoolhub]

Nicehash has a minimum of 63. It would push the difficulty back up if it started mining but it drops below 63 before it ever gets chance; catch 22. It had been working perfectly fine before like every other algorithm. To stop this happening, you need to set your minimum difficulty on your Nicehash stratum to 63; or maybe stop decreasing the difficulty when idle.

The minimum currently on your pool seems to be '60.23529400'. Fixed orders are not working either; they are dropping to '60.23529400' even though they are at running at 500sols then they die.

I was getting 2 zec a day before it stopped working.

Edit: Think I have got 2 fixed orders on Nicehash going before the difficulty dropped. The rest of the idle orders are still dropping down in difficulty then die.
'd=10000' doesn't do anything.

Had a long run but a fixed order just dropped to '60.54927100' difficulty again and died:
free photo hosting

Idle orders are just endless drops:
free image hosting

It works but with it dead 50% of the time, it's pot luck:
image sharing sites

Please fix soon! Thanks!

Ah.. didn't know that nicehash changed its minimum difficulty value. (It was 16 at first)

I fixed this value. You will get 64 minimum diff when connected from nicehash.

Thanks.

[miningpoolhub]

Dear Miningpoolhub,

i saw problem in my desktop interface,
for more 12 hours nothing got reward..
i mining ZCL with nothing problem with my miner
it's normal..?

i'm connect to: asia.equihash-hub.miningpoolhub.com:20575

need your explaination..
thanks

PIC:

Hi
There were some payout wallet crash problem recently.
mining was not affected, but pool info update was delayed for few hours.

It's all resolved now.
Please check your account again.

Sorry for inconvenience.

[aaronsace]

Ah.. didn't know that nicehash changed its minimum difficulty value. (It was 16 at first)

I fixed this value. You will get 64 minimum diff when connected from nicehash.

Thanks.

Boom, it's back! Thank you!

[aaronsace]

My balance keeps going up and down when monitoring the API because the 'On Exchange' column is missing; would you be able to add it on?
Or better yet, have a single balance from all of the pools added together (total estimate in your auto exchange currency).

Code:

{
    "getdashboarddata": {
        "version": "1.0.0",
        "runtime": 1657.438993454,
        "data": {
            "raw": {
                "personal": {
                    "hashrate": 1.189
                },
                "pool": {
                    "hashrate": 652.0897
                },
                "network": {
                    "hashrate": 24533.046,
                    "esttimeperblock": 148.09807957944,
                    "nextdifficulty": 449108.41031343,
                    "blocksuntildiffchange": 1
                }
            },
            "personal": {
                "hashrate": 1189,
                "sharerate": 0.0367,
                "sharedifficulty": 506.66618485884,
                "shares": {
                    "valid": 7680.6602392495,
                    "invalid": 25.855108737946,
                    "invalid_percent": 0.34,
                    "unpaid": 0
                },
                "estimates": {
                    "block": 0.01377049,
                    "fee": 0.00012393,
                    "donation": 0,
                    "payout": 0.01364656
                }
            },
            "balance": {
                "confirmed": 0,
                "unconfirmed": 0,
                "orphaned": 0
            },
            "balance_for_auto_exchange": {
                "confirmed": 0,
                "unconfirmed": 0.01713859,
                "orphaned": 0
            },
            "recent_credits_24hours": {
                "amount": 1.02882701
            },
            "recent_credits": [{
                "date": "2016-11-18",
                "amount": 0.01729424
            }, {
                "date": "2016-11-17",
                "amount": 1.01397453
            }, {
                "date": "2016-11-16",
                "amount": 0.7994299
            }, {
                "date": "2016-11-15",
                "amount": 2.04364841
            }, {
                "date": "2016-11-14",
                "amount": 1.50125841
            }, {
                "date": "2016-11-13",
                "amount": 3.97025695
            }, {
                "date": "2016-11-12",
                "amount": 2.44823804
            }],
            "pool": {
                "info": {
                    "name": "Zcash(ZEC) Mining Pool Hub",
                    "currency": "ZEC"
                },
                "workers": 1659,
                "hashrate": 652.0897,
                "shares": {
                    "valid": 3350490.7322354,
                    "invalid": 74886.499688618,
                    "invalid_percent": 2.19,
                    "estimated": 3725232,
                    "progress": 89.94
                },
                "price": "",
                "difficulty": 16,
                "target_bits": 20
            },
            "system": {
                "load": [5.26, 3.91, 2.99]
            },
            "network": {
                "hashrate": 24533.046,
                "difficulty": 465653.93874343,
                "block": 12231,
                "esttimeperblock": 148.1,
                "nextdifficulty": 449108.41031343,
                "blocksuntildiffchange": 1
            }
        }
    }
}

free pic

[Biterion]

Dear Miningpoolhub,

i saw problem in my desktop interface,
for more 12 hours nothing got reward..
i mining ZCL with nothing problem with my miner
it's normal..?

i'm connect to: asia.equihash-hub.miningpoolhub.com:20575

need your explaination..
thanks

PIC:

https://s11.postimg.org/w2lu5bt37/Screenshot_3.jpg

Hi
There were some payout wallet crash problem recently.
mining was not affected, but pool info update was delayed for few hours.

It's all resolved now.
Please check your account again.

Sorry for inconvenience.

yeah...
after wake up from my sleep this morning (gmt+7), i saw my desktop interface was running well..
until now my earning show up without problem again...

thanks to you @Miningpoolhub

enjoy mining with you

[miningpoolhub]

My balance keeps going up and down when monitoring the API because the 'On Exchange' column is missing; would you be able to add it on?
Or better yet, have a single balance from all of the pools added together (total estimate in your auto exchange currency).

Code:

{
    "getdashboarddata": {
        "version": "1.0.0",
        "runtime": 1657.438993454,
        "data": {
            "raw": {
                "personal": {
                    "hashrate": 1.189
                },
                "pool": {
                    "hashrate": 652.0897
                },
                "network": {
                    "hashrate": 24533.046,
                    "esttimeperblock": 148.09807957944,
                    "nextdifficulty": 449108.41031343,
                    "blocksuntildiffchange": 1
                }
            },
            "personal": {
                "hashrate": 1189,
                "sharerate": 0.0367,
                "sharedifficulty": 506.66618485884,
                "shares": {
                    "valid": 7680.6602392495,
                    "invalid": 25.855108737946,
                    "invalid_percent": 0.34,
                    "unpaid": 0
                },
                "estimates": {
                    "block": 0.01377049,
                    "fee": 0.00012393,
                    "donation": 0,
                    "payout": 0.01364656
                }
            },
            "balance": {
                "confirmed": 0,
                "unconfirmed": 0,
                "orphaned": 0
            },
            "balance_for_auto_exchange": {
                "confirmed": 0,
                "unconfirmed": 0.01713859,
                "orphaned": 0
            },
            "recent_credits_24hours": {
                "amount": 1.02882701
            },
            "recent_credits": [{
                "date": "2016-11-18",
                "amount": 0.01729424
            }, {
                "date": "2016-11-17",
                "amount": 1.01397453
            }, {
                "date": "2016-11-16",
                "amount": 0.7994299
            }, {
                "date": "2016-11-15",
                "amount": 2.04364841
            }, {
                "date": "2016-11-14",
                "amount": 1.50125841
            }, {
                "date": "2016-11-13",
                "amount": 3.97025695
            }, {
                "date": "2016-11-12",
                "amount": 2.44823804
            }],
            "pool": {
                "info": {
                    "name": "Zcash(ZEC) Mining Pool Hub",
                    "currency": "ZEC"
                },
                "workers": 1659,
                "hashrate": 652.0897,
                "shares": {
                    "valid": 3350490.7322354,
                    "invalid": 74886.499688618,
                    "invalid_percent": 2.19,
                    "estimated": 3725232,
                    "progress": 89.94
                },
                "price": "",
                "difficulty": 16,
                "target_bits": 20
            },
            "system": {
                "load": [5.26, 3.91, 2.99]
            },
            "network": {
                "hashrate": 24533.046,
                "difficulty": 465653.93874343,
                "block": 12231,
                "esttimeperblock": 148.1,
                "nextdifficulty": 449108.41031343,
                "blocksuntildiffchange": 1
            }
        }
    }
}

free pic

I added "balance_on_exchange" for getdashboarddata api call.
I hope you like it.

I will add more data on API soon as you suggested.

[miningpoolhub]

yeah...
after wake up from my sleep this morning (gmt+7), i saw my desktop interface was running well..
until now my earning show up without problem again...

thanks to you @Miningpoolhub

enjoy mining with you

You're welcome.
 

[aaronsace]

I added "balance_on_exchange" for getdashboarddata api call.
I hope you like it.

I will add more data on API soon as you suggested.

You're awesome, thank you!