SecureBitChat/securebit-chat
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

feat: rebrand to SecureBit.chat due to name conflict

Browse Source 
BREAKING CHANGE: Project renamed from LockBit.chat to SecureBit.chat

- Changed project name to avoid confusion with LockBit ransomware group
- Updated all documentation, branding, and references
- Maintained all existing functionality and security features
- Domain migration planned to securebit.chat

Reason: The LockBit name became associated with a notorious ransomware
group, causing conflicts on platforms and potential confusion for users.
SecureBit better reflects our mission of providing secure P2P messaging
while avoiding negative associations.

This change affects:
- README.md and all documentation
- Package.json name field
- Brand assets and logos
- Website references
- Social media handles

Core functionality remains unchanged:
✅ 12-layer military-grade security
✅ Lightning Network integration
✅ P2P WebRTC architecture
✅ Open source MIT license
This commit is contained in:
lockbitchat
2025-08-14 15:54:11 -04:00
parent 27428cdb0e
commit 19e3047282
11 changed files with 70 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -1,9 +1,9 @@
# lockbit-chat
# securebit-chat
🔒 World's most secure P2P messenger with Lightning Network integration. End-to-end encryption, pay-per-session model, zero data collection. WebRTC direct connections, quantum-resistant roadmap. Privacy-first communication for the Bitcoin age ⚡
🛡️ LockBit.chat - Enhanced Security Edition
🛡️ SecureBit.chat - Enhanced Security Edition
🎯 About the Project
LockBit.chat is a revolutionary P2P messenger that combines:
SecureBit.chat is a revolutionary P2P messenger that combines:
Military-grade cryptography (ECDH P-384 + AES-GCM 256)
Lightning Network payments for sessions
@@ -35,7 +35,7 @@ No metadata collection
🚀 Quick Start
Open: https://lockbit.chat
Open: https://SecureBit.chat
Choose: "Create Channel" or "Join"
Pay: for session via Lightning
Chat: securely!
@@ -71,8 +71,8 @@ P2P: WebRTC DataChannels
Payments: Lightning Network / WebLN
Local Development:
bashgit clone https://github.com/lockbitchat/lockbit-chat.git
cd lockbit-chat
bashgit clone https://github.com/SecureBitChat/securebit-chat.git
cd securebit-chat
python -m http.server 8000
# Open http://localhost:8000
🤝 Contributing
@@ -88,8 +88,8 @@ How to help:
📄 License
MIT License with mandatory attribution
⚠️ Disclaimer
LockBit.chat is provided "as is". Use at your own risk. For mission-critical communications, additional security verification is recommended.
SecureBit.chat is provided "as is". Use at your own risk. For mission-critical communications, additional security verification is recommended.
📞 Contacts
🌐 Website: https://lockbit.chat
🌐 Website: https://SecureBit.chat
📧 Email: lockbitchat@tutanota.com

18
SECURITY.md
View File

@@ -2,7 +2,7 @@
## 🛡️ Security Overview
LockBit.chat is built with security-first principles and implements **military-grade security** with 12-layer protection system. We take security vulnerabilities seriously and appreciate responsible disclosure from the security community.
SecureBit.chat is built with security-first principles and implements **military-grade security** with 12-layer protection system. We take security vulnerabilities seriously and appreciate responsible disclosure from the security community.
**Current Security Status:** 🔒 **MAXIMUM SECURITY (Stage 4)** - Exceeds government-grade communication standards
@@ -52,7 +52,7 @@ For **critical security issues** that could compromise user safety:
**DO NOT** create a public GitHub issue.
**Contact us privately:**
- 📧 **Email:** security@lockbit.chat (PGP key below)
- 📧 **Email:** security@SecureBit.chat (PGP key below)
- 🔒 **Signal:** +[REDACTED] (ask for Signal number via email)
- 🔐 **Keybase:** @lockbitchat
@@ -63,7 +63,7 @@ For general security improvements or non-critical findings:
## 📝 Vulnerability Disclosure Process
1. **Report:** Send details to security@lockbit.chat
1. **Report:** Send details to security@SecureBit.chat
2. **Acknowledgment:** We'll respond within 24 hours
3. **Investigation:** We'll investigate and keep you updated
4. **Fix:** We'll develop and test a fix
@@ -77,10 +77,10 @@ For general security improvements or non-critical findings:
## 🏆 Security Hall of Fame
We maintain a hall of fame for security researchers who help improve LockBit.chat:
We maintain a hall of fame for security researchers who help improve SecureBit.chat:
<!-- Security researchers will be listed here -->
*Be the first to help secure LockBit.chat!*
*Be the first to help secure SecureBit.chat!*
## 🔍 Security Audit History
@@ -123,7 +123,7 @@ We maintain a hall of fame for security researchers who help improve LockBit.cha
### For Maximum Security:
1. **Verify Authenticity:** Always verify out-of-band codes (enhanced 6-digit format)
2. **Use Official Source:** Only use https://lockbit.chat
2. **Use Official Source:** Only use https://SecureBit.chat
3. **Keep Updated:** Use version 4.0.x for maximum security
4. **Secure Environment:** Use updated browsers on secure devices
5. **Lightning Wallets:** Use reputable Lightning wallets (Alby, Zeus, etc.)
@@ -213,14 +213,14 @@ webrtcManager.getSecurityStatus()
## 📞 Contact Information
- **Security Team:** security@lockbit.chat
- **Security Team:** security@SecureBit.chat
- **General Contact:** lockbitchat@tutanota.com
- **GitHub Issues:** https://github.com/lockbitchat/lockbit-chat/issues
- **GitHub Issues:** https://github.com/lockbitchat/securebit-chat/issues
- **Security Announcements:** [@lockbitchat](https://twitter.com/lockbitchat)
## 🏅 Security Achievements
LockBit.chat v4.0 provides:
SecureBit.chat v4.0 provides:
- **🥇 Military-Grade Security:** 12-layer protection system
- **🥇 Government-Level Encryption:** Triple AES-256-GCM + P-384 ECDH/ECDSA
- **🥇 Perfect Forward Secrecy:** Complete with automatic key rotation

4
doc/API.md
View File

@@ -1,8 +1,8 @@
# LockBit.chat API Documentation
# SecureBit.chat API Documentation
## 🏗️ Architecture Overview
LockBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
SecureBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
## 📚 Core Classes

22
doc/CONTRIBUTING.md
View File

@@ -1,6 +1,6 @@
# Contributing to LockBit.chat
# Contributing to SecureBit.chat
🎉 **Thank you for your interest in contributing to LockBit.chat!**
🎉 **Thank you for your interest in contributing to SecureBit.chat!**
We're building the most secure P2P messenger with Lightning Network integration, and we need your help to make it even better.
@@ -19,7 +19,7 @@ Help audit our cryptographic implementation
Improve guides, tutorials, and technical docs
### 🌍 Translations
Help make LockBit.chat accessible worldwide
Help make SecureBit.chat accessible worldwide
### 💻 Code Contributions
Submit pull requests for bug fixes and features
@@ -36,8 +36,8 @@ Submit pull requests for bug fixes and features
``bash
# 1. Fork the repository on GitHub
# 2. Clone your fork
git clone https://github.com/yourusername/lockbit-chat.git
cd lockbit-chat
git clone https://github.com/yourusername/securebit-chat.git
cd securebit-chat
# 3. Create a development branch
git checkout -b feature/your-feature-name
@@ -240,7 +240,7 @@ Submit PR - Follow contribution guidelines
Translation Keys
json{
"header.title": "LockBit.chat - Enhanced Security Edition",
"header.title": "SecureBit.chat - Enhanced Security Edition",
"security.level.high": "HIGH",
"crypto.algorithm.ecdh": "ECDH P-384",
"error.connection.failed": "Connection failed"
@@ -267,7 +267,7 @@ Communication Channels
GitHub Discussions - Technical discussions
GitHub Issues - Bug reports and features
Email - lockbitchat@tutanota.com
Security - security@lockbit.chat
Security - security@SecureBit.chat
Code of Conduct
We follow the Contributor Covenant:
@@ -311,11 +311,11 @@ Thank you for helping make the internet more private and secure! 🛡️
# docs/API.md
``markdown
# LockBit.chat API Documentation
# SecureBit.chat API Documentation
## 🏗️ Architecture Overview
LockBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
SecureBit.chat is built as a client-side application with no backend servers. The "API" consists of JavaScript classes and methods that handle cryptography, P2P connections, and Lightning Network integration.
## 📚 Core Classes
@@ -954,7 +954,7 @@ javascript// Service worker for offline capability
// sw.js
self.addEventListener('install', event => {
event.waitUntil(
caches.open('lockbit-chat-v1').then(cache => {
caches.open('securebit-chat-v1').then(cache => {
return cache.addAll([
'/',
'/index.html',
@@ -1203,7 +1203,7 @@ Getting Help
Documentation: Full API docs at /docs/
GitHub Issues: Bug reports and feature requests
Community: Discussions and Q&A
Security: security@lockbit.chat for vulnerabilities
Security: security@SecureBit.chat for vulnerabilities
Contributing

18
doc/CRYPTOGRAPHY.md
View File

@@ -1,8 +1,8 @@
# LockBit.chat Cryptographic Implementation
# SecureBit.chat Cryptographic Implementation
## 🔐 Overview
LockBit.chat implements state-of-the-art cryptographic protocols providing **military-grade security** for peer-to-peer communications. Our cryptographic design prioritizes security, performance, and future-proofing against emerging threats including quantum computing.
SecureBit.chat implements state-of-the-art cryptographic protocols providing **military-grade security** for peer-to-peer communications. Our cryptographic design prioritizes security, performance, and future-proofing against emerging threats including quantum computing.
**Cryptographic Strength:** 256+ bit security level
**Quantum Resistance:** Timeline > 2040
@@ -492,7 +492,7 @@ async function deriveSharedKeys(privateKey, publicKey, salt) {
const encoder = new TextEncoder();
// Enhanced context info
const contextInfo = encoder.encode('LockBit.chat v4.0 Enhanced Security Edition');
const contextInfo = encoder.encode('SecureBit.chat v4.0 Enhanced Security Edition');
// Derive master shared secret
const sharedSecret = await crypto.subtle.deriveKey(
@@ -1302,9 +1302,9 @@ class CryptographicErrorHandler {
### Technical Support
For cryptographic implementation questions:
- **Security Team:** security@lockbit.chat
- **Cryptographic Specialists:** crypto@lockbit.chat
- **GitHub Issues:** [Cryptography Issues](https://github.com/lockbitchat/lockbit-chat/issues?q=label%3Acryptography)
- **Security Team:** security@SecureBit.chat
- **Cryptographic Specialists:** crypto@SecureBit.chat
- **GitHub Issues:** [Cryptography Issues](https://github.com/lockbitchat/securebit-chat/issues?q=label%3Acryptography)
### Additional Resources
@@ -1327,7 +1327,7 @@ For cryptographic implementation questions:
## 🏁 Conclusion
LockBit.chat's cryptographic implementation represents the state-of-the-art in secure peer-to-peer communications. Our multi-layered approach combining classical cryptography with forward-looking security measures provides unprecedented protection against current and future threats.
SecureBit.chat's cryptographic implementation represents the state-of-the-art in secure peer-to-peer communications. Our multi-layered approach combining classical cryptography with forward-looking security measures provides unprecedented protection against current and future threats.
### Key Achievements
@@ -1348,11 +1348,11 @@ Our cryptographic implementation provides:
- **Forward Secrecy:** Past communications remain secure
- **Replay Protection:** Comprehensive anti-replay mechanisms
**This cryptographic foundation enables LockBit.chat to provide the most secure peer-to-peer communications platform available today.**
**This cryptographic foundation enables SecureBit.chat to provide the most secure peer-to-peer communications platform available today.**
---
*This document reflects the current state of cryptographic implementation in LockBit.chat v4.0. All algorithms and protocols are subject to ongoing security review and enhancement.*
*This document reflects the current state of cryptographic implementation in SecureBit.chat v4.0. All algorithms and protocols are subject to ongoing security review and enhancement.*
**Last Updated:** January 14, 2025
**Document Version:** 4.0

12
doc/SECURITY-ARCHITECTURE.md
View File

@@ -1,8 +1,8 @@
# LockBit.chat Security Architecture
# SecureBit.chat Security Architecture
## 🛡️ Overview
LockBit.chat implements a revolutionary **12-layer security architecture** that provides military-grade protection for peer-to-peer communications. This document details the technical implementation of our security system, which exceeds most government and enterprise communication standards.
SecureBit.chat implements a revolutionary **12-layer security architecture** that provides military-grade protection for peer-to-peer communications. This document details the technical implementation of our security system, which exceeds most government and enterprise communication standards.
**Current Implementation:** Stage 4 - Maximum Security
**Security Rating:** Military-Grade
@@ -107,7 +107,7 @@ const keyPackage = {
- **Curve:** NIST P-384 (secp384r1)
- **Key Derivation:** HKDF with SHA-384
- **Salt Size:** 64 bytes (enhanced from standard 32 bytes)
- **Context Info:** "LockBit.chat v4.0 Enhanced Security Edition"
- **Context Info:** "SecureBit.chat v4.0 Enhanced Security Edition"
**Key Derivation Process:**
```javascript
@@ -706,9 +706,9 @@ webrtcManager.checkFakeTrafficStatus()
For technical questions about the security architecture:
- **Security Team:** security@lockbit.chat
- **Technical Documentation:** docs@lockbit.chat
- **GitHub Issues:** [Security Architecture Issues](https://github.com/lockbitchat/lockbit-chat/issues?q=label%3Asecurity-architecture)
- **Security Team:** security@SecureBit.chat
- **Technical Documentation:** docs@SecureBit.chat
- **GitHub Issues:** [Security Architecture Issues](https://github.com/lockbitchat/securebit-chat/issues?q=label%3Asecurity-architecture)
---

34
index.html
View File

@@ -18,24 +18,24 @@
<meta http-equiv="Referrer-Policy" content="strict-origin-when-cross-origin">
<!-- GitHub Pages SEO -->
<meta name="description" content="LockBit.chat — P2P messenger with military-grade cryptography and Lightning Network payments">
<meta name="description" content="SecureBit.chat — P2P messenger with military-grade cryptography and Lightning Network payments">
<meta name="keywords" content="P2P messenger, encryption, Lightning Network, WebRTC, privacy">
<meta name="author" content="Volodymyr">
<link rel="canonical" href="https://github.com/lockbitchat/lockbit-chat/">
<link rel="canonical" href="https://github.com/lockbitchat/securebit-chat/">
<!-- Open Graph -->
<meta property="og:title" content="LockBit.chat - Enhanced Security Edition">
<meta property="og:title" content="SecureBit.chat - Enhanced Security Edition">
<meta property="og:description" content="The first P2P messenger with Lightning Network payments">
<meta property="og:url" content="https://github.com/lockbitchat/lockbit-chat/">
<meta property="og:url" content="https://github.com/lockbitchat/securebit-chat/">
<meta property="og:type" content="website">
<meta property="og:image" content="https://github.com/lockbitchat/lockbit-chat/assets/images/og-image.png">
<meta property="og:image" content="https://github.com/lockbitchat/securebit-chat/assets/images/og-image.png">
<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="LockBit.chat - Enhanced Security Edition">
<meta name="twitter:title" content="SecureBit.chat - Enhanced Security Edition">
<meta name="twitter:description" content="P2P messenger with military-grade cryptography">
<title>LockBit.chat - Enhanced Security Edition</title>
<title>SecureBit.chat - Enhanced Security Edition</title>
<script src="https://unpkg.com/react@18/umd/react.production.min.js"></script>
<script src="https://unpkg.com/react-dom@18/umd/react-dom.production.min.js"></script>
<script src="https://unpkg.com/@babel/standalone/babel.min.js"></script>
@@ -166,7 +166,7 @@
React.createElement('h3', {
key: 'title',
className: "text-2xl font-semibold text-primary mb-3"
}, 'Why LockBit.chat is unique'),
}, 'Why SecureBit.chat is unique'),
React.createElement('p', {
key: 'subtitle',
className: "text-secondary max-w-2xl mx-auto"
@@ -276,7 +276,7 @@
const messengers = [
{
name: "LockBit.chat",
name: "SecureBit.chat",
logo: <div className="w-8 h-8 bg-orange-500/10 border border-orange-500/20 rounded-lg flex items-center justify-center">
<i className="fas fa-shield-halved text-orange-400" />
</div>,
@@ -455,7 +455,7 @@
Enhanced Security Edition Comparison
</h3>
<p className="text-secondary max-w-2xl mx-auto mb-4">
LockBit.chat v4.0 Enhanced Security Edition vs leading secure messengers
SecureBit.chat v4.0 Enhanced Security Edition vs leading secure messengers
</p>
<div className="inline-flex items-center px-4 py-2 bg-yellow-500/10 border border-yellow-500/20 rounded-lg">
<span className="text-yellow-400 mr-2">🏆</span>
@@ -601,10 +601,10 @@
<div className="p-6 bg-gradient-to-r from-orange-500/10 to-yellow-500/10 border border-orange-500/20 rounded-xl">
<h4 className="text-xl font-bold text-orange-400 mb-4 flex items-center">
<i className="fas fa-trophy mr-3" />
LockBit.chat v4.0 Enhanced Security Edition Summary
SecureBit.chat v4.0 Enhanced Security Edition Summary
</h4>
<p className="text-secondary leading-relaxed text-lg mb-4">
LockBit.chat dominates in 11 out of 15 security categories, establishing itself as the most secure P2P messenger available.
SecureBit.chat dominates in 11 out of 15 security categories, establishing itself as the most secure P2P messenger available.
The Enhanced Security Edition introduces revolutionary 12-layer defense architecture, Lightning Network integration, and military-grade cryptography that exceeds government and enterprise standards.
</p>
<div className="grid md:grid-cols-2 gap-4 mt-6">
@@ -895,7 +895,7 @@
Development Roadmap
</h3>
<p key="subtitle" className="text-secondary max-w-2xl mx-auto mb-6">
Evolution of LockBit.chat: from initial development to a quantum-resistant decentralized network
Evolution of SecureBit.chat: from initial development to a quantum-resistant decentralized network
</p>
<div
key="roadmap-note"
@@ -1057,7 +1057,7 @@
Join the future of privacy
</h4>
<p key="cta-description" className="text-secondary mb-6">
LockBit.chat grows thanks to the community. Your ideas and feedback help shape the future of secure communication.
SecureBit.chat grows thanks to the community. Your ideas and feedback help shape the future of secure communication.
</p>
<div
@@ -1066,7 +1066,7 @@
>
<a
key="github-link"
href="https://github.com/lockbitchat/lockbit-chat/"
href="https://github.com/lockbitchat/securebit-chat/"
className="btn-primary text-white py-3 px-6 rounded-lg font-medium transition-all duration-200 flex items-center justify-center"
>
<i key="github-icon" className="fab fa-github mr-2" />
@@ -1176,7 +1176,7 @@
React.createElement('h1', {
key: 'title',
className: 'text-lg sm:text-xl font-semibold text-primary'
}, 'LockBit.chat'),
}, 'SecureBit.chat'),
React.createElement('p', {
key: 'subtitle',
className: 'text-xs sm:text-sm text-muted hidden sm:block'
@@ -2916,7 +2916,7 @@
handleAnswerError
);
handleMessage('🚀 LockBit.chat Enhanced Edition initialized. Ready to establish a secure connection with ECDH, encrypted exchange, and verification.', 'system');
handleMessage('🚀 SecureBit.chat Enhanced Edition initialized. Ready to establish a secure connection with ECDH, encrypted exchange, and verification.', 'system');
// Cleanup on page unload
const handleBeforeUnload = () => {

2
src/components/ui/Header.jsx
View File

@@ -105,7 +105,7 @@ const EnhancedMinimalHeader = ({
React.createElement('h1', {
key: 'title',
className: 'text-lg sm:text-xl font-semibold text-primary'
}, 'LockBit.chat'),
}, 'SecureBit.chat'),
React.createElement('p', {
key: 'subtitle',
className: 'text-xs sm:text-sm text-muted hidden sm:block'

2
src/crypto/EnhancedSecureCryptoUtils.js
View File

@@ -1275,7 +1275,7 @@ class EnhancedSecureCryptoUtils {
const encoder = new TextEncoder();
// Enhanced context info with version and additional entropy
const contextInfo = encoder.encode('LockBit.chat v4.0 Enhanced Security Edition');
const contextInfo = encoder.encode('SecureBit.chat v4.0 Enhanced Security Edition');
// Derive master shared secret with enhanced parameters
// Try SHA-384 first, fallback to SHA-256

10
src/session/PayPerSessionManager.js
View File

@@ -445,7 +445,7 @@ class PayPerSessionManager {
body: JSON.stringify({
out: false, // incoming payment
amount: pricing.sats,
memo: `LockBit.chat ${sessionType} session (${pricing.hours}h) - ${Date.now()}`,
memo: `SecureBit.chat ${sessionType} session (${pricing.hours}h) - ${Date.now()}`,
unit: 'sat',
expiry: this.verificationConfig.invoiceExpiryMinutes * 60 // В секундах
}),
@@ -470,9 +470,9 @@ class PayPerSessionManager {
sessionType: sessionType,
createdAt: Date.now(),
expiresAt: Date.now() + (this.verificationConfig.invoiceExpiryMinutes * 60 * 1000),
description: data.description || data.memo || `LockBit.chat ${sessionType} session`,
description: data.description || data.memo || `SecureBit.chat ${sessionType} session`,
bolt11: data.bolt11 || data.payment_request,
memo: data.memo || `LockBit.chat ${sessionType} session`
memo: data.memo || `SecureBit.chat ${sessionType} session`
};
} catch (error) {
@@ -502,7 +502,7 @@ class PayPerSessionManager {
sessionType: sessionType,
createdAt: Date.now(),
expiresAt: Date.now() + (5 * 60 * 1000), // 5 минут
description: `LockBit.chat ${sessionType} session (DEMO)`,
description: `SecureBit.chat ${sessionType} session (DEMO)`,
isDemo: true
};
}
@@ -1242,7 +1242,7 @@ class PayPerSessionManager {
return {
amount: pricing.sats,
memo: `LockBit.chat ${sessionType} session (${pricing.hours}h) - ${timestamp}`,
memo: `SecureBit.chat ${sessionType} session (${pricing.hours}h) - ${timestamp}`,
sessionType: sessionType,
timestamp: timestamp,
paymentHash: paymentHash,

2
test-lnbits-integration.html
View File

@@ -158,7 +158,7 @@
body: JSON.stringify({
out: false,
amount: 500,
memo: 'LockBit.chat test invoice',
memo: 'SecureBit.chat test invoice',
unit: 'sat',
expiry: 300
})