bitchat: A Decentralized "Doomsday Chat Tool" Built with Bluetooth Mesh and Nostr

As a Java veteran who's been tormented by Spring Boot for years, I nearly thought I'd slipped into a parallel universe when I encountered bitchat, a Swift project that builds a decentralized chat tool using Bluetooth Mesh—and seamlessly switches to the Nostr protocol over the internet? This is basically a real-life "doomsday communicator" meets "digital campfire."

What the heck is this thing?

In short, bitchat is an instant messaging app with a dual-channel architecture:

• Local Mode: Uses Bluetooth Mesh networking for automatic device discovery and multi-hop relaying (up to 7 hops), fully functional offline. Ideal for extreme scenarios like earthquakes, protests, or wilderness camping.
• Global Mode: Connects to 290+ Nostr relay nodes worldwide and supports geohash-based "location channels" (e.g., #dr5rsj7 represents a specific neighborhood).

The wildest part? It doesn’t even require an account! No phone number, no email, no persistent ID—you open the app and instantly become an anonymous node, sending private messages like IRC with /msg. This design reminded me of my college days transferring files via infrared in dorm rooms—except now it’s upgraded to an encrypted, self-organizing, intelligently routed modern version.

Technical Architecture: Communication Layers Like LEGO Bricks

The core innovation of bitchat lies in its hybrid transport architecture. Think of it as a vehicle that can handle both off-road trails and highways:

• Bluetooth Mesh Layer: Uses the Noise Protocol for end-to-end encryption, transmits messages in a compact binary format, and applies LZ4 compression with adaptive power-saving strategies. It’s like outfitting every message with body armor and stuffing it into a vacuum-sealed bag.
• Nostr Layer: Implements the NIP-17 encryption standard, using "gift-wrapping" to hide recipient identities and prevent relay snooping.

Even more impressive is the intelligent routing: When sending a private message, it prioritizes Bluetooth (fast and private), falls back to Nostr if Bluetooth isn’t available, and queues the message if neither works—waiting for network recovery. This logic is smarter than my company’s microservices circuit-breaking and degradation strategy!

Getting Started: A Blessing for Swift Devs, Confusion for Java Veterans

As a Java developer, my first instinct was: “Where are the Maven coordinates? Where’s the Gradle dependency?” But then I realized—this is a pure iOS/macOS app. Here’s how you build it:

## Option 1: Open with Xcode
cd bitchat
open bitchat.xcodeproj

## You'll need to manually configure Local.xcconfig and Bundle ID

Or use just (a modern command runner):

brew install just
just run  # Auto-configures and runs
just clean  # Cleans up and resets

Honestly, this setup might feel a bit alienating for non-Apple ecosystem developers. But if you’re a Swift engineer, this project is a playground—clean code structure, well-decoupled modules, and even a triple-tap data wipe feature that’s far more honest about privacy than some big-tech apps.

Security Warning: Don’t Use It for Secrets

The authors are refreshingly transparent. The README includes a prominent warning: Private messaging hasn’t undergone third-party security audits and may contain vulnerabilities—don’t use it for sensitive communications. That honesty deserves applause! While many open-source projects pretend to be bulletproof, bitchat straight-up tells you, “Hey, this is still in beta.”

That said, public channels (Bluetooth broadcasts) carry no security risk—they’re inherently public, like shouting in a town square. Encryption isn’t needed when everyone can hear you anyway.

Should You Learn From It? My Take

• If you work on mobile/IoT: Absolutely dive deep! Bluetooth Mesh + multi-hop relaying + adaptive power management has huge potential in emergency comms, field operations, and ad-hoc networking.
• If you’re a backend/Java developer: Even though the language differs, the protocol design philosophy—dual channels, intelligent fallback, location-based channels—can inspire your own systems. Could you build a “LAN-first” microservices call chain?
• For regular users: It’s already on the App Store. Give it a try—it’s cool, especially as an “underground comms tool” at tech-savvy geek meetups.

One final rant: The project is called bitchat, yet the UI follows a minimalist IRC style with not a single emoji in sight… Clearly, hardcore devs only care about protocols and byte streams!

In summary, bitchat isn’t the “next WeChat”—but it might just be the “next lifeline in a disaster.” In an era dominated by centralized platforms, this decentralized, offline-first design feels like a breath of fresh air: niche, yes—but razor-sharp.