{"repo":"SecureBitChat/securebit-chat","free":true,"listed":false,"github":"https://github.com/SecureBitChat/securebit-chat","clone":"git clone https://github.com/SecureBitChat/securebit-chat.git","description":"Browser implementation of the SecureBit.chat protocol, wire-compatible with the desktop app. Per-message Double Ratchet, post-compromise recovery, mandatory SAS verification. Peer-to-peer, no accounts, no server in the trust boundary. Open source, audited.","language":"JavaScript","stars":33,"topics":["anonymous-chat","decentralized","end-to-end-encryption","p2p-chat","real-time-chat","censorship-resistant","cross-platform","messaging","peer-to-peer","privacy"],"license":"MIT","category":"chat-messaging","readme_excerpt":"SecureBit.chat End-to-end encrypted, peer-to-peer chat that runs entirely in your browser. No accounts. No servers storing your messages. No installation required. Features · How it works · Security · Quick start · Documentation --- SecureBit.chat is a browser-based, peer-to-peer messenger built on WebRTC and the Web Crypto API . Two people establish a direct, end-to-end encrypted channel and verify each other in person. There is no registration, no central server relaying or storing messages, and no account whose metadata can leak. Everything cryptographic happens locally in the two browsers. It is designed for people who need a small, auditable, zero-infrastructure way to talk privately: journalists and sources, security researchers, or anyone who simply wants a conversation that leaves nothing behind. Screenshots Open a secure channel Encrypted conversation :---: :---: Features Encryption and verification - ECDH P-384 key agreement with derived per-session keys, AES-256-GCM payloads, and DTLS-protected transport. - Double Ratchet forward secrecy. Every message is encrypted with its own key, and the session re-keys itself each time the conversation changes direction. See Forward secrecy. - Interactive safety code verification. You confirm a short code out of band before the session is trusted, which is what defeats a man in the middle. - A minimal invitation. The code you hand over carries only what is needed to open the connection — roughly 110 to 150 bytes, one QR code. K","default_branch":null,"files":null,"tree":[],"storefront":"/r/SecureBitChat","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/SecureBitChat/securebit-chat/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}