Middlecoin has recently been switching coins a lot faster than instant profitability would dictate. I have some miners there and did see diffs indicating CAT for a few minutes this morning, but it seems to bouncing between LTC, WDC, and FTC.

Based on the coin switch speed either the switching algo has a bug or the pool operator is intentionally trying to spread that 10 GH/s around to avoid breaking smaller coins (using coin switching as a kind of pulse-width modulator).

This is the fundamental problem that the fork didn't fix: until there is enough constant hash to make the effect minimal, multipools are going to cause huge difficulty swings by jumping in when the difficulty is low, mining out all the blocks, pushing the diff up, and jumping out. We only have to mine 36 blocks now to get through the high diff, but we don't get many of the easy ones for all that work.

Until the net hashrate is too big for a multipool to significantly effect (which means 20+ GH/s), the difficulty NEEDS to depend on more than just the last 36 blocks. The 36 block retarget is great, but the new difficulty should be calculated from the last 2016 block times so that fast 4x diff swings dont happen.

The diff briefly dropped to 24, maybe he got luck on those blocks.

LTC would show in cgminer with a diff of 3.37K or 221M, depending which version you have. I don't see that diff now, we seem to be switching between DOGE and CAT (17.3M and 6.45M).

He says a lot of things.

Your mining on the US server results in unexchanged balance, which is paid out later. The EU server is immediately autotraded.

Check what the sum of immature, unexchanged, and balance add up to for each period.

Not to speak for h2o (I'd like to hear his thoughts on this) but this isn't quite that simple. There are a lot of steps to this process.

We (as miners) send hashpower to the server. We have no way to collectively see how many shares are valid blocks on the coin being mined, and we dont even know the coin being mined (even if h2o compiled and published data per share and per it would be extremely simple to fake).

Next, blocks go from the server wallets to exchanges. Again, this data could be published, but easily faked. We have no idea where h2o is trading coin (and I'm not sure I want to know), and what exchange rates are for the coins. Then, BTC are sent from exchanges (probably through middlecoin wallets) to users. The fee probably comes out here.

I'm all for transparency, and it would be nice to know a bit more about the inner workings here. However PROVING that the shares sent in should result in a certain amount of BTC out would be extraordinarily difficult, and would certainly expose everything about the process (which would consequently destroy much of the advantage middlecoin has over competitive pools).

The client stores the wallet.dat file in the C:\Users/username/AppData/Roaming/CatCoin folder; if you didn't delete that folder, the new client would have looked there by default and found the old wallet.dat file.

I would recommend doing that. I have seen less than a minute of downtime on the US server in the last 5 hours... only 2 disconnects and both resumed in seconds.

Backup your wallet, and download and install the latest .qt from the original post on the this thread.

The new wallet just needs to point to the same wallet.dat file that the old one had. Backup the wallet.dat, uninstall
 Catcoin, download and install the new wallet, restore the wallet.dat, and you are good to go.

I am using 3.1.1 and have not had to recompile to fix the disconnect/drop issue. I don't know if there is any advantage with the newer versions, especially on middlecoin - can anyone comment on this?

Also, the switch/disconnect frequency seem to had dropped way off, looks like the fix has rolled out.

The Windows wallet in the OP is working great for me. Do a clean install of that and you will be on the right chain.

cat.poolerino.com has been fixed: 0.16 GH/s

All the forked blocks were orphaned.

Net hashrate is estimated from block time, which has not been very consistent.

Shouldn't that automatically update?

Coinium and poolerino are synced on block 20365 now, but coinium still saying 1811 until next diff change.

Why does coinium have the next difficulty change in 1813 blocks? That should have changed with the original fork.

Maybe there are 3 or 4 forks

No, the shortest chain wins.

Simple explanation: lag. If it's not that, then there are multiple forks, which is not good.