feat: rebrand to SecureBit.chat due to name conflict

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

doc/CRYPTOGRAPHY.md

@@ -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