Posts Tagged ‘KnCMiner Titan ASIC’

KnCMiner with New Titan Scrypt ASIC Updates

24, Oct 2014

kncminer-titan-scrypt-asic-miner

KnCMiner continues to get a more and more unhappy customers due to the continuing issues with the Titan Scrypt ASIC miners and the way the company seems to be treating their customers. Lately KNC has announced that they do plan to move from selling mining hardware to end users to making mining hardware for their own data center and to mine crypto currencies themselves. They have stopped accepting new orders from customers a while ago, their announced KNC Cloud mining plans were most likely just a PR move as the company most likely does not want to sell cloud mining hashrate to customers, though they apparently do still have the offer “available” for on their website.

Back to the company’s Titan Scrypt ASIC miners, it seems that the shipping of units is still going very slow and we are already past the promised Q3 delivery for Batch 1 units. The people that were lucky enough to get their units already report a lot of issues and problems, both with the software and the hardware and apparently KNC is slow to respond to issues and it still refuses to offer refunds. Today KnCMiner has released a new firmware for the Titan miners that supposedly should improve stability and hashrate, and apparently it does help to increase hashrate. The latest update comes with the news that they “expect to deliver the remainder of batch 1 of the most efficient hardware miner on the market over the next three weeks to our customers”. Will this mean less unhappy customers, probably no, as there are people that are still expecting KNC to deliver on their promises made even before the drama with the Titan evens tarted.

KnCMiner Responding With Some Tips for Titan Owners Reporting Issues

9, Oct 2014

kncminer-titan-scrypt-asic-miner

Today the guys at KnCMiner have released some tips for users that have received or are about to get their Titan Scrypt ASIC miners regarding how to maximize the hashrate and meet the announced 300 MHS expectations that users are having. According to KNC the use of crypto coins with very fast blocktimes on multi-pools are not recommended for maximum hashrate and they do recommend users to go for the following pools that should not have issues with the high hashrate that the Titan miners have:

WeMineLTC (stable above 300MH/s, this pool also merge-mines DOGE).
LiteGuardian (best performance so far but LTC only (no merged DOGE mining)) 300MH/s+
GHash (300MH/s+ on both LTC and Multi-pool)

KNCMiner have also announced that they are working with some other pools in order to improve performance with the Titan miners where currently users are having trouble getting at 300 MHS. These pools include Coinotron, where they are apparently getting around 260-270MH/s so far as well as CleverMining and apparently others that were not cited in the latest news release coming from the company.


The settings KNC recommends to be used on the mentioned above pools:

WeMineLTC: Use the regular stratum and leave the worker settings at default; stratum+tcp://power.wemineltc.com:3333
LiteGuardian: Use the ASIC-ready URL: stratum+tcp://asic1.liteguardian.com:3335
Ghash: Set the difficuly to 8192 at the pool, you can find this under worker settings. You can use the LTC/DOGE or Multipool URLs: stratum+tcp://ltc.ghash.io:3333 or stratum+tcp://multi.ghash.io:3333

This however is not enough to cover for the many more problems that users who have already reported after receiving their Titan miners as the lower than advertised hashrate is just one of the issues that is often experienced. It also does not cover the fact that KnCMiner is already late in shipping all of their Titan Batch 1 miners to users, something that was supposed to happen before the end of Q3 and we are already Q4 with a lot of people still waiting for their mining hardware. With the KNC policy of not offering refunds to customers, their products having a lot of issues, the company delaying shipments and so on it seems that a lot of people are already considering taking legal action against KnCMiner…


top