We are discontinuing the Cryptocat service starting tomorrow. The software is no longer maintained. Looking for alternatives? We recommend Wire. wire.com Thank you for sharing this journey with us.

Cryptocat has been using a formally verified messaging protocol implementation for the past 10 months. More to be presented at #EuroSP17.

Heads-up: it's currently possible for someone to reveal your IP address by exploiting a low-severity bug in file sharing. Update coming.

Reminder: we are running a bug bounty program. crypto.cat/security.html#…

Update 3.2.08 is now available, bringing security improvements and better macOS and Linux integration: crypto.cat/news.html#3.2.…

Pushing hard in 2017, we stand by our open letter from December: journalists using email should switch to Cryptocat. crypto.cat/news.html#nytl…

We paid €754 in infrastructure costs to run Cryptocat’s network in 2016. Help us fundraise for 2017. Here’s how: crypto.cat/news.html#fund…

Group chat: still planned, keeps getting delayed due to lack of time available to spend on the substantial development needed. It'll happen!

Wouldn’t it be awful if your Cryptocat chats were insecure? We actually made that mistake in 2013, but even we wouldn’t use CloudFlare.

Takeaway from Vault7 dump: pretty much all endpoints are exploitable. Still, Cryptocat doesn't reveal you to anyone with your phone number.

Fact is, for many at the White House, the threat model isn't CIA as much as Sean Spicer installing Signal and seeing if your number pops up.

Encrypted chat needs to be accessible under easy to obtain, interchangeable anonymous identifiers. The opposite of your phone number.

We had a service outage yesterday for about an hour. Everything is back to normal.

An attempt today to poison NS lookups for the crypto.cat TLD failed to harm users due to our client-side certificate pinning.

We’ve run into some network issues. Please stand by.

Back in operation. Also fixed a bug that prohibited new account creation.

File transfers didn’t work for a few days because of a very silly server misconfiguration. Sorry about that.

Cryptocat service was unavailable for a few hours due to a network hardware error. Service has now resumed.

It appears that the Cryptocat network is under a denial of service attack. Whoever's doing this, could you just stop? Honestly, what's the point?

Hello! Here is some Cryptocat news. We haven’t pushed a software update in a while, but one is indeed coming with bug fixes (especially for unreadable messages) and some new fun research. Current release still works great. Thanks for using Cryptocat!