Author

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

newbie
Activity: 27
Merit: 0
When mining DGB - Skein.....is there any advantage to setting difficulty directly in miner?
newbie
Activity: 9
Merit: 0
No reply from miningpoolhub.com
I'm worried now what will happen to my earning.
Anyone .. what should i do now?
Mods please help.
@ miningpoolhub.com moderater, Kindly solve my problem.
Its been almost 2 days.
Im worried about payments.
full member
Activity: 235
Merit: 100
Your different hash rates are based on 2 things.  First, your real time hash as seen by your cards on your side, and the lower number is the hash seen by the pool for your successful hashes. Pool will be lower always as your submitted shares will never be exactly what you're hashing at.

As a request for the pool operator, is there a way you can add the newer equihash coins to the multipool?  Zencash and Hush would fit in well for the multipool to swing to when their difficultly drops.
legendary
Activity: 1274
Merit: 1006
Today I started mining on your pool.
I was mining for few hours with 2 workers, of which 1 worked (2x GTX 1060) didn't show real speed.
In actual miner i get about 44MH/s but on the pool it showed speed of ~23MH/s.
Any idea why?
jr. member
Activity: 85
Merit: 1
may i know, how long is the processing time for on-demand withdrawal?
is withdrawal to ETH has been enabled?
sr. member
Activity: 476
Merit: 250
No reply from miningpoolhub.com
I'm worried now what will happen to my earning.
Anyone .. what should i do now?
Mods please help.

Don't worry, MiningPoolHub can check your account but the pool is working: https://zcash.miningpoolhub.com/index.php?page=statistics&action=blocks
newbie
Activity: 9
Merit: 0
No reply from miningpoolhub.com
I'm worried now what will happen to my earning.
Anyone .. what should i do now?
Mods please help.
newbie
Activity: 9
Merit: 0
Hi,
 I have been mining on your miningpoolhub.com for ZCash since 3 days.
Earlier the payments used to show in the wallet within 1/2 an hr or so.
But since yesterday evening, i have mined multiple times, but shill no payment , not even unconfirmed ones are shown there.
The graph shows my work but wallet balance and transaction all none.
Kindly help here, its been 25-30 hrs since.
Should i be worried.
sr. member
Activity: 305
Merit: 250
How to configure to use ethos?
Could you tell the configuration to eth?
jr. member
Activity: 48
Merit: 11
Thanks a lot for correction of ETH problem. I see my my ETH back in wallet.
Thanks! Best pool support ever  Cheesy

Indeed I can confirm mine was returned back as well! Shows up as credit with n/a for block #. Thanks for the effort miningpoolhub! Much appreciated!

Quote
- Overloaded Ethereum network due to Status, Skincoin ICO needs higher txfee and almost 2~3 hours for transfer. Enabled manual payout and auto exchange only.
  Recent 619 omitted withdrawal transactions that are not written in blockchain are all credited to each account with txfee added. Please withdraw them again.
  Sorry for late. Scanned all withdrawals one by one to make sure all things are correct.

211560991   2017-06-21 09:12:13 (UTC)   Credit   Confirmed         n/a

full member
Activity: 154
Merit: 100
Ive tried running DGB-Groestl with ccminer (tried a bunch of different versions). But im always getting an insane amount of rejects. Mainly because of low diff rate. Never had such problems with DGB-Skein. Can someone help me out?

You likely need to use Myriad-Groestl or myr-gr as that is usually what DGB-Groestl pools accept for hashes since it is about 45% faster.
member
Activity: 142
Merit: 10
Thanks a lot for correction of ETH problem. I see my my ETH back in wallet.
Thanks! Best pool support ever  Cheesy
newbie
Activity: 4
Merit: 0
Ive tried running DGB-Groestl with ccminer (tried a bunch of different versions). But im always getting an insane amount of rejects. Mainly because of low diff rate. Never had such problems with DGB-Skein. Can someone help me out?
hero member
Activity: 698
Merit: 500
can you make eth daemon to include zero fee transactions with blocks you mine, just like you can with mining bitcoin thus making your own transactions free?
full member
Activity: 304
Merit: 100
MPH, could you possibly add LBRY to the pool? Nemo's nVidia miner could do with LBRY as auto-switching coin too...

EDIT: I'd rather use MPH than zpool  Wink

Yeah I'll add that.
I'd recommend you to mine at zpool for now. Then come and mine with us when LBRY pool is ready.

Hey boss, does that mean you finally commit to the promise and deliver LBRY, Decred and Pascal in a more acceptable time frame? Also Zen, Hush, Komodo, Ubiq pretty please. Smiley
newbie
Activity: 3
Merit: 0
I also have a transaction stuck since the 19th. It`s ID 8151669, done on 2017-06-19 08:42:12 (UTC) It hasn`t showed up in the destination wallet yet
jr. member
Activity: 48
Merit: 11
I know the status at top of pool page says ETH network overloaded & withdrawals disabled but what about the withdrawals done before (as in earlier today) that are stuck?  They say confirmed under transactions but are not found on any explorer. Are we to assume eventually they'll go? (it's been like 12 hours now for mine. It's in UTC time: 209982215   2017-06-20 15:08:12 (UTC))
Thx
Bill
newbie
Activity: 3
Merit: 0
Hello,

First time on miningpoolhub, rented some hashpower on nicehash and trying to connect port 17014 (qubit) but nicehash gives an error "difficulty too low" it says that it should be at least 0.05 but pools difficulty is 0.03 and because of that, it just doesn't even connects to the pool.
btw i have connected with password d=8 which works well with other pools that i'm using. Is there any configuration that i'm missing for nicehash?
user id: 61993



Don't need to set the difficulty.

It should be fine if nicehash would able to start mining and vardiff kicks in but it wouldn't even start mining because starting diff is too low for nicehash, it just disconnects.

Output of their pool verification without setting difficulty with password (same as setting diff with password):


Resolving pool host hub.miningpoolhub.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 34.224.196.33:17014... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=0.03, minimum=0.05)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.
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!





NiceHash have probably increased the minimum. Mine seems to be currently connected at 0.1 difficulty but it's obviously variable so it may drop to 0.03 and fail at some point. MiningPoolHub will have to check it.

Gonna have to wait for miningpoolhubs response then. Thanks anyway!
sr. member
Activity: 476
Merit: 250
Hello,

First time on miningpoolhub, rented some hashpower on nicehash and trying to connect port 17014 (qubit) but nicehash gives an error "difficulty too low" it says that it should be at least 0.05 but pools difficulty is 0.03 and because of that, it just doesn't even connects to the pool.
btw i have connected with password d=8 which works well with other pools that i'm using. Is there any configuration that i'm missing for nicehash?
user id: 61993



Don't need to set the difficulty.

It should be fine if nicehash would able to start mining and vardiff kicks in but it wouldn't even start mining because starting diff is too low for nicehash, it just disconnects.

Output of their pool verification without setting difficulty with password (same as setting diff with password):


Resolving pool host hub.miningpoolhub.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 34.224.196.33:17014... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=0.03, minimum=0.05)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.
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!





NiceHash have probably increased the minimum. Mine seems to be currently connected at 0.1 difficulty but it's obviously variable so it may drop to 0.03 and fail at some point. MiningPoolHub will have to check it.
newbie
Activity: 3
Merit: 0
Hello,

First time on miningpoolhub, rented some hashpower on nicehash and trying to connect port 17014 (qubit) but nicehash gives an error "difficulty too low" it says that it should be at least 0.05 but pools difficulty is 0.03 and because of that, it just doesn't even connects to the pool.
btw i have connected with password d=8 which works well with other pools that i'm using. Is there any configuration that i'm missing for nicehash?
user id: 61993



Don't need to set the difficulty.

It should be fine if nicehash would able to start mining and vardiff kicks in but it wouldn't even start mining because starting diff is too low for nicehash, it just disconnects.

Output of their pool verification without setting difficulty with password (same as setting diff with password):


Resolving pool host hub.miningpoolhub.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 34.224.196.33:17014... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=0.03, minimum=0.05)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.
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!



Jump to: