bitchat: Offline Encrypted Messaging Through Bluetooth Mesh Networks

“

When natural disasters disrupt internet access, when protests face communication blackouts, or when confidential discussions demand absolute privacy – traditional messaging apps fail. bitchat delivers truly decentralized encrypted communication using Bluetooth mesh technology, requiring zero internet infrastructure. This technical exploration reveals how it works.

The Fundamental Flaws in Modern Communication

Current messaging systems suffer three critical vulnerabilities:

1. Centralized dependency: Reliance on servers and internet backbones
2. Metadata exposure: Communication patterns and relationships are logged
3. Single-point failure: Entire networks collapse if infrastructure fails

bitchat’s architectural solution:

graph LR
   Traditional[Traditional Apps] --> Internet --> Servers --> Surveillance
   bitchat --> BluetoothMesh --> DeviceToDevice --> EncryptedPrivacy

Technical Architecture: Three-Layer Design

1. System Overview (Based on Whitepaper Diagrams)

graph TB
   AppLayer[Application Layer] --> ServiceLayer[Encryption Services] --> NetworkLayer[Mesh Routing] --> Transport[BLE Transport]

Core Component Functions:

Layer	Component	Primary Function
Application	Chat UI	User interaction
Service	Encryption Engine	X25519/AES-256 encryption
Network	Relay Engine	Multi-hop message forwarding
Transport	Fragment Handler	Large message segmentation

2. Bluetooth Mesh Operation Principles

Network Topology Example:

graph TD
    A[Alice] --> B[Bob]
    B --> C[Carol]
    C --> D[Dave]
    D --> E[Eve]
    style A fill:#4caf50
    style E fill:#f44336

• Direct range: ~30 meters (BLE specification)
• Extended reach: Message relay through intermediary devices
• Bridge nodes: Connect separate physical clusters (e.g., between conference rooms)

Secure Message Delivery Mechanics

1. Message Relay Protocol (TTL Mechanism)

graph LR
    Sender[Origin Device TTL=7] --> Relay1[Relay 1 TTL=6] --> Relay2[Relay 2 TTL=5] --> Recipient[Destination TTL=0]

• TTL reduction: Decremented by 1 at each hop
• Loop prevention: Message ID tracking
• Relay decision logic:

  if packet.ttl <= 0: discard
  elif packet.id in processed_list: discard
  else: forward
  

2. Offline Message Handling (Store-and-Forward)

sequenceDiagram
    Sender->>Relay: Transmit message
    Relay->>Relay: Recipient offline → Cache message
    Recipient->>Relay: Online notification
    Relay->>Recipient: Deliver cached messages

Message Retention Policies:

Message Type	Retention Period	Storage Limit
Regular	12 hours	100 messages
Favorite Contacts	Permanent	1000 messages

Encryption Framework: Privacy Assurance

1. Key Exchange Process

sequenceDiagram
    Alice->>Bob: Public key transmission
    Bob->>Alice: Public key response
    Alice->>Bob: Encrypted test (X25519)
    Bob->>Alice: Verification confirmation
    Alice->>Bob: Encrypted message (AES-256-GCM)

2. Channel Encryption Method

graph LR
    Password --> Argon2id --> 256bitKey --> AES-256-GCM

Core Functionality Explained

1. Channel Communication System

stateDiagram-v2
   [*] --> Discovery
   Discovery --> Joined: Join #channel
   Joined --> PasswordCheck: Protected channel
   PasswordCheck --> Unlocked: Correct password
   Unlocked --> [*]: Exit channel

• Naming convention: #ChannelName (e.g., #EmergencyResponse)
• Administration:

  • Channel owners manage passwords
  • Configurable message retention policies

2. Message Fragmentation (Overcoming BLE Limits)

graph TD
   LargeFile --> FragmentEngine
   FragmentEngine --> F1[START Fragment]
   FragmentEngine --> F2[CONTINUE Fragment]
   FragmentEngine --> F3[END Fragment]
   F1 --> Transmission
   F2 --> Transmission
   F3 --> Transmission

• Fragment size: ≤500 bytes each
• Reassembly: Automatic reconstruction at destination

Privacy Protection Systems

1. Anti-Traffic Analysis

gantt
    title Cover Traffic Implementation
    Real Message 1 : 0, 1
    Dummy Message : 2, 1
    Real Message 2 : 4, 1
    Dummy Message : 6, 1

2. Transmission Randomization

graph LR
    UserAction --> RandomDelay(50-500ms) --> NetworkTransmission

3. Ephemeral Identities

• Session-specific random IDs
• No phone/email linkage
• Contact recognition via public key fingerprints

Performance Optimization Techniques

1. Adaptive Compression

graph LR
    Message --> SizeCheck{>100 bytes?}
    SizeCheck -->|Yes| EntropyAnalysis
    EntropyAnalysis -->|Compressible| LZ4Compression
    LZ4Compression --> Transmission
    SizeCheck -->|No| DirectTransmission

• Compression ratio: 30-70% reduction
• Processing speed: Real-time operation

2. Battery Management Strategy

Battery Level	Scan Cycle	Max Connections
>60%	3s scan / 2s pause	20 devices
30-60%	2s scan / 3s pause	10 devices
10-30%	1s scan / 8s pause	5 devices
<10%	0.5s scan / 20s pause	2 devices

Future Development Roadmap

1. Multi-Transport Architecture

graph TB
    Bluetooth --> WiFiDirect[WiFi Direct 250Mbps]
    WiFiDirect --> Ultrasound[Ultrasonic 1-10kbps]
    Ultrasound --> LoRa[LoRa 2-15km]

2. Nostr Protocol Integration

graph LR
    LocalMesh --> Gateway --> NostrRelay --> RemoteMesh

• Selective participation: User-controlled activation
• Encryption preservation: End-to-end security maintained
• Use cases:

  1. Cross-region disaster coordination
  2. Large event communication scaling
  3. Intermittent connectivity synchronization

Technical FAQ

Q1: What’s the maximum communication range?

“

Direct device-to-device: ~30 meters. Through 7 relay hops: Theoretical 200m+ (environment-dependent).

Q2: Does it support file transfers?

“

Yes. The fragmentation system splits 10KB files into 20 fragments (500 bytes each) for transmission.

Q3: How are attacks prevented?

“

Four-layer protection:

1. TTL limits propagation distance
2. Digital signatures prevent tampering
3. Connection limits block DDoS
4. Automatic relay cache clearing

Q4: What’s the battery impact?

“

Adaptive power management:

• Full charge: Continuous operation
• Low battery: 30-second scan intervals
• Real-world test: ~5% hourly consumption during active use

Conclusion: The Engineering Philosophy

bitchat demonstrates through elegant engineering:

1. True decentralization: Server-free communication viability
2. Provable privacy: Strong encryption + metadata protection
3. Simplicity as strength: 2000-line core protocol

“

As stated in the whitepaper: “When messages flow without fiber cables or cell towers, humans reclaim communication’s original freedom – this is technology’s authentic purpose.”