Show Posts
|
Pages: [1]
|
Well In the US you can sue for notting , in sweden this is diffrent , but KNC is going to refunt as I read so I guess they are not so bad at all. oh btw if you dont accept the refund well then you are on your own. as long KNC miners are not FCC or CE , certified you have NO CASE if it explodes in your face!Does being this stupid come naturally or do you have to work at it? @s1gs3gv I'm waiting for the prelim hearings where we go before the judge and outline our case. Should be May/June. I'm not in the class action, I have my own case but the class action has slowed everything down. The Judge wants to hear all the KNC cases together to speed up the process. So unfortunately the head start I had has been nullified. @notlist3d Give Joakim or Magnus a bell. Someone posted a few pages back they were offering to work on a percentage with no up front costs on the class action. I've already paid so I haven't got the details but it might be worth dropping them a line. Based on the consistency in his postings, I think it's a natural ability.
|
|
|
How connect Titan at nicehash pool Any details???
Here's a config with Westhash as primary and Nicehash as fail-over: { "pools": [ { "url": "stratum+tcp://stratum.westhash.com:3333/#xnsub#skipcbcheck", "user": "<ADDRESS HERE>", "pass": "<PASSWORD HERE>,d=16384" }, { "url": "stratum+tcp://stratum.nicehash.com:3333/#xnsub#skipcbcheck", "user": "<ADDRESS HERE>", "pass": "<PASSWORD HERE>,d=16384" } ], "failover-only": true, "scrypt-n": 10 }
|
|
|
Wrong info from me about the mining software. The Titan uses bfgminer v 5.0.0 so extranonce isn't an issue.
You will have to set #xnsub and #skipcbcheck manually, i.e., your pool url will be stratum+tcp://stratum.nicehash.com:3333/#xnsub#skipcbcheck . Based on what the Westhash site recommends for difficulty I used 32768 which is the recommendation for a hashrate of 64MHs - 128MHs, although I'm over that at app 330-350 MH/s, but the 64 - 128 MH/s is the highest range on their chart.
Try to set the difficulty to 16384 - d=16384 . You can set the difficulty you like, you don't want to put the difficulty they recommended. If this is also not working, don't set any difficulty, just mine without difficulty parameter(d=X). After 6 hours with that difficulty my hashrate is way lower than I get elsewhere (327 vs 340+ at clevermining) and rejects is at 6.8, so that difficulty isn't the answer.
I keep hearing (actually only from Nicehash/Westhash people) that the Titan works on Nicehash/Westhash and gets 350 MH/s with low rejects, etc but every time I try it I get lower hashrate and high rejects. I'll probably head back to clevermining - where my return might be very slightly less - but I can set the miner and forget it and get a high hashrate and low rejects.
Please do what I say and check whether it is okay! -MZ Thanks for the additional feedback. I've been using the #xnsub and #skipbccheck all along based on a posting/recommendation on the KNCMiner forum on 1/10/15 which said the following: We suggest you to use #xnsub AND #skipcbcheck parameters to get stable mining on NiceHash or WestHash, example:
stratum+tcp://stratum.nicehash.com/#xnsub#skipcbcheck
With those settings you'll be able to get a stable 350 Mh/s average speed with fw 1.95 overclocking at 325MHs.** And the poster posted this screenshot https://www.nicehash.com/imgs/KnC_Titan_NiceHash.png as "proof" but to me that looks like 320 MH/s over 1253 hours, not 350 and what looks like 0.00% rejects . Based on the screenshot, about an hour ago I tried 16384 and I'm currently at an effective hashrate of 327 MH/s with a reject rate of 6.5% so I still apparently haven't located the secret decoder combination of settings which will get me mining at app 340-350 with a reject rate of around 1-2%. After 20 hours with diff set to 8192, I had an effective rate of 326 MH/s and 7.1% rejects. So apparently the Titan still doesn't work very well at westhash/nicehash. Back to clevermining
|
|
|
Did you ping the websites nicehash and westhash? Which is closer to you? Use the closer one and try again. Try decreasing the difficulty again or with no difficulty parameter.
-MZ
I'm on the west coast of the US so I assume westhash is closer and that's my primary with nicehash as a failover. The ping times are quite similar though. I set difficulty to 8192 and I'm going to let that run until I check it later tomorrow. I already tried with no diff and that produced 330 MH/s effective hashrate and 5.2% reject rate after 24 hours. That might be the best I get if I stayed at westhash.
|
|
|
Wrong info from me about the mining software. The Titan uses bfgminer v 5.0.0 so extranonce isn't an issue.
You will have to set #xnsub and #skipcbcheck manually, i.e., your pool url will be stratum+tcp://stratum.nicehash.com:3333/#xnsub#skipcbcheck . Based on what the Westhash site recommends for difficulty I used 32768 which is the recommendation for a hashrate of 64MHs - 128MHs, although I'm over that at app 330-350 MH/s, but the 64 - 128 MH/s is the highest range on their chart.
Try to set the difficulty to 16384 - d=16384 . You can set the difficulty you like, you don't want to put the difficulty they recommended. If this is also not working, don't set any difficulty, just mine without difficulty parameter(d=X). After 6 hours with that difficulty my hashrate is way lower than I get elsewhere (327 vs 340+ at clevermining) and rejects is at 6.8, so that difficulty isn't the answer.
I keep hearing (actually only from Nicehash/Westhash people) that the Titan works on Nicehash/Westhash and gets 350 MH/s with low rejects, etc but every time I try it I get lower hashrate and high rejects. I'll probably head back to clevermining - where my return might be very slightly less - but I can set the miner and forget it and get a high hashrate and low rejects.
Please do what I say and check whether it is okay! -MZ Thanks for the additional feedback. I've been using the #xnsub and #skipbccheck all along based on a posting/recommendation on the KNCMiner forum on 1/10/15 which said the following: We suggest you to use #xnsub AND #skipcbcheck parameters to get stable mining on NiceHash or WestHash, example:
stratum+tcp://stratum.nicehash.com/#xnsub#skipcbcheck
With those settings you'll be able to get a stable 350 Mh/s average speed with fw 1.95 overclocking at 325MHs.** And the poster posted this screenshot https://www.nicehash.com/imgs/KnC_Titan_NiceHash.png as "proof" but to me that looks like 320 MH/s over 1253 hours, not 350 and what looks like 0.00% rejects . Based on the screenshot, about an hour ago I tried 16384 and I'm currently at an effective hashrate of 327 MH/s with a reject rate of 6.5% so I still apparently haven't located the secret decoder combination of settings which will get me mining at app 340-350 with a reject rate of around 1-2%.
|
|
|
Is anyone mining Westhash with a KncMiner Titan? I tried Westhash for about 24 hours and the hashrate was ok at app 330 MH/s but cgminer was showing 5.2% reject rate. Any way to get the reject rate down?
Thanks,
Try to use extranonce subscription and also try to set a custom difficulty(neither high nor lower). See https://www.nicehash.com/index.jsp?p=faq#faqs9 for difficulty table. P.S. Have you tried BFGMiner? -MZ Wrong info from me about the mining software. The Titan uses bfgminer v 5.0.0 so extranonce isn't an issue. Based on what the Westhash site recommends for difficulty I used 32768 which is the recommendation for a hashrate of 64MHs - 128MHs, although I'm over that at app 330-350 MH/s, but the 64 - 128 MH/s is the highest range on their chart. After 6 hours with that difficulty my hashrate is way lower than I get elsewhere (327 vs 340+ at clevermining) and rejects is at 6.8, so that difficulty isn't the answer. I keep hearing (actually only from Nicehash/Westhash people) that the Titan works on Nicehash/Westhash and gets 350 MH/s with low rejects, etc but every time I try it I get lower hashrate and high rejects. I'll probably head back to clevermining - where my return might be very slightly less - but I can set the miner and forget it and get a high hashrate and low rejects.
|
|
|
Is anyone mining Westhash with a KncMiner Titan? I tried Westhash for about 24 hours and the hashrate was ok at app 330 MH/s but cgminer was showing 5.2% reject rate. Any way to get the reject rate down?
Thanks,
|
|
|
On a non-guldencoin related question:
How come my 24 hour payout amount seldom - if ever - matches the BTC/day per MH/s multiplied by my avg hash rate per that 24 hours.
If, for some illogical reason, BTC/day per MH/s multiplied by my avg hash rate per that 24 hours is not what I should be getting paid, what is the secret formula?
Are you looking at the coins received in your wallet? This might not match due to immature/unexchanged/unpaid balance remaining at CM. If you include those it should match quite closely. Yes, I'm looking at coins received because that's what matters. Every day - with a very, very few exceptions, the BTC/day per MH/s multiplied by my avg hash rate per that 24 hours is more (usually by a good amount) than the btc I receive. The next day is the same thing. It's not like I ever receive an out-of-band catch up payment and the "immature/unexchanged/unpaid balance remaining at CM" every day appears to remain at CM forever. Am I missing something besides a good amount of btc? Also, is there some way to directly contact CM support/this person Terk, or is this thread the only means of support? Thanks Send a PM to Terk, that's then only way that I know of. Maybe a tweet would work too, not sure. Are you looking at the 24 hour hashrate and the BTC/day rate at the same time when you are receiving your payment? Timing matters too. If you could show some numbers I could maybe help more. I have followed CM payouts for nearly a year and it has always been close to the displayed rate, so I'm genuinely curious why you would be seeing a difference. What I'm doing is looking at the hashrate chart/graph for my miner. For each date there is a graph point that displays my 24 hr avg hashrate. I multiply that figure by the "BTC per 1 MH/s" obtained from the "Daily Details" chart for the same date. Thanks for your help. Maybe, I'll try pm'img the mysterious/reclusive Terk or most likely I won't and will just accept what might be another passive/agressive rip-off by the altcoin industry. Plus, isn't there some requirement I have to meet in order to pm from this forum? Just an observation (and this is in no way directed toward you; you provided much appreciated assistance and feedback) but based on my experience, the customer support/service in the altcoin industry is the worst of any industry with which I have ever been involved. I ordered a Titan from KncMiner and that experience was absolutely legendary in it's terribleness; it was so terrible it was awe-inspiring and beautiful in its own way. To get in contact with somebody from Clevermining - whom I believe I am generating capital for when I mine there - is some mysterious, undocumented process which apparently requires pm'ing from this forum. Their website definitely isn't showing any Contact Us type of information and "Terk" isn't exactly a presence on this forum from what I can see.
|
|
|
A few days ago the European Cleverming server is giving me problems with repeated disconnections. In the end I changed the server USA and go without fault except a somewhat higher percentage of rejected, normal to have to go further to receive their shares. Am I just pass me or is it generally a problem with the European servers?. My Titan is in Valencia Spain.
Regards
I was having a disconnection issue with the US server from about 12/21 - about 12/28. I'd wake up or come home from work to a not mining miner (Titan) showing a "Pool 1: Unknown stratum msg ..." type of error. I have a back up pool configured but failover didn't work. It got so bad with so much downtime, I went over to litecoinpool.org for about a week. Since moving back to clevermining the issue hasn't recurred.
|
|
|
On a non-guldencoin related question:
How come my 24 hour payout amount seldom - if ever - matches the BTC/day per MH/s multiplied by my avg hash rate per that 24 hours.
If, for some illogical reason, BTC/day per MH/s multiplied by my avg hash rate per that 24 hours is not what I should be getting paid, what is the secret formula?
Are you looking at the coins received in your wallet? This might not match due to immature/unexchanged/unpaid balance remaining at CM. If you include those it should match quite closely. Yes, I'm looking at coins received because that's what matters. Every day - with a very, very few exceptions, the BTC/day per MH/s multiplied by my avg hash rate per that 24 hours is more (usually by a good amount) than the btc I receive. The next day is the same thing. It's not like I ever receive an out-of-band catch up payment and the "immature/unexchanged/unpaid balance remaining at CM" every day appears to remain at CM forever. Am I missing something besides a good amount of btc? Also, is there some way to directly contact CM support/this person Terk, or is this thread the only means of support? Thanks
|
|
|
On a non-guldencoin related question:
How come my 24 hour payout amount seldom - if ever - matches the BTC/day per MH/s multiplied by my avg hash rate per that 24 hours.
If, for some illogical reason, BTC/day per MH/s multiplied by my avg hash rate per that 24 hours is not what I should be getting paid, what is the secret formula?
|
|
|
|