Topic: Swedish ASIC miner company kncminer.com - page 774. (Read 3050071 times)
I always thought "Network Protection" was a funny way to put it. I would think "Customer Protection" would be more apt.
Forbes article discussing KNC, always good to see the press keep coming..
http://www.forbes.com/sites/kashmirhill/2014/01/03/the-craziest-bitcoin-business-making-money-minting-machines/
Great article - 450 coins and hosted, too. I want to flush my head in the toilet over and over for getting a refund on my oct hosted orders. Ugh! http://www.forbes.com/sites/kashmirhill/2014/01/03/the-craziest-bitcoin-business-making-money-minting-machines/
So, looking back the network protection statement is this:
KnCMiner Network Protection Statement
At KnCMiner we are aware of the service we are providing to our customers. We are also aware that we need our customers to have a return on their devices in order to purchase form us again. With the scale of the supply chains, agreements and factories we have access to, we need to be cautious we don’t ship too many devices and therefore reduce the return to our customers. So with that in mind our plan is to do as follows:
We will ship no devices in December 2013, January 2014 or February 2014. Meaning that once we have taken the difficulty up at the end of November we will not release any more hashing power for 3 months. We will then release our new generation of devices, which will begin shipping in March 2014. These devices will also have a much higher GH/$ rating than any of our current offerings.
We would like to state that If any of our competitors continues to add large amounts of hashing power to the network during December, January or February. We will continue to release our devices as competitively priced as we can to protect our customers share of the network.
Thanks
KnCMiner Team
follow on Twitter | friend on Facebook | forward to a friend
Copyright © 2013 KNCMiner, All rights reserved.
-------------------
I wonder what exactly constitutes "large amounts of hashing power". There's a constant increase - just look at increased difficulty - but one can't point to a large jump indicative of a single large addition.
KnCMiner Network Protection Statement
At KnCMiner we are aware of the service we are providing to our customers. We are also aware that we need our customers to have a return on their devices in order to purchase form us again. With the scale of the supply chains, agreements and factories we have access to, we need to be cautious we don’t ship too many devices and therefore reduce the return to our customers. So with that in mind our plan is to do as follows:
We will ship no devices in December 2013, January 2014 or February 2014. Meaning that once we have taken the difficulty up at the end of November we will not release any more hashing power for 3 months. We will then release our new generation of devices, which will begin shipping in March 2014. These devices will also have a much higher GH/$ rating than any of our current offerings.
We would like to state that If any of our competitors continues to add large amounts of hashing power to the network during December, January or February. We will continue to release our devices as competitively priced as we can to protect our customers share of the network.
Thanks
KnCMiner Team
follow on Twitter | friend on Facebook | forward to a friend
Copyright © 2013 KNCMiner, All rights reserved.
-------------------
I wonder what exactly constitutes "large amounts of hashing power". There's a constant increase - just look at increased difficulty - but one can't point to a large jump indicative of a single large addition.
Forbes article discussing KNC, always good to see the press keep coming..
http://www.forbes.com/sites/kashmirhill/2014/01/03/the-craziest-bitcoin-business-making-money-minting-machines/
http://www.forbes.com/sites/kashmirhill/2014/01/03/the-craziest-bitcoin-business-making-money-minting-machines/
If KNC don't release ready-to-ship Jupiters, people are just going to continue to spend their BTC and cash on Antminers, Cubes, BFL Singles, 55nm Avalons and Bitfury clones.
KNC is doing NOTHING to protect the network hashrate!
They are letting the 2nd tier competition make a fortune instead. I've recently bought some Antminers and Bitfury boards and I would have happily given that money to KNC instead.
RELEASE THE JUPES!
KNC is doing NOTHING to protect the network hashrate!
They are letting the 2nd tier competition make a fortune instead. I've recently bought some Antminers and Bitfury boards and I would have happily given that money to KNC instead.
RELEASE THE JUPES!
I have done the same. 4 ants in my basement with other asorted Asic equipment. I would have happily filled up my M board with more bitfury H-cards but I could not justify the price on the cards. Nothing against MBP but I would rather just let it sit semi populated at that price.
Thanks to all those who replied to my pricing question. Quite an array of opinions. I myself wont believe a low price on a re-release of Jupiters when I see it.
Suggested to have bitcoins on hand - burning a hole in my wallet.... So with nothing new today we wait until the 7th.
If KNC don't release ready-to-ship Jupiters, people are just going to continue to spend their BTC and cash on Antminers, Cubes, BFL Singles, 55nm Avalons and Bitfury clones.
KNC is doing NOTHING to protect the network hashrate!
They are letting the 2nd tier competition make a fortune instead. I've recently bought some Antminers and Bitfury boards and I would have happily given that money to KNC instead.
RELEASE THE JUPES!
KNC is doing NOTHING to protect the network hashrate!
They are letting the 2nd tier competition make a fortune instead. I've recently bought some Antminers and Bitfury boards and I would have happily given that money to KNC instead.
RELEASE THE JUPES!
The only person who confirmed that one is on the way is luke-jr for testing, they didn't even tell him, fedex did. Hashfast promised shipping by the 31st to the bitter end. At this point they hired a lawyer, rewrote all sales terms, sent a letter to customers telling them that if they didn't agree to a USD value refund in the next 15 days they would be agreeing to an indefinite wait for products, and it is fairly obvious they are looking to circle the wagons and prepare for the escape.
Does anyone notice that their miners generally runs better until the first flushwork?
I get around 1% HW errors, and after a flushwork occurs, it shoots up to 3-4%. The HW ticker goes from 1-7 a jump to upwards of 50 a jump.
YES, I noticed that all along... I think the flush-work....still needs work!I get around 1% HW errors, and after a flushwork occurs, it shoots up to 3-4%. The HW ticker goes from 1-7 a jump to upwards of 50 a jump.
****
It seems to "Flush" with every single block detected, and not for just the pool you are on, which causes the errror rate to be higher than it has to be...drastically.
IMHO...that's the biggest tweak needed atm
You are way off on this one...
Flushwork has to run with every block detected on the network. Blocks are built on top of each other network wide, not just on your pool.
I never had that problem mining with GPU's... and it never flushed anything other than our own "Stale" shares.
In pool mining...We don't solve blocks for other pools, we work on our own blocks, and by running flush-work every time a block is detected, you literally loose every workshare you are currently solving, even though your pool hasn't found it's block yet.
My pants are literally loose.
But no, all miners (and pools) are working to add a new block to the end of THE block chain. Pools don't each work on their own separate chain.
Each time a new block is added to the chain, all miners (and pools) stop their current work, and begin new work, trying to extend the now longer chain.
The block trying to be added is unique to the pool, but the chain it is being added to is not.
(There are rare exceptions involving hostile miners, but let's not complicate the discussion with those cases.)
Try this.... look/watch the error rate jump @ flushwork times.
Given the jumps, why would the dumped/flushed shares contribute to errors if the pool didn't want them?
You will also notice the lack of a jump in errors during the flushwork when your pool is finding the block.
I hear what you are saying, but the errors I monitored over the course of mining say otherwise.
I can point my Raedon card at the same pool, on a separate account, and physically see the difference.
IMO there is is still a bug (or more than one bug) in the KnC driver code that handles work changes.
Changing work should never cause a HW error. A HW error indicates that the an ASIC chip returned a nonce claiming that it results in a valid share of difficulty 1 or greater, but the controller then does not reach the same conclusion when it tries to validate that claim, and rules that the ASIC was wrong (a hardware error).
A HW error always indicates a local problem, specifically a disagreement between the hashing engine(s) and the host/controller. A pool should never be able to cause a HW error to be reported.
(BTW, the correct spelling is "lose", not "loose". I'd go mad if I tried to explain this to everyone I see making this error, but you seem like a pragmatic enough fellow that it's probably safe to explain it to you.
)Wizkid057 has created a cgminer that disables work flushes in the cgminer source. https://bitcointalksearch.org/topic/m.4229913
As much as i wish this was true, It wouldn't end up killing BFL. They occupy a hell of a lot of space in terms of marketing, appealing on the broadest of terms. I'd hazard a guess that they're target audience these days is their target audience has always been noobs who don't know any better.
FTFY.
Thanks, haha. As much as i wish this was true, It wouldn't end up killing BFL. They occupy a hell of a lot of space in terms of marketing, appealing on the broadest of terms. I'd hazard a guess that they're target audience these days is their target audience has always been noobs who don't know any better.
FTFY.
While I'm no fan of hashfast, they're supposedly shipping right now. "supposedly".
Of course it could've been 1 single machine to some address somewhere.
Of course it could've been 1 single machine to some address somewhere.
Started on NYE didn't they? Still not seen anyone post a picture of one up and running. Or have they shipped more?
They claim it did, and that several have been shipped out. They posted news on their website yesterday that more have shipped, and released speed claims.
I'm sure if it's legit we'll hear someone post something up. I'm betting to save their butts, they shipped a few to "friends".
While I'm no fan of hashfast, they're supposedly shipping right now. "supposedly".
Of course it could've been 1 single machine to some address somewhere.
Of course it could've been 1 single machine to some address somewhere.
Started on NYE didn't they? Still not seen anyone post a picture of one up and running. Or have they shipped more?
"The largest industrial park in the US is located on Long Island - The Hauppauge Industrial Park which houses 1,300 companies and employs more than 55,000 people."
I'm surprised no bitcoin miner has come out of Hauppauge. Corporate attorneys likely nixed the idea opting not to piss off NY banks.
I'm surprised no bitcoin miner has come out of Hauppauge. Corporate attorneys likely nixed the idea opting not to piss off NY banks.
While I'm no fan of hashfast, they're supposedly shipping right now. "supposedly".
Of course it could've been 1 single machine to some address somewhere.
Of course it could've been 1 single machine to some address somewhere.
Hashfast already failed majorly -
Have you a link to the Hashfast failure or are you going on network hashrate not showing a sharp rise?
Could they have deliberately signaled pending shipment then withheld to see if some darkhorse ASIC producer/facility would come online - that hoping to stay below the radar?
Any news for new jupiter batch from knc ? Thanks.
Yes, it sold out today for under 10 minutes.
Were you just making this up? Or did it actually happen?
He's making it up.
It was under 8 minutes.
Btw the price KNC decided to sell them for today was very good. $2500 was a good call
You paid $2500 each!? I clicked the "I'm an existing KNC customer" checkbox and it dropped the price down to $995 each. Oh well, lesson learned
Again we were having a giggle, there's been no recent further sale of 28nm products!
Does anyone notice that their miners generally runs better until the first flushwork?
I get around 1% HW errors, and after a flushwork occurs, it shoots up to 3-4%. The HW ticker goes from 1-7 a jump to upwards of 50 a jump.
YES, I noticed that all along... I think the flush-work....still needs work!I get around 1% HW errors, and after a flushwork occurs, it shoots up to 3-4%. The HW ticker goes from 1-7 a jump to upwards of 50 a jump.
****
It seems to "Flush" with every single block detected, and not for just the pool you are on, which causes the errror rate to be higher than it has to be...drastically.
IMHO...that's the biggest tweak needed atm
You are way off on this one...
Flushwork has to run with every block detected on the network. Blocks are built on top of each other network wide, not just on your pool.
I never had that problem mining with GPU's... and it never flushed anything other than our own "Stale" shares.
In pool mining...We don't solve blocks for other pools, we work on our own blocks, and by running flush-work every time a block is detected, you literally loose every workshare you are currently solving, even though your pool hasn't found it's block yet.
My pants are literally loose.
But no, all miners (and pools) are working to add a new block to the end of THE block chain. Pools don't each work on their own separate chain.
Each time a new block is added to the chain, all miners (and pools) stop their current work, and begin new work, trying to extend the now longer chain.
The block trying to be added is unique to the pool, but the chain it is being added to is not.
(There are rare exceptions involving hostile miners, but let's not complicate the discussion with those cases.)
Try this.... look/watch the error rate jump @ flushwork times.
Given the jumps, why would the dumped/flushed shares contribute to errors if the pool didn't want them?
You will also notice the lack of a jump in errors during the flushwork when your pool is finding the block.
I hear what you are saying, but the errors I monitored over the course of mining say otherwise.
I can point my Raedon card at the same pool, on a separate account, and physically see the difference.
IMO there is is still a bug (or more than one bug) in the KnC driver code that handles work changes.
Changing work should never cause a HW error. A HW error indicates that the an ASIC chip returned a nonce claiming that it results in a valid share of difficulty 1 or greater, but the controller then does not reach the same conclusion when it tries to validate that claim, and rules that the ASIC was wrong (a hardware error).
A HW error always indicates a local problem, specifically a disagreement between the hashing engine(s) and the host/controller. A pool should never be able to cause a HW error to be reported.
(BTW, the correct spelling is "lose", not "loose". I'd go mad if I tried to explain this to everyone I see making this error, but you seem like a pragmatic enough fellow that it's probably safe to explain it to you.
) Any news for new jupiter batch from knc ? Thanks.
Yes, it sold out today for under 10 minutes.
Were you just making this up? Or did it actually happen?
He's making it up.
It was under 8 minutes.
Btw the price KNC decided to sell them for today was very good. $2500 was a good call
You paid $2500 each!? I clicked the "I'm an existing KNC customer" checkbox and it dropped the price down to $995 each. Oh well, lesson learned
Hashfast already failed majorly -
Have you a link to the Hashfast failure or are you going on network hashrate not showing a sharp rise?
Jump to: