Radar Chat hit the headlines last week as the 'privacy-first Signal fork with Bitcoin Lightning payments built in.' The pitch is seductive: end-to-end encrypted messaging combined with self-custodial micropayments, all without a token or centralized server. Crypto Briefing framed it as a 'move to drive mainstream adoption.' But after 48 hours of aggressive investigation—pulling the APK apart, tracing the GitHub commits, and running testnet transactions—I found a project that screams 'early-stage experiment' with more holes than a testnet faucet.
The GitHub repo shows exactly 7 commits, all made by a single anonymous contributor. The codebase is a direct clone of Signal's v6.48.0, with only a few files modified to bolt on Lightning support. No audit reports exist. No team page. No roadmap. The Twitter account has 48 followers, most of them bots. This is not the infrastructure for mainstream adoption; it's a side project that might die before its first Lightning channel closes.
Context: Why This Fork Even Matters
The combination of messaging and payments is a crowded battlefield. Telegram’s TON blockchain already handles billions in token transfers. WhatsApp is rolling out payments in Brazil. Signal itself has stayed pure—no crypto, no blockchain, just encrypted text. Radar Chat's differentiation is self-custodial Bitcoin Lightning payments: you run your own Lightning node inside the app, control your own private keys, and route payments over the Lightning Network without a custodian. In theory, this is the holy grail for privacy absolutists who want to send satoshis as easily as they send a text.
But theory and practice diverge hard when you actually try to use it. I downloaded the Android APK from their website (no Google Play listing—already a red flag for mainstream adoption). The app launched, let me register a phone number, and displayed a Signal-style chat interface. The Lightning tab, however, required me to open a channel. The app automatically connected to a single public node run by the team (identity unknown). I funded a testnet channel with 100,000 satoshis from my own node. The payment flow was clunky: I had to scan a QR code from another device, wait 30 seconds for the Lightning invoice to settle, and then the chat showed a 'paid' badge. For a tech-savvy user, it's acceptable. For a normie? Impossible.
Core: What the Code Actually Reveals
I decompiled the APK using JADX and traced the Lightning module. The app uses LDK (Lightning Development Kit) version 0.0.115—a lightweight library for mobile nodes. That's a solid choice. But the channel management logic is alarmingly simple: it only supports one outbound channel to a default peer, no inbound liquidity options, and no backup mechanism for channel state. If you lose your phone without a backup, your channel funds are gone. The app doesn't even generate a seed phrase during setup; it silently stores the private key in Android's Keystore, which is encrypted but exportable only by root. The response for 'lost funds' is: 'We recommend testing with small amounts.' That's not a product; it's a prototype.
I also ran a static analysis using my Python scripts to scrape the repository for any hardcoded API keys or dangerous permissions. The app requests the 'CAPABILITY_C2C' permission (android.permission.INTERNET is standard), but also 'QUERY_ALL_PACKAGES'—a permission often used for fingerprinting. No evidence of actual data leaks, but the permission creep is concerning. More critically, the app sends all messages through a centralized relay server (just like Signal), but the Lightning node communicates directly with the Bitcoin network. That means your IP is exposed when your Lightning node syncs gossip. The team claims 'privacy-first,' but your IP is visible to every Lightning peer you connect to.
Contrarian Angle: Why the Skepticism May Be Overblown
But let me play devil’s advocate. Every major crypto project started as an anonymous fork with no users. Monero’s early code was a Bytecoin fork. Lightning itself was a whitepaper with no implementation. Radar Chat’s anonymity could be a feature, not a bug—the team may want to avoid early regulatory attention. And the lack of a token is actually refreshing: no VCs to please, no speculative farming, no pre-mine. The app is free, open-source, and self-custodial by design. If they can iterate fast and solve the UX friction, they might carve out a niche for privacy-conscious Bitcoiners who refuse to use custodial wallets like Wallet of Satoshi.
During the 2021 NFT metadata fragmentation investigation, I learned that many projects claimed decentralization but used centralized server links. Radar Chat's code is at least transparent: you can build it yourself from source (if you can get the dependencies right). I attempted a reproducible build and failed because of differences in the Android SDK versions. But the fact that the source is available and the build scripts are mostly correct is more than most 'crypto' apps offer.
Still, the risks are real. The self-custodial Lightning experience is notoriously hard to get right. Phoenix Wallet has been doing it for years with a polished UX, and they still have issues with channel liquidity and fees. Radar Chat has zero documentation on fee policies, channel rebalancing, or backup procedures. If a user opens a channel and the peer goes offline, they could lose access to their funds until the peer comes back—or forever if the peer drops the channel. The app doesn't even show the channel's status clearly.
Takeaway: The 90-Day Window
Radar Chat has a narrow window to prove it's more than a PR stunt. The team needs to publish a formal security audit (preferably from a firm like Trail of Bits or Kudelski), release a desktop client with full channel management, and publish a clear roadmap. Without those, this project will fade into the graveyard of Signal forks. But if they execute, they could own a tiny but loyal slice of the ‘privacy payments’ market. My advice: watch the GitHub commit frequency. If it drops below one per week for a month, assume the project is dead.
I've seen this pattern before—during the 2017 CryptoKitties crisis, dozens of 'decentralized gaming' forks appeared and vanished within weeks. Radar Chat shows the same early-stage fragility. The code is minimal. The team is invisible. The user experience is broken. Yet, the core idea—self-custodial messaging payments—is legitimately valuable. The question is whether anyone competent will build it properly.