World’s most secure P2P messenger. End-to-end encrypted, zero-server architecture, quantum-resistant roadmap. WebRTC direct connections, advanced ECDH + DTLS + SAS verification, full ASN.1 validation. FOSS
Thank you all for your interest in SecureBitChat and for taking the time to check out the project! We recently completed a full redesign of the application and are actively working on the next major update. Some of the features currently in development include:
- Audio and video calling
- Mesh groups with multiple simultaneous peer-to-peer connections
- Faster connection establishment
- The ability to create and manage entities for quickly reconnecting with trusted contacts and sessions
Your feedback and questions are incredibly valuable and help shape the direction of the project.
Thanks again for the support, and stay tuned-there’s much more to come!
This is all in js and uses jsx for frontend. Has anyone tried this out yet? Using webRTC is interesting but do t you need a centralized STUN or TURN for ICE policies ?
Great question.
WebRTC still relies on STUN and, when direct connectivity isn’t possible, TURN for ICE.
SecureBitChat currently supports ^Direct Mode^, where users exchange the SDP manually (copy/paste, QR code, file, etc.). Once exchanged, the peers establish a direct WebRTC connection.
Right now, users can configure their own STUN and TURN servers directly in the settings, use public servers, or any infrastructure they trust. An optional assisted connection mode is currently in development.
