76% invalid... I think something is wrong with the pool... that can't be normal can it?
Just seems to be Zcash; Zclassic doesn't report high invalid.
There are no errors on the NiceHash screen; actually has a positive delta! So confused.
Pool reports back "Succeeded" message most of the time for submitting ZEC/ZCL shares due to old miner bugs (Genoil miner and some of them disconnects when they send stale shares) Website shows actual invalid numbers. I think it's time to fix this workaround and get things correct. Thanks, ye, I'm certainly not getting that high invalid shares otherwise I wouldn't be getting so much Zcash. I've noticed an issue with the 'On Exchange' value. 'Debited' transactions appear on Zcash pool but the related 'Credit' transactions don't appear on the Bitcoin pool for ages. Currently there is a 'Debit_AE' (611292) for 5 ZEC but no 'Credit' for BTC; the issue is that the 'On Exchange' does not include the 5 ZEC. I don't have a very good understanding of it but there just seems to be a black hole now and then. I checked that transaction and found that Zcash debit has already credited to your account with 0.53483242 BTC. Bitcoin auto payout was already done also. I think you didn't notice auto payout and thought it did not credited at all. Or maybe... it's not that like to happen.. but.. there's some time gap between "end of auto exchange" and "credit" in miningpoolhub. It took about 7 minutes last time. Maybe you checked at that time period? If you checked it between 11-26 21:01:37 (UTC) ~ 11-26 21:08:45 (UTC), you would have seen disharmony values that there's no On Exchange at Zcash row and 0 Bitcoin. I would fix this timing gap soon anyway. Also Balances page doesn't reflect realtime values. It is cache backed data, updated regularly. I will improve this too as well. Cheers, it's working great; looking forward to the improvements. When you're suddenly 5 zec down you're like, oh ****, what have I done!  |
|
|
|
76% invalid... I think something is wrong with the pool... that can't be normal can it?
Just seems to be Zcash; Zclassic doesn't report high invalid.
There are no errors on the NiceHash screen; actually has a positive delta! So confused.
Pool reports back "Succeeded" message most of the time for submitting ZEC/ZCL shares due to old miner bugs (Genoil miner and some of them disconnects when they send stale shares) Website shows actual invalid numbers. I think it's time to fix this workaround and get things correct. Thanks, ye, I'm certainly not getting that high invalid shares otherwise I wouldn't be getting so much Zcash. I've noticed an issue with the 'On Exchange' value. 'Debited' transactions appear on Zcash pool but the related 'Credit' transactions don't appear on the Bitcoin pool for ages. Currently there is a 'Debit_AE' (611292) for 5 ZEC but no 'Credit' for BTC; the issue is that the 'On Exchange' does not include the 5 ZEC. I don't have a very good understanding of it but there just seems to be a black hole now and then. |
|
|
|
whats wrong with this bat
eu1-zcash.flypool.org:3333 -zwal taddress.rig2b -zpsw x -benchmark 1 -tt 90 -fanmin 50
getting average hash 500+ showing in console and nothing at flypool for over 2 hours?
Are fly pools stats down right now?
LOL, u set benchmark mode |
|
|
|
You can already do this by mining at an auto-switching pool using Claymore. What would be useful is for Claymore to auto-switch POOLS based on profit, he can dream big and combine all his miners controlled by a separate program that looks at the pool API's and starts the appropriate miner.
Can you imagine hundreds of thousands of miners hitting that API? How do you think the nicehash miner works? Nicehash isn't a free service. They are paying for bandwidth/resources by the fees. A public API is going to have costs / overheads. Claymore wouldn't need an API; the switching would be done locally and you access the APIs from the pools. A local controller app would launch the miner(s) and connect to them via the 'mport' to tell it what pool to use. If all the miners had a benchmark feature as well, it could determine the speed for each algo to base the profit calculations off. This is all that Nicehash do but they lock it to only their pool's API. |
|
|
|
76% invalid... I think something is wrong with the pool... that can't be normal can it? Just seems to be Zcash; Zclassic doesn't report high invalid. There are no errors on the NiceHash screen; actually has a positive delta! So confused.  img upload |
|
|
|
How do you completely turn off this MSI light
is that to remove the light and unplug it Just take those little screws out. Must be a wire behind it. |
|
|
|
Does anyone know which is stable downvolt for SAPPHIRE RX480 NITRO OC + for 1342 MHZ GPU and 2000 MHZ for memory?
1350 MHZ 1130mv core 2200 MHZ 1100mv mem |
|
|
|
v7 uses too much CPU compard to ie v6 - imo that should be fixed in 7.1
Lower the intensity setting. Default is 4 but 0 uses no CPU: "-i 0" |
|
|
|
And dual mining zec/zcl?
That would be pointless; no benefit at all. You do realise that you can mine both? Why would you want to do it at the same time? This will mine either ZEC or ZCL depending on what is most profitable: europe.ethash-hub.miningpoolhub.com:17023 |
|
|
|
last night i use claymore V7 and look what happens in my Main board !!!!!
why this thing are happen?
all earlier versions was good and no problem with them,but last night after changing the claymore version to V7,this is happend
Maybe your setup sucked from the start? how much experience do you have setting up these rigs? what hardware are you using all together? Maybe it's easier to pinpoint your error than putting the blame on a dev? thousands of users are running this. thanks! maybe your right , but all version about 1 month is working good.when im changing my claymore to V7 this is happen . CPU G630 4X RX480 RADEON 8GB 4GB RAM MAIN biostar h61b PS : 1350 Wat This is nothing to do with software. Running software does not blow up your computer! Bad hardware pushed to it's limits is why computers blow up. Please don't post irrelevant topics in this thread; start your own. |
|
|
|
any chance you will begin to work on nvidia and cuda? amd is reaching is limit already i don't think it's possible to do high improvement anymore
on the other hand a 1070 is stuggling to have 125 sol and it should be 160 at the very least, and i think it might be higher, up to 180...
I still can improve speed, though it requires more and more efforts and time. It seems about 300H/s on stock 390X is possible. So it's not over for AMD yet and therefore I don't have time for NVidia. You hate Nvidia ? . He's one man, there are other miners you know. |
|
|
|
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! |
|
|
|
Getting 166 sol/s out of a rx470 8gb nitro
How in the world are you doing that?  ?? Who cares not to be rude but what is the watts per H? I do 2.2 k h across 18 cards using 5 mobos . Rx 470 or rx 480. No bios bs. I set msi after burner 4.3 My watts are 7.9 amps x 240 volts = 1896 watts say 1900 So 1900/2200= .863 watts per H/s My best rig does .799 watts per H/s Yes, that is true more is better, but not at the cost of efficiency......W/Hs would be the better question! Claymore command: "-cclock 1350 -mclock 2200 -cvddc 1140 -mvddc 1100 -powlim 0 -tt 80" 100% stable, core speed stays constant 1350 (doesn't dip); same clock settings can even be used for gaming. |
|
|
|
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). {
"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 |
|
|
|
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! |
|
|
|
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 hostingIdle orders are just endless drops:  free image hostingIt works but with it dead 50% of the time, it's pot luck:  image sharing sitesPlease fix soon! Thanks! |
|
|
|
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 |
|
|
|
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. |
|
|
|
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 Hey, any update? All 40 orders are down... |
|
|
|
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 |
|
|
|
|
Show Posts
