1.0 firmware should be coming very soon: https://github.com/KnCMiner/meta-kncminer/commit/816fe79a23eef44143b9dbdc9cbe8b84973b11c3

Good news: you may now set a manually difficulty setting by using d= as your password.
For example:

We do mine 100% LTC if our hashrate high enough and the other coins drop below 100%. However, even if we're mining another coin that is ~102% vs LTC, due to luck and spacing between blocks we may fluctuate between 97% or 106%, for example.

The more significant drop we saw today was due to Cryptsy's API being down ALL NIGHT. With their API down we have trouble estimating which coins are the most profitable to mine and we ended up not spending our hashrate as efficiently as we would have otherwise.

Honestly I spend about 20% of my time dealing with/working around Cryptsy's problems. Their wallets go down, stop accepting deposits, APIs go in and out and return stale data, etc. Last night I got pretty pissed and called them out publicly on their shit:
https://twitter.com/CoinShift/with_replies

But I doubt that'll help much -- and it's not like we can switch exchanges easily, the other ones just don't have enough volume.

Anyone else get a shipping notice besides @Elenelen?

Why oh why does today have to be a holiday in Sweden!

We added three fresh coins a few hours ago. Our internal BTC/6h graph is showing over 125% -- should see the 24h graph rising to meet this over the next few hours

Thanks for the feedback, we weren't aware of those HW issue problems. We will add a manual difficulty setting this weekend.

Cheers!

Glad you noticed!

Yes, we've switched to a nicer charting system that is a bit more detailed and shows you more information when you hover on the graphs. It's still a little rough around the edges but it's definitely an improvement.

We also split out a graph for each of your workers now, which was a highly requested feature. Sorry that took so long!

@jgauthier I will get you an API for that today

I want to try to avoid announcing any announcements, so let me just say this: Yes, we're working on supporting other algos. In the mean time, we're mining at 163% which ain't half bad!

We've added Silkcoin to Coinshift -- mining at >120% LTC profitability.

Great work, guys.

Minimum daily payout amount is 0.001 -- what is your current balance?

Today we added Fluttercoin and Whitecoin.

We can add one or two more today. Asiacoin would be hard since it's not traded on Cryptsy, but we'll run the numbers and see if it would be worth it.

Anyone know what which "secret" coin Wafflepool is mining with random rewards in the 250,000-300,000 range? Will add it ASAP.

Adding two more coins tomorrow, let us know if you have suggestions!

Keep in mind that they must be traded on an exchange with a trade API and have a fair amount of volume in BTC.

Hi Clocker -- your remaining balance has been sent, thanks for mining with us.

Thanks for relaying that. It was a huge bummer -- fortunately AUR has hit their hard-fork which halves the block time (and maturity time) in addition to adding a better difficulty adjustment algorithm. Hopefully we'll see that coin get much healthier over the next couple of weeks and we can re-enable it.

It was rolled in to your normal one -- if you mined some of the AUR you should have seen a sharp jump in your balance.
LTC is in the rotation, but only if we hit a certain hashrate threshold. The problem we have with LTC is that our hashrate isn't quite high enough to mine it without luck being a significant factor. We had a period of bad luck while mining LTC that dropped our BTC/MH below the LTC line, which drops our hashrate even more and the problem compounds! However, things have definitely stabilized recently and our hashrate is doing pretty well.

Everything looks OK to me -- perhaps when you checked the site you were on the lower end of the variance. When I checked your hashrate was reported as >2900Kh: http://cl.ly/Uh37

The site currently reports the hashrate as calculated over the last 20 minutes. There is going to be some variance there, which is why you see the graph oscillate between 2300 and 3000. Maybe we need to increase that so it gives you a better picture of your actual hashrate. The problem there is that we don't want it to take a long time for new users to see their hashrate ramp up. There is definitely a way to make it work for both, so we'll work on it.

To double check I calculated your hashrate over the last hour:

We're at .00498 right now which is good considering we're above Wafflepool and CleverMining (as of this very moment). I expect we'll get a bit above .005 today.

The AUR is finally mature so it will exchange today.

Yep, fair enough. We've been very disappointed with the performance over the last day. We trimmed out some poor performing coins last night and things are much better today. We'll keep you posted.

What's your address? I'll take a look. If you could post a screenshot of your rig hashrate that would be helpful too.

That's a common question. Since finding a block is an independent random chance, you shouldn't slice up the hashrate and try to look at pieces independently across small time periods (in this case, the instantaneous DOGE hashrate). Statistically there is no benefit to maintaining some "minimum" instantaneous hashrate on a single coin.

We do manage the pool's "hashrate efficiency", but it matters only in aggregate across all the coins we're mining and across a longer time period. In other words, you should look at the weighted average of the coin difficulties, not any one coin. For example, imagine we had 2000 altcoins, all with the same difficulty as DOGE. We then allocate 0.05% to each. If you look at an individual coin you would think the probability of finding a block would be quite low. However, in aggregate, we'll actually find blocks quite often -- this is because the risk/reward ratio for each unit of hashrate is profitable.

Another way to think about it is thinking of it over a longer timescale. Instantaneously at some points it was .73% DOGE and others it was 80% DOGE, but over the course of the day it averaged out to 700MH/sec.