Took a while, but a complete re-sync fixed it. Now on block 60362

Hrm, possibly not perfect. I'm getting these error messages again:

"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

My Wallet is also only Syncing up to block 60256 out of 60295

I can try deleting my chain and re-syncing

Got it, Thanks. Perfect!

Has the Windows Binary been (re)moved?

I'm getting a 404 Not Found error when I try to open http://cganomaly.com/downloads/CGA_1.3.0.1_WIN.exe

I think Cipherpool (http://kit.cipherpool.com) may be mining on a fork. They still have unconfirmed blocks from the 15th!

I can see 2 workers on there pushing 3.5MH; so that's a lot of wasted Hash.

I suspect that's because Cryptsy and Coinedup have been our primary two exchanges so far.

I've done a little trading on Poloniex with Kitteh, but the majority has been on those two. Anyone else in the same boat?

You've sort of hit the nail on the head there. ALL of the Altcoins are down at the moment due to repercussions from the MtGox collapse. This isn't a specific Kitteh thing. There's a lot of investors that have been spooked and are now moving from Altcoins --> Bitcoin --> Fiat. This is causing a lot of dumping as people rush to get out of Cryptos.

Stop focusing on price for the moment; Bitcoin and, by association, Altcoins will recover it's just going to take a while. There's too much big money invested in Bitcoin mining hardware and GPUs for Bitcoin to become completely worthless.

So take a deep breath, buy up the coins while they're cheap and lets see if we can build a stronger community around the coin.

Suggestions include using the Kitteh Tipbot on Reddit and what's a Memecoin like Kitteh without Funny Cat Photo's? It's been 7 pages since the last Meme picture! Half the reason Dogecoin is popular is their community and the sheer number of meme pictures they produce. Funny Cat photos practically started the 'Meme' genre, so why aren't we exploiting that more?

I don't know how many will agree with me, but I'd like to request a 'cuter' Maneki Neko logo for the coin to support this

my apologies, to clarify, I was suggesting that you 'snapshot' the net hash rate at the point of the block hash creation, not a continuously changing value. I.e. you wouldn't know what the block hash would be prior to the creation. this would obfuscate the value of the block until it was announced prior to mining.

I have no idea if this would work, but how about this?

Rather than the anomaly being created based on 1/Difficulty, how about the reward being determined by 1/Network hash rate at declaration of block reward?

You could then trigger the reward based on another factor, such as the last digit being odd, even, the number '3', etc.

The network hash fluctuates rapidly, unlike difficulty. The reward would still be announced at the start of the block, but as it could not be so easily predicted, the Multi-pools would not have as much time to 'swoop in' and steal the block. Similarly, as you can't accurately control the total net Hash rate, you couldn't force it to generate an Anomaly every time.

-T

Voted

Hendo mentioned he was preparing to move on page 174;and he was going to be offline for stretches over the next two weeks. So silence on his part is expected.

It would still be good to see a little more activity on this thread, and possibly an update on the KGW implementation progress.

An exchange would be mad to touch us while we're forking so regularly.

If an Exchange were to fork unexpectedly while trades were occurring it would be disastrous. It would destroy the coin's reputation.

I'm not about to take a poll, but I suspect the general consensus is to avoid an exchange until these issues are resolved.

Either way this is the Dev's call to make

The forking issues need to be resolved before the coin can be traded reliably on an Exchange. So holding off is a good thing. 42 Coin was crippled by being listed too early on an Exchange; so yes we need transactions and volume, but we also need Stability.

CGA won't be worth anything if transactions can't be processed, or if an Exchange itself ends up on a fork.

The issue is more to do with your ulterior motives, rather than your stated 'good intentions'.

You have a considerably larger stake in this coin than I do and probably many others; yet you publicly destroy the reputation of the coin and those associated with it; rather than dealing with it in private and with a little more dignity.

By airing your 'Dirty Laundry' very publicly, you've only succeeded in damaging the coin for everyone. Ok, fine, you might have warned us all off of the 42Dice site, but considering how obvious your motives are, how can we trust you? The result is that we trust neither party and the coin's reputation tarnished.

So how cheap do you want to get your '42' before you let us raise its value out of the gutter; so you can make a massive profit?

That's not a very 'Hippie' thing to do.

I haven't forked this time either, but these three are not in my config file and I can't delete them using 'addnode remove'

I'm not sure how we get rid of them 

@S4w3d0ff Sorry for not replying last time; it was after Midnight so I'd gone to bed when you replied. I removed some nodes from my Config file and redownloaded the blockchain; which resolved my problem.

My Wallet is currently at block 11131 and I'm currently mining solo.

From 'getpeerinfo' I can see that these nodes are still running the wrong version:

58.6.247.70
50.147.39.37
76.126.49.244

I suspect they're the current causes of the fork. If anyone has these in their config files, I suggest removing them. Do we have any idea who the owners are?

Nope, the error has returned. I'm not sure why I'm so many blocks behind you

Edit, just jumped to 6093, but still displaying the error

Ok, I have the four nodes from the first post. I've just deleted and redownloaded the blockchain and I'm showing Block 6086.

If I do a 'getmininginfo' I'm no longer receiving the error

I'm showing 6081. I just deleted and redownloaded my blockchain; as I'm getting an error:

"Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."