Big milestone for Zerion. 🔐 For some time, we’ve been looking for the right independent security team to audit Zerion. We spoke with multiple respected security firms because we didn’t want to rush this decision. For a project built around private communication, Tor, cryptography and self-custody, choosing the right auditors matters. Today, we’re happy to announce that Zerion’s independent security assessment with Cure53 is officially scheduled. The assessment will cover: 🔐 Messaging protocol & cryptography 🧅 Tor & P2P networking 📱 Android & device security 🔑 Vault & key lifecycle ₿ Bitcoin & Monero wallets 🛠 Native & build integration Cure53 will perform a white-box assessment, followed by fix verification and a publishable report. The audit is scheduled to begin in October 2026. We’ve always said that privacy claims should be verified, not simply trusted. Now we’re putting Zerion to the test. Open source. Independent scrutiny. Real privacy. zerion.chat

We just hit 10,000 Zerion users! 🎉🔐 A huge thank you to everyone who has downloaded Zerion, shared it with others, or helped us improve it along the way. We’re now working on Zerion 3.0.18, with fixes for onion rotation, stability improvements, and some new features. And next week is another big moment for us. Our independent security audit with Cure53 begins. 10,000 users, no phone numbers, no accounts, and no central messaging servers. We’re just getting started. zerion.chat

Big day for Zerion. 🔐 We’ve just released our most stable build yet. After months of development, security hardening and testing, Zerion is ready for its independent security assessment by Cure53, starting October 26. No phone numbers. No accounts. No central messaging server. Communication goes directly between devices over Tor, with post-quantum encryption built in. Everything is open source. Take a look, test it and read the code yourself. github.com/zerionproject/Zer…

I don't understand why you're deleting our posts. Because we're right. It's a real shame. Your users deserve to know the truth. @SimpleXChat You're mixing protocol properties with policy promises. Your own code and documentation describe SimpleX as a client-server network using SMP relays and persistent simplex queues. Those queues have router-generated RID/SID identifiers and verification keys. Your reference SMP server also supports a persistent store log and optional restoration of undelivered messages after restart. And “we can't share data” isn't what your own privacy policy says. It explicitly states that IP addresses and other transport information may be temporarily stored in some circumstances, that hosting/network providers may log IPs, and that temporarily stored information may be disclosed in response to enforceable legal requests. That's not an accusation. It's your documentation. The Tor comparison is even stranger. “Tor relays can log the IPs of all people who use them” is not how onion-service routing works. Client and onion service build separate anonymized circuits to a rendezvous point. A rendezvous relay does not simply receive both users' IP addresses. And saying there is “no policy” limiting Tor relay operators is factually wrong. Tor explicitly tells relay operators not to record or reveal user/destination IP addresses or connection timing/volume, and to keep SafeLogging enabled. This is the architectural difference we're talking about: SimpleX: encrypted messages → application-layer messaging relays → persistent queues → recipient. Zerion direct mode: device onion service → Tor → device onion service. No Zerion messaging relay. No Zerion server-side queue. No Zerion message store. SimpleX has built an interesting system for minimizing what its messaging servers can learn. We chose to remove that application-layer messaging server from the direct path entirely. Those are two legitimate designs. But “our servers only have metadata, while Tor relays can log everyone and have no policy” isn't an accurate comparison of them.

Your private conversations don’t need a phone number, account or central messaging server. Meet Zerion private messaging over Tor with post-quantum encryption on every message. No ads. No tracking. Open source. Download Zerion on Google Play. play.google.com/store/apps/d…

Спокойной ночи, братья.

Privacy isn’t only for journalists, activists or security experts. It’s for everyone. 🔐 Your family group. Your partner. Your friends. Your everyday conversations. We’re building Zerion so private communication can become something normal not something you only think about when something goes wrong. No phone number. No user account. No central messaging server. No ads or tracking. Direct communication over Tor. Open source. Hybrid post-quantum cryptography. And privacy isn’t only about encryption. Phishing, malicious links and social engineering increasingly target people, not just protocols. No messenger can magically eliminate that risk, but we believe communication software should minimize unnecessary identity exposure and give users as little infrastructure as possible to trust. Try Zerion with someone you already talk to every day. Install it with your partner, family or friends. Create a family group. Use it alongside or instead of WhatsApp or Signal and tell us what works, what doesn’t, and what we should improve. Zerion is already available on Android, Windows and Linux/Flatpak, with iOS currently being tested through TestFlight. We don’t just need security researchers testing Zerion. We need real families and everyday users too. 🔐 Privacy should be normal. Try Zerion: play.google.com/store/apps/d…

We’re working on secure offline messaging for Zerion. Encrypted messages can wait for an offline recipient without trusting the relay with the message content. We’re auditing the protocol first: crypto, metadata leaks, replay, cover traffic, recovery and malicious-relay attacks. Only after the audit passes will we implement and ship it. Privacy first. Ship second.

bc1q5hfmyzkadwww9r96sff2ew36ctksmyapucx4kq

Security doesn’t wait. Neither do we. 🔐 Zerion 3.0.12 was already a major security and stability release, with additional hardening across the protocol, pairing, calls and Tor-based communication. Then, on September 23, the Tor Project released a new security update addressing multiple high-severity issues affecting Tor clients, onion services and relays. So we’re moving again. Zerion 3.0.13 is coming today, bringing the latest Tor security update into Zerion. No phone number. No account. No central messaging server. Hybrid post-quantum cryptography. Private communication over Tor. Free & open source. We don’t wait weeks or months when an important part of our security stack receives an update. 3.0.12 hardened Zerion. 3.0.13 keeps the underlying Tor stack current. Download Zerion on Google Play and keep your app updated. 🔐

A new Zerion update is coming and it’s the most stable version we’ve built yet. We also keep getting one question: Who is actually behind Zerion? Zerion is built by a group of security specialists with more than 20 years of experience in offensive security, hacking and security research. Our team holds offensive-security certifications and, importantly, has worked on different messaging applications before. That experience is exactly why we eventually asked ourselves: Why don’t we build the messenger we actually want to use ourselves? So we built Zerion. We have enormous respect for the work that has been done in secure messaging. Signal, for example, has strong cryptography but cryptography is only one part of the threat model. Recent phishing campaigns targeting Signal users and government personnel have shown again that attackers often go around the protocol and attack users, devices and operational workflows instead. WhatsApp has also faced serious zero-day vulnerabilities over the years. For us, relying on a secure protocol alone was never enough. Zerion was designed around a broader threat model: no phone number, no account, no central messaging server, communication over Tor, hybrid post-quantum cryptography, traffic-analysis protections, encrypted local storage and an architecture designed for people who actually care about anonymity and privacy. Privacy wasn’t a feature we added to a messenger. The threat model came first. The messenger was built around it. People sometimes ask who we consider our competitor. The project we respect most in this space is SimpleX. We don’t really see them as an enemy or even as a traditional competitor. Different architectures serve different threat models, and users should understand those differences and choose what fits theirs. We respect what @SimpleXChat is building. Zerion is taking its own path. And with the next update, that path becomes significantly more stable. More soon. zerion.chat

We’re proud of what we’ve built with Zerion. 🔐🧅 What started as an idea has become a real network with 500+ loyal users and we’re growing every day. But the number isn’t what makes us proud. It’s the fact that people are trusting something we built for one purpose: private communication. Today, “privacy” has become a marketing word. Add encryption. Write “private” on the website. Collect a phone number. Require an account. Route communication through centralized infrastructure. We wanted to approach it differently. Privacy wasn’t a feature we added to Zerion. The threat model came first. The messenger was built around it. No phone number. No account registration. No central messaging servers. Tor-native communication. Open source. And we’re nowhere near finished. We’re strengthening the protocol, expanding across platforms, investing in independent security scrutiny, and listening to the people actually using Zerion. To our first 500+ users: Thank you for trusting us, testing us, challenging us and helping us build the messenger we believe should exist. We’re grateful we got the opportunity to build it. 500 is only the beginning. zerion.chat 🧅🔐