Topic: [ANN][C2.1] Coin2 | Pow/PoS | ChainOfConflict[FPS] The Future of Gaming is Now - page 465. (Read 499723 times)

good morning guys :-)

we will post an update as they arrive

as of now the devs are doing their best doing their jobs.

we will make sure the coins will NOT disappear!!!

i invested my own fiat money heavily as well like everyone here

The Dev(Joel)& his team will pull this thru!

thanks for your patience my fellowship of Coin2


PS: I am not selling, when I learned what the Dev's plan with this coin I was like...this is a KEEPER...
Plans: FPS Game + many more (not allowed to say, but will be announce as we progress)...

we are waiting two days.
but nothing like : We are working on it.
is not the from dev.  
I have bad feelings  

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.

And for korenko, you believe in Tor? Look what the world had to learn just now:
http://motherboard.vice.com/read/tor-if-you-want-privacy-or-anonymity-stay-off-the-internet-this-week

Tor clients could possibly be induced to send sensitive information like "what sites you visited in this session" to your entry guards.

Well it would be great to hear some news but perhaps devs  are busy ... :-) I just hope that everything is going to be ok.

Excellent! With PoS this coin will be something really special!

+1

Implementing a multipool wouldn't require changing any of the fundamentals of the coin. The coin could stay at the 50mil max supply AND provide incentive for miners to secure the network.

I don't have much hash power to contribute, but I'd be happy to point my miner at it if it meant securing the coin and increasing the value of my holdings.

Why isn't there a multipool for this coin?
That would secure the network and also rise the value of this coin.

... I don't think I can spare any time to this. ....

For my thoughts; converting that to PoS
might be possible, either they can
remove current wallet completely, and
fork from peercoin derivatives (even mint).

I think it should sync nicely, and if it is
able to sync, just replace everyone's wallet
with that one.

Otherwise, they might have forked from
a later version of bitcoin which is not
backwards compatible (I doubt so),
it may better to take peercoin's changes to original bitcoin
it forked from and apply those changes to the coin's code.

Come on C2! Work in progress I wish to see final results.

Joel himself posted on FB that he will pump the price on bter to 0.001 asking everyone to remove their sell orders, then he did nothing. I call this desperation.

Anyway, I really could not care less about your brainwashed community.