Topic: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin. - page 28. (Read 487517 times)
June 04, 2018, 08:30:21 PM
June 04, 2018, 07:43:19 PM
Block was finded at 2558% of luck and next also was finded.
All of them are orphaned.
Will now someone also say it's normal?
All of them are orphaned.
Will now someone also say it's normal?
June 04, 2018, 05:21:05 PM
its a like we lost an IT guy who knows stuff they use to let us know in advance now the users are telling them how to fix it.They now blocked my etn i can get it out.Her heir is horrible
As far as I know there is only one IT guy running the whole of MPH, he has had help in the past but for only a short time - don't know if he's now got more help or not, it's a 24/7 job if there is only one dev running MPH.
June 04, 2018, 04:48:40 PM
But they Have found 2 block! ... Ohh wait! - they are both Orphaned!
https://insight.zcoin.io/block/973eddd13844d711073498692cdc9f2190adae43948516d6e09082545c307cc6
https://insight.zcoin.io/block/b22d4d2fc54bc4014e85362c57e00b41758b01aa55d9c4e60e012353b65a147f
Can it get any worse?...
https://insight.zcoin.io/block/973eddd13844d711073498692cdc9f2190adae43948516d6e09082545c307cc6
https://insight.zcoin.io/block/b22d4d2fc54bc4014e85362c57e00b41758b01aa55d9c4e60e012353b65a147f
Can it get any worse?...
June 04, 2018, 04:40:40 PM
https://storage.googleapis.com/openscreenshot/X/e/7/ry2YbQ7eX.png
It isn't joke, it's tragedy.
2414%
My 16 rigs was heating already the hot air for 10 hours.
It's enaught
It isn't joke, it's tragedy.
2414%
My 16 rigs was heating already the hot air for 10 hours.
It's enaught
June 04, 2018, 01:49:29 PM
its a like we lost an IT guy who knows stuff they use to let us know in advance now the users are telling them how to fix it.They now blocked my etn i can get it out.Her heir is horrible
June 04, 2018, 01:33:49 PM
I think that only Domino can fix this pool's Luck 
June 04, 2018, 11:58:19 AM
Go figure, just yesterday Zcoin@MPH was getting better and pufff "somehow" it got "Cursed" again... I have a feeling that not every one is happy that we the small miners got improved zcoin miners, who knows maybe it's just my feeling...
Maybe You are right but because of 8h my rigs work, I prefer You are not. Now is over 1560% "un-luck"
How much have to wait to find out that this is something abnormal?
June 04, 2018, 11:20:08 AM
0 blocks in last 8 hours on xzc on mph,
What’s wrong with this pool?
Can you answer to us?
You make too much money from xzc miners on your pool but now when the pool has problem you have to be honest with us and tell us the truth...
waiting your comment!!!
What’s wrong with this pool?
Can you answer to us?
You make too much money from xzc miners on your pool but now when the pool has problem you have to be honest with us and tell us the truth...
waiting your comment!!!
June 04, 2018, 10:50:05 AM
My ETH isn't showing up at Bittrex. The wallet address is the same address for bittrex, it hasn't changed but when the transaction went through yesterday, poof! Gone. Can someone help me find it? It isn't much, as I don't have much of a mining "farm", one rig a farm doesn't make...But I didn't mine it to lose it. Any help would be greatly appreciated as MPH doesn't seem to have a contact us. Here is the transaction numbers from MPH if it helps
3112485864 2018-06-03 18:07:42 (UTC) Debit_MP Confirmed 0xe0b2bd...6794c6fb 0x55bcb1...a03c91a1 n/a 0.02257697
When clicked on the link it brings up this URL here
https://etherscan.io/tx/0x55bcb1de8324d58be034d26747d2df665a19afece1af5fb23364b61da03c91a1
So again, any help will be greatly appreciated, Thanks!!
KickinthaChicken
Edit: Problem Solved, kinda of. I didn't have enough ETH to actually complete the transaction, so I have to mine more or buy through the auto-exchange to get enough to get it to credit onto Bittrex. Maybe MPH should up the min. cash out so this doesn't happen to others.
3112485864 2018-06-03 18:07:42 (UTC) Debit_MP Confirmed 0xe0b2bd...6794c6fb 0x55bcb1...a03c91a1 n/a 0.02257697
When clicked on the link it brings up this URL here
https://etherscan.io/tx/0x55bcb1de8324d58be034d26747d2df665a19afece1af5fb23364b61da03c91a1
So again, any help will be greatly appreciated, Thanks!!
KickinthaChicken
Edit: Problem Solved, kinda of. I didn't have enough ETH to actually complete the transaction, so I have to mine more or buy through the auto-exchange to get enough to get it to credit onto Bittrex. Maybe MPH should up the min. cash out so this doesn't happen to others.
June 04, 2018, 10:26:35 AM
Go figure, just yesterday Zcoin@MPH was getting better and pufff "somehow" it got "Cursed" again... I have a feeling that not every one is happy that we the small miners got improved zcoin miners, who knows maybe it's just my feeling...
June 04, 2018, 10:09:28 AM
Whats going on?
MPH has over 1/3 of XZC hashrate now and "bad-luck" 1200%
Normally it isn't possible.
Some admin/owner something do with it?
MPH has over 1/3 of XZC hashrate now and "bad-luck" 1200%
Normally it isn't possible.
Some admin/owner something do with it?
June 04, 2018, 03:14:42 AM
Dear Zcoin miners @Mining Pool Hub:
I welcome you to check my Improved Lyra2Z nVidia miner for [Maxwell\Pascal\Volta] GPU's:
coolMiner Specs:
Benchmark resaults:
1080Ti - 3,750KH/s @2075Mhz core.
1070TI - 2,400KH/s @1987Mhz core (2,500 KH/s+ should be no problem with better OC).
1070 - 1,950KH/s @2025Mhz core (2,000 KH/s+ should be no problem with better OC).
ScreenShots:
1080Ti:
1070 and 1070Ti:
Please see more info on the ANN thread:
https://bitcointalksearch.org/topic/ann-coolminer-lyra2z-miner-for-nvidia-1080ti-375mhsmaxwellpascalvolta-4412370
I hope to hear your feedback.
Have a Cool Day.
I welcome you to check my Improved Lyra2Z nVidia miner for [Maxwell\Pascal\Volta] GPU's:
coolMiner Specs:
- Compiled with Cuda9.2, 64-bit.
- Compiled for nVidia Gpu's with SM_52/SM_61/SM_70 (Maxwell-Pascal-Volta).
- Max-GPU support increased to 20!.
- Stale share bug fixed.
- Lyra2z miner only.
Benchmark resaults:
1080Ti - 3,750KH/s @2075Mhz core.
1070TI - 2,400KH/s @1987Mhz core (2,500 KH/s+ should be no problem with better OC).
1070 - 1,950KH/s @2025Mhz core (2,000 KH/s+ should be no problem with better OC).
ScreenShots:
1080Ti:
1070 and 1070Ti:
Please see more info on the ANN thread:
https://bitcointalksearch.org/topic/ann-coolminer-lyra2z-miner-for-nvidia-1080ti-375mhsmaxwellpascalvolta-4412370
I hope to hear your feedback
.Have a Cool Day.
June 03, 2018, 09:50:06 PM
My problem is since this fork and gold hack they are not fixing thing nor they are issuing the credit before this it worked ok for me.they owe me money coins this is bull.
June 03, 2018, 06:26:51 PM
been mining Monro 9 days this place is broken don't waste your time, im assuming that the bitcoin gold is probably broken and ETN.
Been mining here since December of ‘17. Pool works fine.
I've been mining on MPH for over a year and found it to be, if not the best, then at least one of the best pools out there.
It has had some glitches but these get fixed and it's not like other pools run 100% all the time.
Would be nice if the dev made a bit of an appearance now and again, like he did in the past, just to know he's reading the thread.
June 03, 2018, 04:24:27 PM
been mining Monro 9 days this place is broken don't waste your time, im assuming that the bitcoin gold is probably broken and ETN.
Been mining here since December of ‘17. Pool works fine.
June 03, 2018, 11:54:55 AM
Here is a great explanation of why the ETN fork is so slow.
Edit: Original source - https://electroneum101.com/status-of-the-tech-update-fork/
Why are things so slow after the tech update/fork? Read up!
https://www.reddit.com/r/Electroneum/comments/8o7r7l/why_are_things_so_slow_after_the_tech_updatefork/
Edit: Original source - https://electroneum101.com/status-of-the-tech-update-fork/
Why are things so slow after the tech update/fork? Read up!
https://www.reddit.com/r/Electroneum/comments/8o7r7l/why_are_things_so_slow_after_the_tech_updatefork/
Quote
Why are things so slow after the tech update/fork? After the fork, blocks were being mined very slowly
The team initially thought that the high difficulty was the big culprit for this, coupled with the low hash rate. They reasoned that we were trying to mine blocks at a high difficulty with low hashing power (since all the ASIC miners are now gone) and that it should take time before the difficulty starts adjusting. Read more about how difficulty works here.
But that was only part of the problem...
The real problem (identified here) was related to a feature that was being removed in the new update, ring signatures, and the implementation thereof. Ring signatures were used in the past to obfuscate who the real sender of a transaction was. You could "mix" other transactions with yours and so hide the real sender of the transactions in there. The amount of transaction you "mixed" with yours was known as the ring size.
This feature was removed in the tech update, and no more mixing was allowed. Transactions could only have a ring size of 1. However, there were some transactions in the transaction pool from before the fork that have ring sizes of 5. And processing these transactions after the update is what caused problems.
Unfortunately, it seems like only the "checking" part of the new software was coded right, and not the "block creation" part. They were assuming that no transaction in the pool would have a ring size of more than 1, and so it would not be necessary to check for that when putting together a block.
So as a result, blocks were being created with the unallowed transactions in them, but then immediately rejected by the checking part of the same piece of software, and by other miners who were running the new software.
So pools were mining blocks correctly, but they were rejected right away because of the faulty transactions in them.
The solution to this was just to empty (or flash) the transaction pool, and basically delete all transactions currently awaiting processing. This would keep all the ETN in the wallets of the original senders, and they would need to attempt the transaction again. These transactions would have been reversed anyway had we gone on like this since they would have expired after 3 days in the transaction pool
The team has asked several pools to empty their mempools.
Once all the mempools are flushed, and legitimate blocks are being created, it will still take some time to get through the first 75 blocks until the difficulty starts adjusting downwards, but not nearly as much time as it took initially.
The team initially thought that the high difficulty was the big culprit for this, coupled with the low hash rate. They reasoned that we were trying to mine blocks at a high difficulty with low hashing power (since all the ASIC miners are now gone) and that it should take time before the difficulty starts adjusting. Read more about how difficulty works here.
But that was only part of the problem...
The real problem (identified here) was related to a feature that was being removed in the new update, ring signatures, and the implementation thereof. Ring signatures were used in the past to obfuscate who the real sender of a transaction was. You could "mix" other transactions with yours and so hide the real sender of the transactions in there. The amount of transaction you "mixed" with yours was known as the ring size.
This feature was removed in the tech update, and no more mixing was allowed. Transactions could only have a ring size of 1. However, there were some transactions in the transaction pool from before the fork that have ring sizes of 5. And processing these transactions after the update is what caused problems.
Unfortunately, it seems like only the "checking" part of the new software was coded right, and not the "block creation" part. They were assuming that no transaction in the pool would have a ring size of more than 1, and so it would not be necessary to check for that when putting together a block.
So as a result, blocks were being created with the unallowed transactions in them, but then immediately rejected by the checking part of the same piece of software, and by other miners who were running the new software.
So pools were mining blocks correctly, but they were rejected right away because of the faulty transactions in them.
The solution to this was just to empty (or flash) the transaction pool, and basically delete all transactions currently awaiting processing. This would keep all the ETN in the wallets of the original senders, and they would need to attempt the transaction again. These transactions would have been reversed anyway had we gone on like this since they would have expired after 3 days in the transaction pool
The team has asked several pools to empty their mempools.
Once all the mempools are flushed, and legitimate blocks are being created, it will still take some time to get through the first 75 blocks until the difficulty starts adjusting downwards, but not nearly as much time as it took initially.
June 03, 2018, 11:54:24 AM
been mining Monro 9 days this place is broken don't waste your time, im assuming that the bitcoin gold is probably broken and ETN.
June 01, 2018, 04:11:48 PM
Electroneum (ETN) has a patch. Please update and open up pool. Thanks!
https://twitter.com/electroneum/status/1002337417502842881
https://twitter.com/electroneum/status/1002337417502842881
FYI: The patch didn't work, but if you want to mine empty blocks to help get difficulty down while they fix the patch, I'm sure they would appreciate your help! Unfortunately, the difficulty won't go down much until after the first 60 blocks.
June 01, 2018, 06:45:47 AM
I transfered my ZCl to ZEC address. The destination said they dont have my coins. They said that I should check in with you guys.
Is anyway I could get them back?
Is anyway I could get them back?
Your post is a bit confusing! What is each of these addresses, ZCL and ZEC I mean. Which address is from Mining Pool Hub and which is personal and/or from an exchange.
The sender cannot help you, so if you sent from MPH to an exchange, only the exchange can help you. If you sent from MPH to your personal address, then maybe I know how to fix it... I'll have to research it.
Sorry for the confusing. I transfer ZCL from MPH to ZEC address in the exchange. I've asked the exchange but they said their platform doesn't support ZCL, so they suggest that the ZCL would stuck somewhere between and told me to ask MPH. so here I am. Thanks for answering bro.
Jump to: