You are correct, no more old C2.  All 2.0 now! So if you have not deposited and still in old wallet. They are now worthless.

OLD C2 deposit is disabled and we are switching to NEW C2(Coin2.0). 旧的C2充值已经截止，我们即将为用户兑换为新版本C2(Coin2.0)。

Well, you should have seen it then. We have been moving them over the last two days. its over now. sorry bro!

I second that. It's easy to be nervous when you're waiting for confirmations and your thoughts are running away with you. All I can say is that the devs and the board have been great through all of this and Bittrex support has been first class.

Everything will settle down. Keep in touch with this thread and the answers will come.

The team is very busy at the moment so for anyone still unsure please take the time to read through this thread and try not to post questions that have been answered before.

Ok good and bad news...

We made Coin2.0 with 60 mil coins instead of 50 mil.  We did this because in Proof of Stake a 51% is possible.  It is very expensive but possible.  So we needed extra Coin2.0 to make sure no one could buy the majority (51%) of Coin2.0.  We figure about 8 mil is enough to keep aside for security. We also had to cover the amounts that the 3 exchanges lost during the attack and would like to have a few for bounties for Android wallet and coin2.0j.  However, we are only at 42 million +/- old C2 transfered right now.  We still have to cover the exchanges for what they lost and we will have a better idea tommorrow night. However, if we do not have more people transfer we will have a surplus of +/- ~ 8 million Coin2.0.  

What should we do with this surplus?

1. Would you guys like this to be distributed to you, the users?

2. Save for future development?i.e. Android wallets, multipool, advertisement

3. Faucets/Giveaways?

Please comment.

we are aware of the issue and trying to rectify the issue. Please stand by

Apologise.

New security holes are always showing up. The latest one, the so-called Heartbleed Bug in the OpenSSL cryptographic library, is an especially bad one.
heartbleedHeartbleed OpenSSL zero-day vulnerability.

While Heartbleed only effects OpenSSL's 1.0.1 and the 1.0.2-beta release, 1.01 is already broadly deployed. Since Secure-Socket Layer (SSL) and Transport Layer Security (TLS) are at the heart of Internet security, this security hole is serious.

The flaw can potentially be used to reveal not just the contents of a secured-message, such as a credit-card transaction over HTTPS, but the primary and secondary SSL keys themselves. This data could then, in theory, be used as a skeleton keys to bypass secure servers without leaving a trace that a site had been hacked.

This bug not a problem with OpenSSL's inherent design. It's an implementation problem. That is to say it the result of a programming mistake. There is already a fix available for the problem for the 1.01 program in OpenSSL 1.0.1g. Work is proceeding rapidly for a pair of the 1.02-beta line.

That's bad enough. but what really has some operating system and security companies ticked is that OpenSSL and others were hard at work at delivering the patched versions that would have limited the problem's possible use by blackhat hackers, CloudFlare, a Web security company, revealed in a blog posting details about the security hole and that they've fixed the bug. They appear to have used the methods described by OpenSSL. Unfortunately, for everyone else, these methods were not ready for broad deployment.

According to one senior security developer at a major operating system company, "The main problem with what CloudFlare did was that they jumped the gun before the FIRST AVAILABLE patches were available to users. You don't open the door and wave a red flag before the patches are ready to go."

John Graham-Cumming. a CloudFlare programmer, insisted that this misrepresented CloudFlare's
impact on the news of the Heartbleed security hole since the OpenSSL annoucement had been posted to Hacker News earlier.

At this time, I am informed by sources that Red Hat, Debian, SuSE, Canonical, and Oracle, to name a few, are working at a feverish pace to get the patched versions of OpenSSL out to their clients. It's expected that it may take approximately 12-hours to deliver the patches. When do they become available anyone using OpenSSL 1.01 or 1.02 must deploy the patched version as fast as possible.

Calm down guys. The price went down and back up before. All coins do it. They are working their asses off creating a FPS game. Also have jobs too. If you see a mistake then just PM the dev and he will change it when he has time. Once the game is released this will only keep increasing in value. Yes there will be hiccups on the way but that happens in everything in life.

If you got your coins free then there can be no complaints. If you bought them and you're annoyed at the price then it was your decision to buy. This is an investment not a pump and dump down to 1 Sat coin like most turn out to be.

It's just a blip and we will recover. We have a strong community. Don't listen to the derampers who want the price down. Bitcoin had it too in the early days.

I am glad I am entertaining some people though

Hold the line guys. You will be glad you did.

If you want to sell then do so. The coins will go to an investor and all is good. It will build a solid support from which we can rise from as new investors enter.

First of all you must know that how price goes up and down.
whenever there are higher volume for buy trade then price jumps up and whenever there will be sell order volume price falls down.
If we will be listed in much exchanges there will be little difference in price, might be go up
but for actual price rise we must have a lot better plans, a lot investors, a lot of way for people to involve in C2 so buy volume will rise and sell volume will be less, That is the perfect situation when price will rise up.

Conclusion: Exchanges will help us build up in volume base.